Multiple user credentials possibility in FDP and FairOS

[asabya]

The current implementation of authentication stores the user account info in an SOC with the topic VERSION+USERNAME+PASSWORD.

Currently fairOS does not allow the owner to re-register, but potentially it can, with different password and have different SOCs. This will let the user login into his/her account with multiple passwords.

Steps to reproduce

1. Signup
2. Use the same mnemonic and user name with different password to signup

Should we allow this?

[crtahlin]

This implies I could login with same username but different passwords and I would see different content in my Fairdrive?

[asabya]

No, you will see the same content.

[tamas6]

I think the idea is similar to more fingerprint recognition for your device, which is convenient.

If the case is to implement fingerprint, facial recognition, or voice, -why not!– as user credentials, they could be stored as different password values. Right? btw the market is moving toward passwordless but biometric authentication apps/services, I think it's scary

[darkobas2]

That solely depends on ability to disable/deleting one of the passwords if it gets compromised.... And an ability to see and manage passwords and or access logs. If not is a big security concern.

[asabya]

I was against this, but now that I think of pros we can have two opportunities here.

• With this same exact feature we can introduce Forget/Reset password. Sure you can exploit signup and have multiple passwords for the same account. But for Reset password we would write garbage content into old SOC and upload the new SOC.

• We introduce task specific username. Just add a plus sign (+) and any word after your username.
  For example if I have a portable account called fips, I re-register with fips+fairdrive with my old mnemonic (to state I am the owner of fips). This will not do a ens registration but will create a different mnemonic/seed for a new/different account. That means

This implies I could login with same username but different passwords and I would see different content in my Fairdrive?

this will be archived.

[molekilla]

I don't like it. We need to have recovery kits or guardian eg like Argent or Loopring

[crtahlin]

I think a general solution for account management should be found (password change, password recovery). Also, changing my mind - it is weird for the user to have several accounts for the same data storage. And also much harder for the user to maintain from security perspective (any of the passwords could leak - you need to manage them all).

@tfius let's start a spec arround how account management should look like?

[molekilla]

Let's spec this using BeeSon. Something like this: https://cryptobook.nakov.com/symmetric-key-ciphers/ethereum-wallet-encryption Recovery is another thing, we would need to see what approach works for us: Guardians, Backup Code, or plain old mnemonic. More here https://support.argent.xyz/hc/en-us/articles/360007338877-How-to-recover-my-wallet-with-guardians-complete-guide

…

On Fri, Sep 23, 2022 at 3:57 AM Crt Ahlin ***@***.***> wrote: I think a general solution for account management should be found (password change, password recovery). Also, changing my mind - it is weird for the user to have several accounts for the same data storage. And also much harder for the user to maintain from security perspective (any of the passwords could leak - you need to manage them all). @tfius <https://github.com/tfius> let's start a spec arround how account management should look like? — Reply to this email directly, view it on GitHub <#54 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJQWR4UPBFBMMV43GI6RDLV7VWH7ANCNFSM6AAAAAAQBMV6WA> . You are receiving this because you commented.Message ID: ***@***.***>

[molekilla]

@nugaon full spec described by satoshi labs

https://github.com/satoshilabs/slips/blob/master/slip-0039.md

Motivation
Preservation of digital assets is generally important and it is especially important in the case of decentralized payments systems such as Bitcoin, where there is no recourse in the case of loss of an asset. The usual approach to protecting digital assets is redundant backups, but when the asset itself is of significant and liquidable value, there is a substantial risk of the backup holder absconding with the asset. Shamir's secret-sharing provides a better mechanism for backing up secrets by distributing custodianship among a number of trusted parties in a manner that can prevent loss even if one or a few of those parties become compromised.

However, the lack of SSS standardization to date presents a risk of being unable to perform secret recovery in the future should the tooling change. Therefore, we propose standardizing SSS so that SLIP-0039 compatible implementations will be interoperable.