Set application name to something different from 'python'
Bug #438972 reported by
Kamil Páral
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gkeyring |
Won't Fix
|
Medium
|
Unassigned | ||
| Trunk |
Won't Fix
|
Medium
|
Unassigned | ||
Bug Description
The application name (visible in "ps" or "pgrep") should be set to something else then python. The reason is that GNOME keyring sets permissions according to program name. When it is set to 'python', then all python programs will have the same access privileges to the keyring item.
| Changed in gkeyring: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| Changed in gkeyring: | |
| milestone: | none → 0.2.0 |
Revision history for this message
| Kamil Páral (kamil.paral) wrote | #1 |
| Changed in gkeyring: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
This is very weird. When I first tried it, it looks like to me that every python program had the same access to gnome keyring. But now when trying it, it correctly remembers that only gkeyring.py had access to some password and ask correctly again if I rename the script to gkeyring2.py. Therefore it seems that gnome keyring works well in this respect.
The gtk name is correctly set by the 'import gtk' line.
As for changing process name, it is not currently supported in Python:
http://
It can be done by using native calls:
http://
But it is not necessary for this program I think, so I close this bug.