Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add gnome keyring functionality #204

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ikreb7
Copy link
Contributor

@ikreb7 ikreb7 commented Oct 1, 2020

This is only a first proposal. I want to put the PR up for discussion. With the virtual environment, we could solve the problem with missing pip modules. With the module keyring we could support GNOME Keyring and KWallet.

@twoln What do you think?

@twoln
Copy link
Contributor

twoln commented Nov 2, 2020

I have experimented with the keyring some time ago and was quite disappointed. The main problem seemed to be that if the user did not have the keyring set up, the workflow for this user was getting quite complicated. What I failed to see was the actual added value from the security side. once the machine is copromised pretty much everything can be taken out of it.

@ikreb7
Copy link
Contributor Author

ikreb7 commented Nov 3, 2020

It is definitely better than the current variant. Here are some pros gnome wiki.

We get very much complains about this topic.

@twoln
Copy link
Contributor

twoln commented Nov 3, 2020

I would argue that in the case of a single-user laptop the only attack that this thing really protects from is reading the password from the disk (if the disk is not encrypted). Still I have nothing against supporting this but it will require quite a bit of testing.

@twoln
Copy link
Contributor

twoln commented Nov 3, 2020

the way I get the keyring to work is by just setting s_8021x_data['password-flags'] = 1 instead of 0. The rest seems to be done "by magic", the password gets pushed into the keyring and the connection just works. What I remember from my old tests was that after a new install the keyring was not innitiated and this was causing problems as the initialization process started popping up and was conflicting with the rest of the flow. Can you explain why you need all this code?
This was tested on Ubuntu 20.04 therefore might not be so easy on other distros.

@twoln
Copy link
Contributor

twoln commented Nov 12, 2020

I have so far tested Ubuntu, Mint (Gnome) and OpenSUSE (both Gnome and KDE). I have set the flags to 1 and it worked with the keyring each time. On new installation the keyring needs to be initialized, this may be a bit confusing for the users.
It would be quite easy to ask the user for a choice (like in the NM interface - password for the current user or password for all). This would require the extra screen, other than that no extra code is needed.
More testing required though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants