Sunday, February 24, 2013

Major Security Issue At NiteFlirt

Phone sex platform NiteFlirt (NF) continues to be plagued by problems ever since the switch in 2009, but this latest problem is horrific.

For at least a decade, NF was reliable for its safe double-blind connections. Double-blind calls work one of two ways:

1) A caller dials into the service using 1-800-TO-FLIRT and select his PSO, whereupon the NF system would act as an intermediary, shielding his telephone number, and attempt to reach the PSO, shielding her telephone number. If/when the PSO answered her telephone and accepted the call by pressing "1" on her telephone keypad, the call would then be connected, with neither party knowing the other's telephone number or other information.

2) A caller would select his PSO from the online listings and click the "Call Now" button, whereupon the NF system would dial the telephone number selected in the caller's account. If/when the caller answered his telephone and accepted the call by pressing "1" on his telephone keypad, NF would (again acting as an intermediary shielding both telephone numbers) attempt to reach the PSO, who would also need to accept the call by pressing "1".

In both cases, the phone sex operator needs to press "1" in order for the caller to be connected to her telephone line. The caller would not be connected (or billed) unless the PSO answered the call from NF and accepted the call by pressing "1" on her telephone; no answer, no pressing of "1", and the caller would not be connected to the PSOs telephone line. Even if the PSO's telephone had voicemail which picked-up the call from NF, the call would not, could not, be connected as "1" was not pressed in acceptance.

However, there is now some sort of a "glitch" which is actually connecting calls without receipt of the "1" prompt which is the acceptance of the call -- and this so-called glitch is now connecting calls and sending callers straight to PSO voicemail, resulting in callers hearing the outgoing messages from PSOs (which includes names &/or phone numbers!) and being able to leave messages!

This is a huge security breech.

It is compounded by the fact that NF has, since the transition a few years ago, had other odd glitches which have randomly changed PSO availability settings to "Yes, Taking Calls" meaning that many PSOs are being called when they are not working and, for those using cell or mobile phones especially, this literally means turning their phones off -- which, in fact, activates voicemail services. Yikes!

If you must continue to use NF for your phone sex business or adult entertainment services, you will likely want to cease use of voicemail features on the phone you are using for NF connections. As most of us use cellphones now, it is important to note that you cannot turn off the voicemail feature on your own; you will need to contact your mobile phone service provider and have them disable your voice mail service for you. The same is true for those with cable phones, etc.

Yup, this is going to be a huge pain in the ass.

If this is happening to PSOs, is there the possibility of something similar happening with caller accounts as well? I have no access to that sort of technical information to really know. I do know that callers are connected first, so it would seem unlikely that the situation could happen in reverse, in which a PSO could reach a caller's voicemail. But I've heard callers are getting recordings of attempted connections from NF on their voicemails too -- which doesn't thrill those who use company, family, or other shared telephone lines. Plus, who knows where this "glitch" is? Err on the side of caution.

While NF has officially remained silent on this issue, some folks have suggested going back to using landlines with actual answering machines. We should not have to do this; one of NF's promises is the safety of privacy. But this is not a drill, people, so do what you have to do to stay safe!

1 comment:

Ms. Betty said...

You bet it's a pain!

The whole reason I have voicemail is so that other callers can leave messages while I'm on an NF call.

What really bugs me about this is that this glitch resulted from a change that was supposed to "fix" a different glitch.

Now we just have YET ANOTHER problem instead of a solution.

I don't know why they couldn't have just fixed the original problem instead of creating yet another broken feature!

Related Posts Plugin for WordPress, Blogger...