Sam Black at
45 minutes ish, 4 people (I think)
Change of tack this time; I used a ReactOS VM.
Typing URLs into the ReactOS run box doesn't do anything, and unfortunately the initial try of AnyDesk failed.
TeamViewer was the next try, and since I'd already installed it, it worked fine.
I was told to hang up the call and their technical support department would call me back, which was interesting as they'd already said they were call from the technical support department.
I opened some music, and left the phone next to the speaker for a bit: this didn't improve the mood of the caller, who told me to hang up "properly".
They did call me back about 30 seconds later, and logged in.
It was at this point the alpha quality of ReactOS kicked in, and promptly froze up, requiring a restart: this was a frequent recurrence, and allowed me to be "Very annoyed that their software was crashing my computer".
With the "secure security server (SSS)" connected, "it" ran a scan.
It did upset the "SSS" though, as the `dir /s` command completed far quicker than they wanted, and I was able to watch them type in the scan "failure" notice.
"ip hacked router is malfunctioning. email banking and otehr sensitive data is not secure and needs to be secured as per data protection act 2013.. also eligibe for 200 GBP refund"
...
"Bad command or filename -- ip".
Apparently.
Just to note, the UK's Data Protection Act was in 1998, and you wouldn't tell the end user it's their responsibility to secure it; the caller stuttered a bit when I mentioned that.
Thus, since the "SSS" had found problems, a technician would be sent with a new router, making my IP address secure in future.
However, since there was an individual in Afghanistan using my IP address (how was never explained), they would have to secure all my stuff that I do online, email, banking etc.
So, I needed to log into my accounts whilst connected to the "SSS" to allow them to apply "the securities".
I was actually thankful of ReactOS instability at this point, as I was able to claim I'd checked my accounts before they had managed to reconnect in TeamViewer during the reboot cycle.
They gave up with that, told me my email would be secured if I input a verification code they gave me, and to secure my bank account, they would need my account number.
Playing dumb, I asked why they hadn't got that already, as I was paying them with it.
Transpires they wanted my account login name, not the number.
"I know this is a scam and I've been wasting your time" wasn't the expected login details.
There followed an interesting conversation over what TeamViewer was (apparently it isn't remote desktop unless you select it, and the "SSS" was really a server and not someone on a laptop), how their scam worked, and since I knew they were fraudulent, why did I give them TeamViewer details?
"To waste your time" and "Did you not notice it was a ReactOS VM?" didn't go over well, and me calling them scamming fraudsters preying on unsuspecting victims made them hang up.
I find it strange that they didn't twig I knew what I was doing when they saw "ReactOS", but hey ho.
Handily I got their TeamViewer ID, so if anything they might get barred from the service.
4/10, wouldn't use again.
Change of tack this time; I used a ReactOS VM.
Typing URLs into the ReactOS run box doesn't do anything, and unfortunately the initial try of AnyDesk failed.
TeamViewer was the next try, and since I'd already installed it, it worked fine.
I was told to hang up the call and their technical support department would call me back, which was interesting as they'd already said they were call from the technical support department.
I opened some music, and left the phone next to the speaker for a bit: this didn't improve the mood of the caller, who told me to hang up "properly".
They did call me back about 30 seconds later, and logged in.
It was at this point the alpha quality of ReactOS kicked in, and promptly froze up, requiring a restart: this was a frequent recurrence, and allowed me to be "Very annoyed that their software was crashing my computer".
With the "secure security server (SSS)" connected, "it" ran a scan.
It did upset the "SSS" though, as the `dir /s` command completed far quicker than they wanted, and I was able to watch them type in the scan "failure" notice.
"ip hacked router is malfunctioning. email banking and otehr sensitive data is not secure and needs to be secured as per data protection act 2013.. also eligibe for 200 GBP refund"
...
"Bad command or filename -- ip".
Apparently.
Just to note, the UK's Data Protection Act was in 1998, and you wouldn't tell the end user it's their responsibility to secure it; the caller stuttered a bit when I mentioned that.
Thus, since the "SSS" had found problems, a technician would be sent with a new router, making my IP address secure in future.
However, since there was an individual in Afghanistan using my IP address (how was never explained), they would have to secure all my stuff that I do online, email, banking etc.
So, I needed to log into my accounts whilst connected to the "SSS" to allow them to apply "the securities".
I was actually thankful of ReactOS instability at this point, as I was able to claim I'd checked my accounts before they had managed to reconnect in TeamViewer during the reboot cycle.
They gave up with that, told me my email would be secured if I input a verification code they gave me, and to secure my bank account, they would need my account number.
Playing dumb, I asked why they hadn't got that already, as I was paying them with it.
Transpires they wanted my account login name, not the number.
"I know this is a scam and I've been wasting your time" wasn't the expected login details.
There followed an interesting conversation over what TeamViewer was (apparently it isn't remote desktop unless you select it, and the "SSS" was really a server and not someone on a laptop), how their scam worked, and since I knew they were fraudulent, why did I give them TeamViewer details?
"To waste your time" and "Did you not notice it was a ReactOS VM?" didn't go over well, and me calling them scamming fraudsters preying on unsuspecting victims made them hang up.
I find it strange that they didn't twig I knew what I was doing when they saw "ReactOS", but hey ho.
Handily I got their TeamViewer ID, so if anything they might get barred from the service.
4/10, wouldn't use again.
Excuse the test reply... =)