The person he dealt with told him he had failed the security questions because he hadn't specified which letters in his password were upper or
liz@poppyrecords.invalid.invalid (Liz Tuddenham) writes:
The person he dealt with told him he had failed the security questions
because he hadn't specified which letters in his password were upper or
This is the kind of denial of service attack pioneered by
Vodafone. Eventually all companies will be like this.
or [lower case]The person he dealt with told him he had failed the security questions
because he hadn't specified which letters in his password were upper
Meanwhile I checked Plusnet's fault reporting page and found that they
only accepted written reports by text and not by e-mail. They claim to 'phone back within some specified time to let you know when they will be doing the repairs. How they expect someone with a faulty 'phone to text
them and receive a reply is beyond me.
On 02/03/2026 14:57, Richmond wrote:
liz@poppyrecords.invalid.invalid (Liz Tuddenham) writes:
The person he dealt with told him he had failed the security
questions because he hadn't specified which letters in his password
were upper or >> This is the kind of denial of service attack
pioneered by >> Vodafone. Eventually all companies will be like
this.
I would be concerned if 'a' was accepted instead of 'A' in either an
online login, or in a phone-based security check.
I doubt that the report
" >> The person he dealt with told him he had failed the security
questions >> because he hadn't specified which letters in his password
were upper or [lower case] "
is accurate - the support person will not know if that was the reason,
they will just see 'fail'
jkn <jkn+nin@nicorp.co.uk> writes:
On 02/03/2026 14:57, Richmond wrote:
liz@poppyrecords.invalid.invalid (Liz Tuddenham) writes:
The person he dealt with told him he had failed the security
questions because he hadn't specified which letters in his password
were upper or >> This is the kind of denial of service attack
pioneered by >> Vodafone. Eventually all companies will be like
this.
I would be concerned if 'a' was accepted instead of 'A' in either an
online login, or in a phone-based security check.
I doubt that the report
" >> The person he dealt with told him he had failed the security
questions >> because he hadn't specified which letters in his password
were upper or [lower case] "
is accurate - the support person will not know if that was the reason,
they will just see 'fail'
The support would have needed to know whether it was upper or lower case
in order to type it in, they wouldn't need to get as far as a pass or
fail.
On 02/03/2026 13:27, Liz Tuddenham wrote:
Meanwhile I checked Plusnet's fault reporting page and found that they
only accepted written reports by text and not by e-mail. They claim to 'phone back within some specified time to let you know when they will be doing the repairs. How they expect someone with a faulty 'phone to text them and receive a reply is beyond me.
They probably assume most people have a mobile phone, and can find out or already know about 07800008121. They may then send urls in the text
messages about a thefault, assuming that you have 4g/5g coverage too.
On 02/03/2026 17:13, Richmond wrote:
jkn <jkn+nin@nicorp.co.uk> writes:
On 02/03/2026 14:57, Richmond wrote:
liz@poppyrecords.invalid.invalid (Liz Tuddenham) writes:
The person he dealt with told him he had failed the security
questions because he hadn't specified which letters in his password
were upper or >> This is the kind of denial of service attack
pioneered by >> Vodafone. Eventually all companies will be like
this.
I would be concerned if 'a' was accepted instead of 'A' in either an
online login, or in a phone-based security check.
I doubt that the report
" >> The person he dealt with told him he had failed the security
questions >> because he hadn't specified which letters in his password
were upper or [lower case] "
is accurate - the support person will not know if that was the reason,
they will just see 'fail'
The support would have needed to know whether it was upper or lower case
in order to type it in, they wouldn't need to get as far as a pass or
fail.
Perhaps they should say 'make sure you tell me the correct case' - but
if the attempt fails with the supplied values they will have no
knowledge of whether those supplied letters/digits were simply 'wrong',
or 'the wrong case'. All they will have is 'attempt failed'. That is why
I doubt the report.
jkn <jkn+nin@nicorp.co.uk> wrote:
On 02/03/2026 17:13, Richmond wrote:
jkn <jkn+nin@nicorp.co.uk> writes:
On 02/03/2026 14:57, Richmond wrote:
liz@poppyrecords.invalid.invalid (Liz Tuddenham) writes:
The person he dealt with told him he had failed the security
questions because he hadn't specified which letters in his password >>>>>> were upper or >> This is the kind of denial of service attack
pioneered by >> Vodafone. Eventually all companies will be like
this.
I would be concerned if 'a' was accepted instead of 'A' in either an
online login, or in a phone-based security check.
I doubt that the report
" >> The person he dealt with told him he had failed the security
questions >> because he hadn't specified which letters in his password >>>> were upper or [lower case] "
is accurate - the support person will not know if that was the reason, >>>> they will just see 'fail'
The support would have needed to know whether it was upper or lower case >>> in order to type it in, they wouldn't need to get as far as a pass or
fail.
Perhaps they should say 'make sure you tell me the correct case' - but
if the attempt fails with the supplied values they will have no
knowledge of whether those supplied letters/digits were simply 'wrong',
or 'the wrong case'. All they will have is 'attempt failed'. That is why
I doubt the report.
My neighbour is well into his late 80's and didn't even know the correct terminology for upper and lower case. Even then, the Pusnet operator
could have asked whether the letters were big or small and typed them accordingly.
Nick Finnigan <nix@genie.co.uk> wrote:
On 02/03/2026 13:27, Liz Tuddenham wrote:
Meanwhile I checked Plusnet's fault reporting page and found that they
only accepted written reports by text and not by e-mail. They claim to
'phone back within some specified time to let you know when they will be >>> doing the repairs. How they expect someone with a faulty 'phone to text >>> them and receive a reply is beyond me.
They probably assume most people have a mobile phone, and can find out or
already know about 07800008121. They may then send urls in the text
messages about a thefault, assuming that you have 4g/5g coverage too.
That's one way of doing it but it shouldn't be the only one.
On 02/03/2026 18:25, Liz Tuddenham wrote:
jkn <jkn+nin@nicorp.co.uk> wrote:
On 02/03/2026 17:13, Richmond wrote:
jkn <jkn+nin@nicorp.co.uk> writes:
On 02/03/2026 14:57, Richmond wrote:
liz@poppyrecords.invalid.invalid (Liz Tuddenham) writes:
The person he dealt with told him he had failed the security
questions because he hadn't specified which letters in his password >>>>>> were upper or >> This is the kind of denial of service attack
pioneered by >> Vodafone. Eventually all companies will be like
this.
I would be concerned if 'a' was accepted instead of 'A' in either an >>>> online login, or in a phone-based security check.
I doubt that the report
" >> The person he dealt with told him he had failed the security
questions >> because he hadn't specified which letters in his password >>>> were upper or [lower case] "
is accurate - the support person will not know if that was the reason, >>>> they will just see 'fail'
The support would have needed to know whether it was upper or lower case >>> in order to type it in, they wouldn't need to get as far as a pass or
fail.
Perhaps they should say 'make sure you tell me the correct case' - but
if the attempt fails with the supplied values they will have no
knowledge of whether those supplied letters/digits were simply 'wrong',
or 'the wrong case'. All they will have is 'attempt failed'. That is why >> I doubt the report.
My neighbour is well into his late 80's and didn't even know the correct terminology for upper and lower case. Even then, the Pusnet operator
could have asked whether the letters were big or small and typed them accordingly.
I agree - but they cannot have meaningfully been told that that was the
cause of the failure. Perhaps the Plusnet Operator said something like
"if you say a big letter instead of a small one, it will fail"...
From what I overheard of the conversation, the operator just typed in
the password and said "That failed so I shall have to ask you some more questions". When he started asking about recemt bills and bank details
my neighbour said he could only answer that by going to his bank; I
gather the operator told hm that was what he would have to do. Then my neighbour asked if he could give the password again, this time with big
and small letters and the operator said he couldn't.
It wasn't as if this was a high-security situation, my neighbour just
wanted to report a faulty line.
They probably assume most people have a mobile phone, and can
find out or
On Mon, 2 Mar 2026 20:39:43 +0000
"J. P. Gilliver" <G6JPG@255soft.uk> wrote:
They probably assume most people have a mobile phone, and can
find out or
And all the institutions who only use 'apps' and only provide squiggly
little boxes of pixels to let you contact them.
On 2026/3/2 22:17:29, Liz Tuddenham wrote:
[]
From what I overheard of the conversation, the operator just typed inThat last is the kicker. That shouldn't need _any_ security check -
the password and said "That failed so I shall have to ask you some more
questions". When he started asking about recemt bills and bank details
my neighbour said he could only answer that by going to his bank; I
gather the operator told hm that was what he would have to do. Then my
neighbour asked if he could give the password again, this time with big
and small letters and the operator said he couldn't.
It wasn't as if this was a high-security situation, my neighbour just
wanted to report a faulty line.
since the existence of the faulty line could be verified by (trying to)
call it, and/or doing whatever tests they'd normally do on a line.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 59 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 24:11:26 |
| Calls: | 810 |
| Calls today: | 1 |
| Files: | 1,287 |
| D/L today: |
12 files (21,036K bytes) |
| Messages: | 195,978 |