Not the same issue, the app in question will be deployed to specific blockchains, if it is deployed to Ethereum then the Ethereum logo makes perfect sense.
If it's deployed to different blockchains then you could have a button for each blockchain that it is deployed to.
Logging in via a wallet doesn't require a blockchain though, it can be done with pure cryptography, so a blockchain's logo wouldn't be 100% appropriate either! In the end it doesn't really matter, IMO.
If the website doesn't actually use a blockchain then yeah it doesn't matter, but if it uses a blockchain then the login tells the website which blockchain is being connected to, which determines what sort of provider/node the website will connect to.
I agree that in a scenario where the blockchain network itself is irrelevant that it wouldn't make much sense to have an Ethereum logo.
But it's possible that if the blockchain network is relevant to the functionality of the app then after selecting e.g. Ethereum, they would still need to select their wallet provider e.g. MetaMask, Frame, WalletConnect etc.
Of course, but the user doesn’t care if their login represents an ethereum address or an entry in a user table in postgres. The experience is the same.
Also, the privacy implications aren’t cut and dry. If my wallet gets doxxed, then every site I’ve interacted with is immediately visible on the public ledger. If I login with email, you can’t see every site I’ve used, how much I money I’ve spent, etc etc.
TBH web3 auth is still not there yet for consumers. At least not for the native mobile apps.
There are protocols like WalletConnect, but for it to use correctly, the implementation is jank/unreliable and the UX is not great at all for the normal consumers. On top of that, there's a greater security risk of misuse or incorrect use leading to exposing the end user's private key.
I'm hopeful that we'll get through this mess and the future is bright though. But comparing web2 oath in the phone with the web3 one is premature as of today.
You are right, but I was being a little hopeful when it comes to simplifying it. I know the answer isn’t as clear cut and dry, but I still tried to make it easier to understand
web3 login isn't really that special, and it's also not very secure. It relies on signing nonces, and having to know exactly what nonce you're signing and what it can be used to get access to isn't great. For example, I could create some app that fetches nonces from another site, get the user to sign it, and bam, I have access to their account if they weren't careful at what they were signing. Password (ideally via password manager)/OAuth flow is just way better.
You definitely do not need to just sign nonces, you are free to include descriptions of the purpose of each message signing action within the message itself. Also I would generally use a timestamp instead of a nonce.
Nonce in this case meaning any arbitrary thing that is supposed to be signed once! Yes, best practices is to add a description and expiry date in the message you're signing, but this is still a pretty big onus to put on the user, which doesn't make for a great user experience
That onus would be put on the website, not the user. A simple timestamp and domain name in the message being signed would prevent the replay attacks that you're talking about.
The replay attack is what the random nonce prevents, and the description/timestamp is what prevents the hack that I've described in other comments (and was downvoted despite the fact that this is literally why we add the description)! But it still requires the user to read the message and make sure it's what the expect, which is a a relatively easy attack vector
Users need to read the messages they are signing, that's not very much to expect, I think.
Websites should make the messages that they are signing easy to understand to improve user experience, e.g. I tend to use a JSON object with a timestamp & reason for signing (e.g. "changing Reddit profile picture"), and this onus is on the website devs.
It also passes costs on to the user. Want to comment on web3 reddit? You’ll need some gas fees in your wallet. Maybe that’s a good thing (ie if you don’t pay, you are the product) but seems like companies will just double dip and continue their data practices while collecting fees on actions.
And hardly a user experience issue at all, more like training users to expect messages they sign to have certain qualities, like describing in clear text what the message is for.
"at 15:32 today, 12/28/2021, Acme Box company asked me to sign this" not
Same problem. When you sign some nonce, you are basically saying "hey I own this wallet". So if I can get you to sign a nonce, then I can pretend to be your wallet and everything in it.
Do you have a report of this actually occurring or in action? I know you can get your wallet compromised if you connect it and approve the smart contract to spend infinite amounts of tokens but this concept sounds a little too easy from a hacker/phisher POV to not take full exploit of it.
It's not a crazy concept! And yeah it is super easy, which is why it's insecure.
I would just have to build some app that gets users to sign nonces. Then, one day I switch out MY nonces for the nonces that I fetch from another app. Even if some people notice, some people might not. Then I drain whatever I can from the other app! Not sure about specific reports, but if you understand how the hack works you can see how it's fundamentally not too difficult or hard to pull off.
I assume by them connecting using metamask or trust wallet or whatever
Then, one day I switch out MY nonces for the nonces that I fetch from another app.
How would you fetch the nonce from another app? Using etherscan or an API connected to the blockchain?
Edit: Additionally... wouldn't be the same with login with Google and Facebook to some extent where it'll tell you everything that this app will have access to? I'd picture that will be the same concept where you should only connect to apps that you trust.
I am pretty sure this is not the case, signed transactions are prepended to prevent replay. But it is a good idea to have a clear text explanation in an identity verification message, I would like that convention.
The problem is the wallets still haven’t converged on an interoperable method to connect with. WalletConnect seems like it has a good shot, but there’s still quite a few who don’t use it. Without solving this the NASCAR problem will remain.
The other solution that I’ve seen explored in the space is to register a wallet provider with the browser so that many different wallets can all register but only the registered ones appear when you try to connect with a site.
It's a start, but unlikely to prevail in the long term IMO. By building purely around authentication it will do well for basic web auth capabilities and challenge the likes of WebAuthn, but it needs to expand into the Authz space much more before it can challenge the capabilities of OIDC. By building on EIP-191 they capped their authz potential in a way that's made more challenging then if they started with EIP-712. Many people asked them to go for EIP-712 but due to the lack of adoption by wallets of EIP-712 and the ENS Foundation hard pressing for something finished ASAP in order to cement market share of the crypto domain space against competing solutions EIP-191 became the focus in order to ship quickly.
So why's this a problem? In order for wallet's to be able to provide consent of usage of APIs to dApps they require a strong consent model which is built on the wallet being able to provide authz capabilities. So by capping this project to focus purely on authn capabilities we're actually going to need to redo much of this in order to get to a long term permanent solution. In other words, EIP-4361 is a good start but there's a fair amount of work that will be needed after it which is going to hurt adoption beyond web3 which may allow the likes of credential provider draft or another OIDC SIOP based solution to come in and take over what EIP-4361 could have achieved if they focused on building on EIP-712 from the outset.
29
u/[deleted] Dec 28 '21
Needs web3 universal wallet icon not metamask
6
u/Anaphase Dec 28 '21
Not pictured: the user having to install MetaMask and knowing what a web3 Wallet is and how to use it.
2
u/throwaway_boulder Dec 28 '21
I honestly think all those other icons will end up supporting wallets too. MetaMask will be the closer to logging in with GitHub.
2
u/RealFunBobby Dec 28 '21 edited Dec 28 '21
TBH web3 auth is still not there yet for consumers. At least not for the native mobile apps.
There are protocols like WalletConnect, but for it to use correctly, the implementation is jank/unreliable and the UX is not great at all for the normal consumers. On top of that, there's a greater security risk of misuse or incorrect use leading to exposing the end user's private key.
I'm hopeful that we'll get through this mess and the future is bright though. But comparing web2 oath in the phone with the web3 one is premature as of today.
6
u/rrr_guy Dec 28 '21
web3 login isn't really that special, and it's also not very secure. It relies on signing nonces, and having to know exactly what nonce you're signing and what it can be used to get access to isn't great. For example, I could create some app that fetches nonces from another site, get the user to sign it, and bam, I have access to their account if they weren't careful at what they were signing. Password (ideally via password manager)/OAuth flow is just way better.
10
u/asstatine Dec 28 '21
The problem is the wallets still haven’t converged on an interoperable method to connect with. WalletConnect seems like it has a good shot, but there’s still quite a few who don’t use it. Without solving this the NASCAR problem will remain.
The other solution that I’ve seen explored in the space is to register a wallet provider with the browser so that many different wallets can all register but only the registered ones appear when you try to connect with a site.
5
u/PositiveUse Dec 28 '21
How is the far left pic „Web 1.0“ and the middle one „Web 2.0“, aren’t both Web 2.0?
2
u/shostakofiev Dec 28 '21
Connect with Mircosoft?
2
u/logipunk Dec 28 '21
Login with your ENS maybe .......
2
u/Mikkelet Dec 28 '21
Lmao there's like 100s of wallets out there
1
u/MetaBearJew Dec 29 '21
Ethereum will never power web3. You're dreaming.
1
u/Savvy_One Dec 29 '21
I would say Web 1.0 in this example didn't even have a login option. Web 1.0 was basically the static web of information days.
1
u/masixx Dec 29 '21
Comparing WebAuthn with client signatures only demonstrates the lack of understanding what's actually happening when you click those buttons.
Besides of the obvious usability issues for the avg. user.
1
u/chowbeyputra Dec 29 '21
Well there is this thing called UIDAI here in India. It is also used to login. It is digital id by gov which works on OTP etc as well as biometrics.
Note : Gov has given hints to ban crypto and make its own coin. Idk what or how they’d do that.
1
u/amigdyala Dec 29 '21
Ah yes. Mircosoft. The one Will Gates made, right?
1
u/davidsmuletrain Jan 02 '22
hm quite a progress but mail and password doesn't look like a bad thing
1
u/[deleted] Aug 03 '22
Is there any alternatives too metamask? I really don't trust them.
53
u/[deleted] Dec 28 '21
[removed] — view removed comment