receiving sms codes is an old problem for curve, such tricks could help:
Not clear how an SMS to my phone - the very same device that is running the App I’m trying to log into - is more convenient if I’m somewhere with not very good mobile signal. I know (or can record locally) my password. I can access email via any Internet connection.
That’s before we consider “more secure” and the relative ease of taking over someone’s mobile phone number.
Still the same. Uninstalled, logged in with magic link, prompted to confirm phone, received SMS, prompted to create passcode that can’t confirm. This time more screenshots.
Have you stopped supporting the version with Apple Watch app? Since 3.7.1 that I don’t get a new beta…
Hi @HNF-01 ,
We would suggest not to post your account related sensitive information post here.
We have manually fixed your account.
You should be able to complete the swapover flow now.
The issue was because of the way [with and without country code] you had entered phone number in past and now which appeared to be two different numbers in our system.
@razzz Sorry for this: we are working on bringing it back to beta test stage but we haven’t been including it in recent betas because of some issues with build tooling
Works now !
Hi @Mattia we think you were missing from the feature flag segment we were using. Are you able to try a fresh install and try again?
Now work, thank you
Had this yesterday when I went to use the app - I thought it would only happen if I logged out and back in but it seemed to force me to complete it. Was a bit touch and go for mobile reception in that store but thankfully the SMS managed to get through. Android version was able to autoread and complete the code too.
These statements seem pretty incompatible to me. SMS authentication is pretty widely acknowledged to be the weakest form of 2FA (though still better than password-only). Here it looks like SMS being used as the only factor (no password needed), which is a really bad idea.
SMS is a lot easier to hijack than email, so this seems strictly less secure than either password or magic link via email. Am I missing something here?
SMS?! Seriously? Is it 1998? The world is moving away from SMS authentication which is epically unsafe (just google ss7 sms hack). What you should be doing is moving towards TOTP ( RFC 6238), like Google Authenticator or Authy. Why are you intentionally putting your users at risk of getting hacked?!
Yep I use Authenticator Plus on Android and it’s excellent
Hi, not sure what’s now happening, but no matter what I do with the app, I get it acting as if it’s the first time I’ve ever done so…
It does that to me sometimes after app update. However it clears pretty quickly within 10-15 seconds of opening the app.
Yours seem like something more perhaps , best open a ticket with firstname.lastname@example.org
When release the new beta update?
A Really Bad Idea™
Both for security reasons plus lack of cell coverage in many places where I frequently use Curve, such as supermarkets (where I normally connect to their WiFi instead) etc.
I really hope you’ll reconsider this move.
Rather than signing in with your email and password (or magic link), you will instead be asked to enter your mobile number and the verification code we send via SMS.
I would prefer to stay with secure methods of logging in, thank you.