If a user wants to login to a system/server, it's recommended to have the hashed&salted password saved in a database, along with its salt.
So the user wants to login, types in the password, clicks on login and with his input and the salt the system checks if the correct hash is created.
I understand this part.
But when I don't want to type the password every time, how would I save the password on client-side? I can't save it hashed, because I need to salt the clear password for the checkup. If I save it clear, the client is vulnerable. And if I use any encryption where do I store the "master-password".
Also in my case I don't really want the user to force into creating a master-password. Though it's a required feature not to type in the password every time.
Well, one question I still have on my mind. How is it done in smartphones? For example your wifi password. You enter it once, it's stored on the device, but how is it secured? Do you know that?