New gnome keyring

[bilelmoussaoui]

Switches #56 to use a branch from this repo so we can easily collaborate on it.

progress to-date:

• [x] D-Bus Secret Service API implementation - complete
• [ ] Default keyring (login.keyring) support - almost complete
• [ ] Multiple keyring support - not done

[warusadura]

Does it make sense to store the session along with an Item. As in,

pub struct Item {
    inner: RwLock<portal::Item>,
    path: OwnedObjectPath,
    keyring: Arc<Keyring>,
    locked: bool,
    session: OwnedObjectPath,
}

and then, store the same session inside Collection,

pub struct Collection {
    keyring: Arc<Keyring>,
    pub(crate) items: RwLock<Vec<super::item::Item>>,
    alias: RwLock<String>,
    label: String,
    locked: AtomicBool,
    created: Duration,
    modified: Duration,
    path: OwnedObjectPath,
    sessions: Vec<OwnedObjectPath>,
}

with this way we get access to all the available sessions and we can retrieve a session based on an objectpath. wdyt?

[bilelmoussaoui]

Does it make sense to store the session along with an Item. As in,

pub struct Item {
    inner: RwLock<portal::Item>,
    path: OwnedObjectPath,
    keyring: Arc<Keyring>,
    locked: bool,
    session: OwnedObjectPath,
}

and then, store the same session inside Collection,

pub struct Collection {
    keyring: Arc<Keyring>,
    pub(crate) items: RwLock<Vec<super::item::Item>>,
    alias: RwLock<String>,
    label: String,
    locked: AtomicBool,
    created: Duration,
    modified: Duration,
    path: OwnedObjectPath,
    sessions: Vec<OwnedObjectPath>,
}

with this way we get access to all the available sessions and we can retrieve a session based on an objectpath. wdyt?

Storing the session is required yes, but not just it ObjectPath. Instead you need to store the Sesssion itself which would contain more information than just the object path. Ideally we can store it as HashMap<OwnedObjectPath, Session>, same thing for collections & items I would say.

[warusadura]

Note: dropped following commits due to this change and rebased.

• client: make key generation methods public and encrypt(): 8dcc58f5af2de7b48fe6005e96c7bcd4f3bb6ad6
• client: make crypto crate public under unstable feature: 145f9644db950635be7a125be47be48b629d0db4
• client: Expose native_crypto API generate_iv() and encrypt(): e694e2e05c8d0696288ad66826038498ef2746ce