Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.mobile.android > #109819 > unrolled thread
| Started by | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| First post | 2023-11-08 22:57 +0100 |
| Last post | 2023-11-09 07:32 -0700 |
| Articles | 11 on this page of 31 — 4 participants |
Back to article view | Back to comp.mobile.android
I just noticed that paypal uses whatsapp for 2FA now "Carlos E. R." <robin_listas@es.invalid> - 2023-11-08 22:57 +0100
Re: I just noticed that paypal uses whatsapp for 2FA now Jörg Lorenz <hugybear@gmx.net> - 2023-11-09 01:50 +0100
Re: I just noticed that paypal uses whatsapp for 2FA now Jörg Lorenz <hugybear@gmx.net> - 2023-11-09 01:52 +0100
Re: I just noticed that paypal uses whatsapp for 2FA now Dave Royal<dave@dave123royal.com> - 2023-11-09 09:21 +0000
Re: I just noticed that paypal uses whatsapp for 2FA now "Carlos E. R." <robin_listas@es.invalid> - 2023-11-09 11:39 +0100
Re: I just noticed that paypal uses whatsapp for 2FA now Jörg Lorenz <hugybear@gmx.net> - 2023-11-09 12:41 +0100
Re: I just noticed that paypal uses whatsapp for 2FA now "Carlos E. R." <robin_listas@es.invalid> - 2023-11-09 13:05 +0100
Re: I just noticed that paypal uses whatsapp for 2FA now Dave Royal<dave@dave123royal.com> - 2023-11-09 12:36 +0000
Re: I just noticed that paypal uses whatsapp for 2FA now "Carlos E. R." <robin_listas@es.invalid> - 2023-11-09 13:41 +0100
Re: I just noticed that paypal uses whatsapp for 2FA now AJL <noemail@none.com> - 2023-11-09 07:16 -0700
Re: I just noticed that paypal uses whatsapp for 2FA now Dave Royal<dave@dave123royal.com> - 2023-11-09 14:27 +0000
Re: I just noticed that paypal uses whatsapp for 2FA now AJL <noemail@none.com> - 2023-11-09 08:10 -0700
Re: I just noticed that paypal uses whatsapp for 2FA now Dave Royal<dave@dave123royal.com> - 2023-11-09 15:50 +0000
Re: I just noticed that paypal uses whatsapp for 2FA now Dave Royal<dave@dave123royal.com> - 2023-11-09 15:57 +0000
Re: I just noticed that paypal uses whatsapp for 2FA now AJL <noemail@none.com> - 2023-11-09 09:21 -0700
Re: I just noticed that paypal uses whatsapp for 2FA now "Carlos E. R." <robin_listas@es.invalid> - 2023-11-09 20:15 +0100
Re: I just noticed that paypal uses whatsapp for 2FA now AJL <noemail@none.com> - 2023-11-09 19:49 +0000
Re: I just noticed that paypal uses whatsapp for 2FA now "Carlos E. R." <robin_listas@es.invalid> - 2023-11-09 21:30 +0100
Re: I just noticed that paypal uses whatsapp for 2FA now AJL <noemail@none.com> - 2023-11-09 14:23 -0700
Re: I just noticed that paypal uses whatsapp for 2FA now "Carlos E. R." <robin_listas@es.invalid> - 2023-11-09 22:28 +0100
Re: I just noticed that paypal uses whatsapp for 2FA now AJL <noemail@none.com> - 2023-11-09 15:08 -0700
Re: I just noticed that paypal uses whatsapp for 2FA now AJL <noemail@none.com> - 2023-11-09 09:07 -0700
Re: I just noticed that paypal uses whatsapp for 2FA now Dave Royal<dave@dave123royal.com> - 2023-11-09 16:35 +0000
Re: I just noticed that paypal uses whatsapp for 2FA now AJL <noemail@none.com> - 2023-11-09 10:43 -0700
Re: I just noticed that paypal uses whatsapp for 2FA now "Carlos E. R." <robin_listas@es.invalid> - 2023-11-09 20:20 +0100
Re: I just noticed that paypal uses whatsapp for 2FA now AJL <noemail@none.com> - 2023-11-09 14:23 -0700
Re: I just noticed that paypal uses whatsapp for 2FA now "Carlos E. R." <robin_listas@es.invalid> - 2023-11-09 22:31 +0100
Re: I just noticed that paypal uses whatsapp for 2FA now AJL <noemail@none.com> - 2023-11-09 15:08 -0700
Re: I just noticed that paypal uses whatsapp for 2FA now "Carlos E. R." <robin_listas@es.invalid> - 2023-11-09 23:23 +0100
Re: I just noticed that paypal uses whatsapp for 2FA now AJL <noemail@none.com> - 2023-11-09 15:43 -0700
Re: I just noticed that paypal uses whatsapp for 2FA now AJL <noemail@none.com> - 2023-11-09 07:32 -0700
Page 2 of 2 — ← Prev page 1 [2]
| From | AJL <noemail@none.com> |
|---|---|
| Date | 2023-11-09 15:08 -0700 |
| Message-ID | <uijl8l$2dmkj$2@dont-email.me> |
| In reply to | #109886 |
On 11/9/2023 2:28 PM, Carlos E. R. wrote: > On 2023-11-09 22:23, AJL wrote: > Criminals do those things. I'm not one of them, so I don't know how. Ok, got the lack of subject knowledge admission... > Sites are breached, And people are careless choosing and keeping their PWs. > passwords sold and circulated. (Sh)it happens. That's why 2FA is in use. > Seems to be just a matter of time. Not for me... >> How would they get my username/password. Please no more magic... > Ask them bad guys. So far they're falling down on the job with my stuff...
[toc] | [prev] | [next] | [standalone]
| From | AJL <noemail@none.com> |
|---|---|
| Date | 2023-11-09 09:07 -0700 |
| Message-ID | <uij04f$295hk$1@dont-email.me> |
| In reply to | #109855 |
On 11/9/2023 8:50 AM, Dave Royal wrote: > On 9 Nov 2023 08:10:33 -0700 AJL wrote: >> On 11/9/2023 7:27 AM, Dave Royal wrote: >>> On 09 Nov 2023 07:16:19 -0700 AJL wrote: >>>> Dave Royal<dave@dave123royal.com> wrote: >> >>>>> Amex sends 2FA codes by _both_ SMS and email which is about >>>>> as insecure as you get. And it doesn't ask which I prefer. >> >>>> My Android AMEX app gives me a 2FA CHOICE between text, email, >>>> or a voice phone call. You might recheck yours, perhaps it's >>>> changed... >> >>> I don't use an Amex app - this is with their website. >> >> I just checked it on my AMEX website. They still gave me the same >> three CHOICES (text, email, or voice). I'm in the US. Perhaps >> that's the difference? > > Maybe. > >> BTW I use text. A one time code good for only minutes. Where's the >> big security risk? > > SIM swap fraud. How would a SIM swap get a perp into my AMEX account? He would need my AMEX user name and password to even get the text code. And where does he get that? So I ask again, where's the big security risk in texting a 2FA code?
[toc] | [prev] | [next] | [standalone]
| From | Dave Royal<dave@dave123royal.com> |
|---|---|
| Date | 2023-11-09 16:35 +0000 |
| Message-ID | <uij1o7$29g9i$1@dont-email.me> |
| In reply to | #109857 |
On 9 Nov 2023 09:07:41 -0700 AJL wrote: >On 11/9/2023 8:50 AM, Dave Royal wrote: >> On 9 Nov 2023 08:10:33 -0700 AJL wrote: >>> On 11/9/2023 7:27 AM, Dave Royal wrote: >>>> On 09 Nov 2023 07:16:19 -0700 AJL wrote: >>>>> Dave Royal<dave@dave123royal.com> wrote: >>> >>>>>> Amex sends 2FA codes by _both_ SMS and email which is about >>>>>> as insecure as you get. And it doesn't ask which I prefer. >>> >>>>> My Android AMEX app gives me a 2FA CHOICE between text, email, >>>>> or a voice phone call. You might recheck yours, perhaps it's >>>>> changed... >>> >>>> I don't use an Amex app - this is with their website. >>> >>> I just checked it on my AMEX website. They still gave me the same >>> three CHOICES (text, email, or voice). I'm in the US. Perhaps >>> that's the difference? >> >> Maybe. >> >>> BTW I use text. A one time code good for only minutes. Where's the >>> big security risk? >> >> SIM swap fraud. > >How would a SIM swap get a perp into my AMEX account? He would need my >AMEX user name and password to even get the text code. And where does he >get that? > >So I ask again, where's the big security risk in texting a 2FA code? The point of two factor authentication is to add a _second_ layer of security so that if your account/password is stolen - which happens a lot in data breaches - there must be a second 'token' - something you _have_. With SIM swap fraud the malefactors effectively have your phone and can get the code. I wouldn't say it's a /big/ risk but it's a risk if a large financial tranfer depends on it. Banks implemented it 'cos it was cheap to do. SIM swap fraud was becoming serious a year or so back in the UK but I think operators are supposed to carry out more checks now before providing replacement SIMs. As for WhatsApp, an account can have up to 6(?) linked devices, so presumably the code will appear on all of them. I can imagine a new attack - 'clandestine WA device linking' whereby someone with brief physical access to your mobile links another device to it. -- (Remove numerics from email address)
[toc] | [prev] | [next] | [standalone]
| From | AJL <noemail@none.com> |
|---|---|
| Date | 2023-11-09 10:43 -0700 |
| Message-ID | <uij5on$2adk7$1@dont-email.me> |
| In reply to | #109859 |
On 11/9/2023 9:35 AM, Dave Royal wrote: > On 9 Nov 2023 09:07:41 -0700 AJL wrote: >> So I ask again, where's the big security risk in texting a 2FA >> code? > > The point of two factor authentication is to add a _second_ layer of > security so that if your account/password is stolen - which happens a > lot in data breaches - there must be a second 'token' - something you > _have_. With SIM swap fraud the malefactors effectively have your > phone and can get the code. > > I wouldn't say it's a /big/ risk but it's a risk Everythings a risk. Your risk scenario is infinitesimal IMO... > if a large financial tranfer depends on it. Not a problem. I'm covered for any fraudulent bank transactions that ARE NOT MY FAULT... > Banks implemented it 'cos it was cheap to do. And also it was one more layer of security. > SIM swap fraud was becoming serious a year or so back in the UK but > I think operators are supposed to carry out more checks now before > providing replacement SIMs. I have a security code registered with my phone provider. No business transacted without that code. Course I suppose there's always the inside job thing to worry about for the risk paranoid... > As for WhatsApp, an account can have up to 6(?) linked devices, so > presumably the code will appear on all of them. I can imagine a new > attack - 'clandestine WA device linking' whereby someone with brief > physical access to your mobile links another device to it. Have never used WhatsApp. My whole extended family here uses text... ;)
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-11-09 20:20 +0100 |
| Message-ID | <kr4poqFsdr5U8@mid.individual.net> |
| In reply to | #109859 |
On 2023-11-09 17:35, Dave Royal wrote:
> On 9 Nov 2023 09:07:41 -0700 AJL wrote:
>> On 11/9/2023 8:50 AM, Dave Royal wrote:
>>> On 9 Nov 2023 08:10:33 -0700 AJL wrote:
>>>> On 11/9/2023 7:27 AM, Dave Royal wrote:
...
>>>> BTW I use text. A one time code good for only minutes. Where's the
>>>> big security risk?
>>>
>>> SIM swap fraud.
>>
>> How would a SIM swap get a perp into my AMEX account? He would need my
>> AMEX user name and password to even get the text code. And where does he
>> get that?
>>
>> So I ask again, where's the big security risk in texting a 2FA code?
>
> The point of two factor authentication is to add a _second_ layer of
> security so that if your account/password is stolen - which happens a lot
> in data breaches - there must be a second 'token' - something you _have_.
> With SIM swap fraud the malefactors effectively have your phone and can
> get the code.
>
Right.
So imagine I use the app in the phone to connect to the bank. The bank
sends a code by SMS to the *same* phone, the app reads automatically the
message and logins.
Now suppose my phone is stolen...
> I wouldn't say it's a /big/ risk but it's a risk if a large financial
> tranfer depends on it. Banks implemented it 'cos it was cheap to do.
>
> SIM swap fraud was becoming serious a year or so back in the UK but I
> think operators are supposed to carry out more checks now before providing
> replacement SIMs.
They were fined here for not verifying the identity of the person
getting the sim. So I suppose now they are stricter.
>
> As for WhatsApp, an account can have up to 6(?) linked devices, so
> presumably the code will appear on all of them. I can imagine a new attack
> - 'clandestine WA device linking' whereby someone with brief physical
> access to your mobile links another device to it.
Ah. True.
The code would appear in my phone and in my computer.
Mind, SMS can also be read in the computer if you want. At least with
Google messages. I have not tried, but read about it.
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | AJL <noemail@none.com> |
|---|---|
| Date | 2023-11-09 14:23 -0700 |
| Message-ID | <uijikb$2d473$1@dont-email.me> |
| In reply to | #109869 |
On 11/9/2023 12:20 PM, Carlos E. R. wrote: > imagine I use the app in the phone to connect to the bank. The bank > sends a code by SMS to the *same* phone, > the app reads automatically the message and logins. Doesn't work that way on any of my apps. The 2FA code is sent by text as a number that I then have to then reenter into the app. > Now suppose my phone is stolen... Hopefully your phone AND your phone bank app are BOTH LOCKED. That way the thief has to go through TWO LOCKS to enter your bank app. Pretty unlikely, don't you think... On my phone the 2FA text code only had to authorize the AMEX app ONCE. After that only the user name and PW is required to open the app. (Though AMEX can be set to require a 2FA code on every app entry I find that a bit too much of a hassle for what little added security it may give (IMO-YMMV). I'm still waiting to see why SMS is a poor way to send a 2FA codes. Though I'll admit that pushing "Yes" on a Google Authenticator screen to authorize an app is sure a lot easier...
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-11-09 22:31 +0100 |
| Message-ID | <kr51dmF5kmlU2@mid.individual.net> |
| In reply to | #109884 |
On 2023-11-09 22:23, AJL wrote:
> On 11/9/2023 12:20 PM, Carlos E. R. wrote:
>
>> imagine I use the app in the phone to connect to the bank. The bank
>> sends a code by SMS to the *same* phone,
>
>> the app reads automatically the message and logins.
>
> Doesn't work that way on any of my apps. The 2FA code is sent by text as
> a number that I then have to then reenter into the app.
>
>> Now suppose my phone is stolen...
>
> Hopefully your phone AND your phone bank app are BOTH LOCKED. That way
> the thief has to go through TWO LOCKS to enter your bank app. Pretty
> unlikely, don't you think...
I hope, but could happen.
Some bank apps here use a 4 digit pin code. Others use 8.
>
> On my phone the 2FA text code only had to authorize the AMEX app ONCE.
> After that only the user name and PW is required to open the app.
> (Though AMEX can be set to require a 2FA code on every app entry I find
> that a bit too much of a hassle for what little added security it may
> give (IMO-YMMV).
>
> I'm still waiting to see why SMS is a poor way to send a 2FA codes.
> Though I'll admit that pushing "Yes" on a Google Authenticator screen to
> authorize an app is sure a lot easier...
Well, experts in the field have said so.
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | AJL <noemail@none.com> |
|---|---|
| Date | 2023-11-09 15:08 -0700 |
| Message-ID | <uijl8i$2dmkj$1@dont-email.me> |
| In reply to | #109887 |
On 11/9/2023 2:31 PM, Carlos E. R. wrote: > On 2023-11-09 22:23, AJL wrote: >> Hopefully your phone AND your phone bank app are BOTH LOCKED. That >> way the thief has to go through TWO LOCKS to enter your bank app. >> Pretty unlikely, don't you think... > > I hope, but could happen. By the time a thief could break your locks you could have your passwords changed. My Google stuff (like Gmail) doesn't have a password once you get past my phone lock screen lock. If my phone were stolen I'm counting on that lock screen lock to hold at least an hour or so until I can change my Google password... > Some bank apps here use a 4 digit pin code. Others use 8. Same as above. Change the password quickly if stolen. Then the pin will no longer work. >> I'm still waiting to see why SMS is a poor way to send a 2FA >> codes. > Well, experts in the field have said so. Got me there. But still waiting for a reason why. Though text is unencrypted what good would a timed 6 digit number intercept do anyone? And the good part of using a text is that I'd know IMMEDIATELY if someone's trying to log in to one of my accounts and can take immediate action. Not so with encrypted email...
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-11-09 23:23 +0100 |
| Message-ID | <kr54fsF5kmlU4@mid.individual.net> |
| In reply to | #109892 |
On 2023-11-09 23:08, AJL wrote:
> On 11/9/2023 2:31 PM, Carlos E. R. wrote:
>> On 2023-11-09 22:23, AJL wrote:
>
>>> Hopefully your phone AND your phone bank app are BOTH LOCKED. That
>>> way the thief has to go through TWO LOCKS to enter your bank app.
>>> Pretty unlikely, don't you think...
>>
>> I hope, but could happen.
>
> By the time a thief could break your locks you could have your passwords
> changed.
>
> My Google stuff (like Gmail) doesn't have a password once you get past
> my phone lock screen lock. If my phone were stolen I'm counting on that
> lock screen lock to hold at least an hour or so until I can change my
> Google password...
How? I am on the street, probably, far from home and with no phone.
>
>> Some bank apps here use a 4 digit pin code. Others use 8.
>
> Same as above. Change the password quickly if stolen. Then the pin will
> no longer work.
>
>>> I'm still waiting to see why SMS is a poor way to send a 2FA
>>> codes.
>
>> Well, experts in the field have said so.
>
> Got me there. But still waiting for a reason why. Though text is
> unencrypted what good would a timed 6 digit number intercept do anyone?
If they got your user and password in advance, a lot.
> And the good part of using a text is that I'd know IMMEDIATELY if
> someone's trying to log in to one of my accounts and can take immediate
> action. Not so with encrypted email...
>
>
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | AJL <noemail@none.com> |
|---|---|
| Date | 2023-11-09 15:43 -0700 |
| Message-ID | <uijnb0$2e2uc$1@dont-email.me> |
| In reply to | #109896 |
On 11/9/2023 3:23 PM, Carlos E. R. wrote: > On 2023-11-09 23:08, AJL wrote: >> By the time a thief could break your [phone] locks you could have >> your passwords changed. > How? I am on the street, probably, far from home and with no phone. Guess you're outta luck then. I normally have an (gasp) iPhone nearby (wife's). Then I'm also usually within 30 minutes of home. Guess YMMV (your mileage is a lot bigger than mine) fits better than usual here... ;) >> still waiting for a reason why [text 2FA is bad]. > If they got your user and password in advance, a lot. So how do they get my user name and password? Wait isn't this is where we came in. You can have the last word. It's nap time for me...
[toc] | [prev] | [next] | [standalone]
| From | AJL <noemail@none.com> |
|---|---|
| Date | 2023-11-09 07:32 -0700 |
| Message-ID | <almarsoft.5316242753226342257@news.eternal-september.org> |
| In reply to | #109848 |
AJL <noemail@none.com> wrote: > Dave Royal wrote: > > Amex sends 2FA codes by _both_ > > SMS and email which is about as >> insecure as you get. And it doesn't > ask which I prefer. > My Android AMEX app gives me a > 2FA CHOICE between text, email, or a > voice phone call. You might recheck > yours, perhaps it's changed... > Just stuck my old Android Groundhog > newsreader on an old Amazon > tablet. First post. Newer tablets break > it into read only. So lets see his this > one does... Ah. I see the quote strings were broken. I think I can fix that in this and future posts but it's a PITA. None of my old stuff works anymore, even when used on my old stuff. Test over...
[toc] | [prev] | [standalone]
Page 2 of 2 — ← Prev page 1 [2]
Back to top | Article view | comp.mobile.android
csiph-web