Bug 920837 - Get a grip on decent security policy
Summary: Get a grip on decent security policy
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: seahorse
Version: 18
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-12 21:23 UTC by alexhultman
Modified: 2014-02-05 19:54 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 19:54:37 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description alexhultman 2013-03-12 21:23:03 UTC
The security policy in Fedora is ridiculous.

I have an encrypted HDD that needs root passwords two times every time I mount it. I have stored the encryption key in a keyring.

Updating software can also be ridiculous in the same way. Fedora 15 did actually remember passwords better than Fedora 18 now does. It has become worse every by release.

And I don't get why (the fuck) you have a program that can show all passwords in clear text. Why bother asking for passwords five million times when all passwords are available in clear text.

I'm well aware of the argument "well, every application could potentially display passwords from unlocked keyrings, that's by design". Yes, I know that installed applications could leak passwords to the user if they wanted to (but they don't). Also - if you wanted to display passwords stored in the keyring you would have to install an application that does this. To install an application you have to enter root password so it's essentially safe. Why do you ship Fedora with an application already instaleld that can leak passwords to any user? That's insane.

I might not know exactly how security is handled in Fedora but I know that the current way is idiotic and insane. Don't ship an OS that has a program installed by default that spoils all "secret" passwords to any user!

And stop asking me 259023479723498123640891398273492374 times for my root password. Get a grip.

Comment 1 Fedora Admin XMLRPC Client 2013-05-09 00:24:47 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 2 Fedora End Of Life 2013-12-21 12:06:09 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2014-02-05 19:54:37 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.