Adrian Caspersz <
[email protected]d> wrote:
On 12/05/2022 17:21, Adrian Caspersz wrote:
These _only_ can be used to get back into the account.
However, print it out. Give it to the dog to eat, and then you'll have
your secure account.
Ah, I see Paypal are asking for answers for two previously chosen questions.
Be creative, don't have to be so truthful.
This is the part that trips many up with the "recovery questions".
They take the questions too literal.
Give them the name ya first pet as 'Donald Trump' and ya first school
as 'School of Life'.
Or use a long string of random characters in ya answers and give the
poor sod on the phone a hard time rekeying them.
I've seen reports (sorry, no longer remember what blog/site for
citations) that when calling and talking to customer service reps, that attackers can get the service rep to "bypass" the "long string of random characters" by telling the rep something like: "I just banged out a
bunch of random keys" and the service rep. accepts that as an answer.
So better to use a random assemblage of words, then at least you might
be protected from someone sweet-talking their way past a customer
service rep.
What I do for those questions, for sites that demand them, is this:
$ sort --random-sort --random-source=/dev/urandom /usr/dict/words | head -5 | tr $'\n' " " ; echo
cottonseed suction architect supplants highways
And then "cottonseed suction architect supplants highways" goes in the
field, and in the notes box in my password manager for the site's
entry, so later, if needed, I have a record of what was used. Adjust
size given to "head" for number of words desired.
Hopefully someone sweet-talking with "just mashed random keys" won't be
allowed past by the service rep. And hopefully by being real words,
the rep. will insist on the attacker repeating the actual words.
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)