** Changed in: python-keyring (Ubuntu)
Assignee: (unassigned) => Barry Warsaw (barry)
** Changed in: python-keyring (Ubuntu)
Milestone: None => natty-alpha-3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
To be clear, while I don't like 0.5 (or python password handling in
general), I'd still be okay with having it in main, for launchpadlib
(especially as it still supports unencrypted credentials files as well).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Note that my NACK from above referred to the broken and outdated 0.2
version only. I haven't checked 0.5 yet (as it isn't even packaged), and
I didn't look into the upstream code whether there are any improvements
with memory locking.
--
You received this bug notification because you are a member
** Changed in: null
Assignee: Kees Cook (kees) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/686257
Title:
upgrade to python-keyring 0.5 (and MIR)
--
ubuntu-bugs mailing list
Kees, when you have some time can we get your opinion on the python-
keyring module? Specifically this concern noted by Martin:
The main problem that I see here is that it's handling a lot of
passwords, and doesn't use any kind of mlock()-like protection anywhere.
So passwords are copied around a
** Changed in: python-keyring (Ubuntu)
Assignee: Barry Warsaw (barry) => (unassigned)
** Changed in: python-keyring (Ubuntu)
Milestone: natty-alpha-3 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Summary changed:
- MIR needed (dependency of python-launchpadlib)
+ upgrade to python-keyring 0.5 (and MIR)
** Changed in: python-keyring (Ubuntu)
Assignee: (unassigned) => Barry Warsaw (barry)
** Changed in: python-keyring (Ubuntu)
Milestone: None => natty-alpha-3
--
You received
