Here are the latest commented ideas about Ubuntu.
Never lose focus while typing a password
Written by pabix the 18 Jan 09 at 21:42.
Global category: Security.
New
It may have happened to you. You're typing a password in a web page, and suddenly, a window pops up, with a text field inside it, and since you did not notice it at once, you password displays in clear in the other window.
Solution #2:
Lock Enter key for some seconds in newly popped up windows
Written by
marvo the 19 Jan 09 at 08:45.
The unwanted visibility of passwords is only one annoyance in foreground-catching windows. Much worse is in my opinion that some of them require some input and do have their focus already set to the "ok" button. More then once I have "confirmed" some pop-up-messages while typing a text in my browser or word processor. It would be very helpful if the ok-button of a pop-up-box was inactive at least for some seconds.
The unwanted visibility of passwords is only one annoyance in foreground-catching windows. Much worse is in my opinion that some of them require some input and do have their focus already set to the "ok" button. More then once I have "confirmed" some pop-up-messages while typing a text in my browser or word processor. It would be very helpful if the ok-button of a pop-up-box was inactive at least for some seconds.
Solution #3:
Lock focus while typing.
Written by
gmatht the 19 Jan 09 at 11:10.
Lock focus for one second (or so) since the last key was pressed so that we never lose focus while typing.
Lock focus for one second (or so) since the last key was pressed so that we never lose focus while typing.
Solution #4:
Remove focus, use attention methods
Written by
dolf1074 the 25 Jan 09 at 00:47.
When an application wants your attention, it should ask it. NOT suddenly appear and take the focus. A program is now already able to ask your attention by flashing the application in the taskbar. So why some applications don't use that and rather want to bother the user in there work flow, I don't know.
When an application wants your attention, it should ask it. NOT suddenly appear and take the focus. A program is now already able to ask your attention by flashing the application in the taskbar. So why some applications don't use that and rather want to bother the user in there work flow, I don't know.
Solution #5:
Implement Solution #1 but have as an option
Solution #1 is an excellent idea, but not all may like it. This should be a default option, with the ability to disable it. Perhaps this option could be in System > Preferences > Windows.
Solution #1 is an excellent idea, but not all may like it. This should be a default option, with the ability to disable it. Perhaps this option could be in System > Preferences > Windows.
Solution #6:
Beep if a window pops up while typing in a password box ( but as an option )
Written by
Andrius the 3 Feb 09 at 18:13.
this can be also useful for non-password textboxes
this can be also useful for non-password textboxes
Solution #7:
Have ability to set system wide how to deal with stolen focus
Written by
grofaty the 7 Feb 09 at 18:13.
Like #4, but have ability to set how you would like to deal with stolen focus.
For system wide options should be:
1. Allow stolen focus (like now)
2. Double blink program in task bar
3. Set notification.
4. Don't bother me at all.
Windows XP has this solution already implemented by installing "Tweak UI" official Windows program. Read more at:
http://mycvs.org/archives/2004/11/16/applications-stealing-focus-on-windows-xp
Like #4, but have ability to set how you would like to deal with stolen focus.
For system wide options should be:
1. Allow stolen focus (like now)
2. Double blink program in task bar
3. Set notification.
4. Don't bother me at all.
Windows XP has this solution already implemented by installing "Tweak UI" official Windows program. Read more at: http://mycvs.org/archives/2004/11/16/applications-stealing-focus-on-windows-xp
Solution #8:
Don't steal the focus!
The newly opened application should not steal the focus at all, or make a switch somewhere for this.
The newly opened application should not steal the focus at all, or make a switch somewhere for this.
Solution #9:
Provide a flexible option in compiz
This depends on the context. Let's say you're browsing files in Nautilus (an application), and you double click a file. In this case you might prefer not to have the new window opened in the background (which happens sometimes).
Provide it as an OPTION in compiz (try ccsm), that is capable of providing this feature based on window name or class. Setting could be tailored the way user wants, and would stay out of the way of those who don't care.
This depends on the context. Let's say you're browsing files in Nautilus (an application), and you double click a file. In this case you might prefer not to have the new window opened in the background (which happens sometimes).
Provide it as an OPTION in compiz (try ccsm), that is capable of providing this feature based on window name or class. Setting could be tailored the way user wants, and would stay out of the way of those who don't care.
Solution #10:
Request to click before prompting
Written by
Lachu the 6 Feb 10 at 15:03.
Password fields should request to click special widget, with lock whole X Server onto password field and exit widget.
User ought to input password, before click onto that button! There no way to exit from this field without clicking button again.
Behavior of enter key/arrows could be: give focus to exit button.
Below password prompt, some helping messages should appear, like press exit key to accept prompting password.
Password fields should request to click special widget, with lock whole X Server onto password field and exit widget.
User ought to input password, before click onto that button! There no way to exit from this field without clicking button again.
Behavior of enter key/arrows could be: give focus to exit button.
Below password prompt, some helping messages should appear, like press exit key to accept prompting password.
Preventing unwanted eyes prying on confidential information
Written by humphreybc the 29 Oct 09 at 03:31.
Related project: Gnome .
New
Despite needing to enter your root password to alter such basic things as CPU Scaling, you are not once prompted to enter it to access the Passwords and Encryption Keyring. Anyone is able to view your stored MSN, Twitter, email and Wifi passwords in four simple clicks of the mouse from the desktop.
How to reproduce:
1. Restart your computer and login. Do not enter any passwords after your desktop has loaded.
2. Go to Applications > Accessories > Passwords and Encryption Keyrings
3. Click on the 'Login' folder to drop down and view the programs that store data here.
4. Double click on something you want to look at.
5. Click Password to show some dots, then uncheck the box below the dots marked "Show password"
6. Note that throughout this whole procedure, not once were you prompted to enter in anything that verifies you are authorized to view this information.
This is a security risk, and, because it is a conscious decision for design, not classified as a bug.
Here's the related Ubuntu Forums thread:
http://ubuntuforums.org/showthread.php?t=1302342
and, a post on omgubuntu.co.uk:
http://www.omgubuntu.co.uk/2009/10/security-issue-in-gnome-lets-anyone-see.html
[....]
Solution #1:
Prompt to enter user password before showing stored passwords in clear text
The Seahorse program should prompt you to enter in your user password, much the same way that sudo works, before allowing the stored passwords to be displayed in clear text.
Also, the "Passwords and Encryption Keys" Application should be moved to Preferences.
The Seahorse program should prompt you to enter in your user password, much the same way that sudo works, before allowing the stored passwords to be displayed in clear text.
Also, the "Passwords and Encryption Keys" Application should be moved to Preferences.
Solution #2:
Unify Ubuntu personal security.
Written by
snkiz the 29 Oct 09 at 04:11.
this is my thought on how to fix it.
The way I see it Ubuntu is almost there, seahorse does ask permission
just no confirmation. And we do have the tools like gconf. And
policykit, witch can handle non-root permissions and IMO is way under
used.
Here's my idea, create a sane list of default apps that can access
seahorse. The ability to change that list through gconf, and
permission checks through policykit for unexpected apps, changing info
or viewing passwords. And finally come up with a unified personal
security policy for the desktop as a whole. (IN about me you need your
password to change your password and about me does not display clear
text.)
this is my thought on how to fix it.
The way I see it Ubuntu is almost there, seahorse does ask permission
just no confirmation. And we do have the tools like gconf. And
policykit, witch can handle non-root permissions and IMO is way under
used.
Here's my idea, create a sane list of default apps that can access
seahorse. The ability to change that list through gconf, and
permission checks through policykit for unexpected apps, changing info
or viewing passwords. And finally come up with a unified personal
security policy for the desktop as a whole. (IN about me you need your
password to change your password and about me does not display clear
text.)
Solution #3:
Don't show passwords in plain text
Written by
daithi the 27 Nov 09 at 03:04.
Why is there even an option to show passwords in plain text from within a GUI application? This option should be removed, especially if the other solutions are likely to be difficult to implement in practice.
Why is there even an option to show passwords in plain text from within a GUI application? This option should be removed, especially if the other solutions are likely to be difficult to implement in practice.
Solution #4:
Require user password before showing passwords in keyrings
Written by
zorkerz the 2 Dec 09 at 03:15.
The Seahorse program should prompt you to enter in your user password, much the same way that sudo works, before allowing the stored passwords to be displayed in clear text.
Note: this is the same as solution #1 except that the seahorse launcher "Passwords and Encryption Keys" should remain under applications.
The Seahorse program should prompt you to enter in your user password, much the same way that sudo works, before allowing the stored passwords to be displayed in clear text.
Note: this is the same as solution #1 except that the seahorse launcher "Passwords and Encryption Keys" should remain under applications.
Solution #5:
Temporary Solution: Educate people
Written by
agrouo the 15 Dec 09 at 01:56.
When using a graphical tool for key management (e.g. seahorse) for the first time, tell the people that their passwords and account are generally not safe and they should resort to locking their session and let others use the easily accessible guest account.
(not denying the bigger, but most probably quite harder problem, of securing passwords)
When using a graphical tool for key management (e.g. seahorse) for the first time, tell the people that their passwords and account are generally not safe and they should resort to locking their session and let others use the easily accessible guest account.
(not denying the bigger, but most probably quite harder problem, of securing passwords)
Solution #6:
Authentication service instead of password store
Written by
agrouo the 15 Dec 09 at 02:37.
Generally switch to a better security scheme than passwords. Especially, where no direct user interaction is necessary.
Aims
* preventing programs from accessing passwords of other programs
* avoid using passwords as far as possible
How
* if possible use mechanisms without passwords (e.g. mail account AUTH DIGEST)
* reconstructing passwords should happen in different applications
This consists of three parts:
1) allow programs to let the service handle authentication for them (e.g. mail program lets the authentication service handle AUTH DIGEST authentication, so it doesn't need to see the password at all)
2) restrict access to stored information to the right programs (see Solution #2)
3) For applications which need to use password: instead of storing user-entered passwords to be accessed by the application, store keys which the application needs for decrypting the real passwords.
In this way, attacks would have to be crafted for specific applications, not only against the password store.
Generally switch to a better security scheme than passwords. Especially, where no direct user interaction is necessary.
Aims
* preventing programs from accessing passwords of other programs
* avoid using passwords as far as possible
How
* if possible use mechanisms without passwords (e.g. mail account AUTH DIGEST)
* reconstructing passwords should happen in different applications
This consists of three parts:
1) allow programs to let the service handle authentication for them (e.g. mail program lets the authentication service handle AUTH DIGEST authentication, so it doesn't need to see the password at all)
2) restrict access to stored information to the right programs (see Solution #2)
3) For applications which need to use password: instead of storing user-entered passwords to be accessed by the application, store keys which the application needs for decrypting the real passwords.
In this way, attacks would have to be crafted for specific applications, not only against the password store.
Ask for application restart after security update
Written by xfuser4 the 21 Aug 09 at 06:16.
Related project: Update manager .
New
There are sometimes very critical security updates for applications (like the last Pidign-Update).
Unfortunately the Update Manager doesn't inform the user, that the update is only effective, if the application is restarted after it.
Since suspend-2-ram works for now on many computers, some applications are only seldom restarted (e.g. Pidgin may run for several weeks).
In the case of pidgin this is even a security risk, since an application with a security leak might run for several weeks until the last security fixes will apply.
Solution #1:
Ask for restart of applications
Written by
xfuser4 the 21 Aug 09 at 06:16.
After kernel updates, we are asked for restarting the computer. If a (critical) update of an application have happened, the update manager should ask for an restart of the application (or inform the user about the need of a restart).
After kernel updates, we are asked for restarting the computer. If a (critical) update of an application have happened, the update manager should ask for an restart of the application (or inform the user about the need of a restart).
Solution #2:
Updater proposes auto-restart and restore of affected apps
If 1 or more critical updates have been installed, we are offered a checklist of all apps that will benefit from a restart. The dialogue makes clear that all listed apps will benefit from a restart (and maybe how) and that all checked apps will be automatically restarted with an attempt made to return the app to its previous state (subject to security or other important concerns). Examples: Transmission torrents return to their individual active/paused status, Pidgin either remains unlogged or autologs the last user, active OpenOffice docs are reopened.
Updater preferences allow the user to choose which update types appear on the checklist: "security", "bug fix", "new feature"
If 1 or more critical updates have been installed, we are offered a checklist of all apps that will benefit from a restart. The dialogue makes clear that all listed apps will benefit from a restart (and maybe how) and that all checked apps will be automatically restarted with an attempt made to return the app to its previous state (subject to security or other important concerns). Examples: Transmission torrents return to their individual active/paused status, Pidgin either remains unlogged or autologs the last user, active OpenOffice docs are reopened.
Updater preferences allow the user to choose which update types appear on the checklist: "security", "bug fix", "new feature"
Solution #3:
Only Prompt for application restart if X time elapsed since update.
Written by
lavinog the 31 Aug 09 at 17:07.
Annoying users with restart notices can deter users from updating in a timely manner.
To avoid displaying excessive restart prompts, the prompts should be displayed after a preset time if the application hasn't been restarted since the update.
User A was only going to be using pidgin for 20 minutes, he shouldn't be interrupted by a dialog asking him to put his conversation on hold for a restart.
User B performs updates, but leaves his computer idle for a couple of hours. When he comes back to his computer, he will see a dialog box explaining that the recent security update wont take affect until the application is restarted.
Annoying users with restart notices can deter users from updating in a timely manner.
To avoid displaying excessive restart prompts, the prompts should be displayed after a preset time if the application hasn't been restarted since the update.
User A was only going to be using pidgin for 20 minutes, he shouldn't be interrupted by a dialog asking him to put his conversation on hold for a restart.
User B performs updates, but leaves his computer idle for a couple of hours. When he comes back to his computer, he will see a dialog box explaining that the recent security update wont take affect until the application is restarted.
Solution #4:
Update the application without restart
I propose to update the application "on-fly". So you don't need to stop chatting if your instant messenger gets an update.
I propose to update the application "on-fly". So you don't need to stop chatting if your instant messenger gets an update.
Solution #5:
Show restart indicator in tray
Written by
adisk the 16 Sep 09 at 15:18.
Show restart indicator in tray.
Click on indicator show question for restart.
Show restart indicator in tray.
Click on indicator show question for restart.
Solution #6:
Send email notification to admin
Written by
adisk the 16 Sep 09 at 15:40.
Send email notification to admin. For servers only.
Send email notification to admin. For servers only.
Solution #7:
#5 but with more details
like #5, but when the "restart-indicator" is clicked it folds down to a list, the top entry saying
"some of your applications received important updates, but need to be restarted before these can take effect".
after that a list of applications in question and a "restart all" item follow.
if the user clicks on one of the apps it is restartet and disappears from the list.
if an app was manually restartet (by the user) it also disappears from the list.
if there are no more apps left the restart-indicator should close by itself.
sometimes system components receive updates which will only take effect after a full reboot. this can be incorporated by adding an item to the very bottom that says "In fact there are some udpates which require to restart the entire operating system. Restart now! "
like #5, but when the "restart-indicator" is clicked it folds down to a list, the top entry saying
"some of your applications received important updates, but need to be restarted before these can take effect".
after that a list of applications in question and a "restart all" item follow.
if the user clicks on one of the apps it is restartet and disappears from the list.
if an app was manually restartet (by the user) it also disappears from the list.
if there are no more apps left the restart-indicator should close by itself.
sometimes system components receive updates which will only take effect after a full reboot. this can be incorporated by adding an item to the very bottom that says "In fact there are some udpates which require to restart the entire operating system. Restart now! "
<img src="http://img390.imageshack.us/img390/5393/ubunturestartnotify.png">
Software center asks for password too often
Written by snostorm the 27 Oct 09 at 15:01.
Related project: Ubuntu Software Center .
New
If you go to install something via the software center, it installs it system-wide, which of course requires a password.
Now this is obviously annoying, but would also seem to also cause a security risk; if the user gets used to entering his password at any point, he may enter it when he has no idea why the dialog is there, allowing malware to get root access.
Of course, the password dialogs are a necessary part of security. But everything in the default repositories is known to be safe, and a password is required to add non-standard repos.
Add security to login process and sytem accountablity
Written by axx the 29 Sep 09 at 07:00.
Global category: Security.
New
If you login on tty1, you are informed of failed login attempts since your last successful.
This sort of information can be useful.
Taking this further, and going back to this hack on OS X (
http://www.macosxhints.com/article.php?story=2006120918170984), it could be an interesting idea to add an option to the login manager to warn you of failed connection attempts on your account and offer to capture pictures via the webcam on login failures (it clearly makes most sense on laptops).
This could be taken further by having the photo e-mailed or uploaded to a FTP server, which could be quite useful in case of computer theft.
This provides accountability of what happens to your computer when you're away and could help in case of theft.
Solution #1:
add option to take webcam snapshots to GDM / KDM
Written by
axx the 29 Sep 09 at 07:00.
After a successful login, the system should warn the user if there were any unsuccessful login attempts on their account, via a notification for instance.
If the system detects a working webcam, it should be quite simple to have GDM/KDM use the webcam to take a snapshot.
This should be added as an option to the login manager.
Given a working internet connection, the picture should be send to an e-mail address or FTP server. Motion is capable of similar things, maybe it could be used to do so.
This also would be an option in the login manager's preferences.
The only caveat is that the system needs a working internet connection to send the data, and wifi connections are usually up and running *after* login. Ethernet connections shouldn't be a problem.
After a successful login, the system should warn the user if there were any unsuccessful login attempts on their account, via a notification for instance.
If the system detects a working webcam, it should be quite simple to have GDM/KDM use the webcam to take a snapshot.
This should be added as an option to the login manager.
Given a working internet connection, the picture should be send to an e-mail address or FTP server. Motion is capable of similar things, maybe it could be used to do so.
This also would be an option in the login manager's preferences.
The only caveat is that the system needs a working internet connection to send the data, and wifi connections are usually up and running *after* login. Ethernet connections shouldn't be a problem.
Solution #2:
Cheese can do this
Could be triggered to take a snapshot and mail it.
Could be triggered to take a snapshot and mail it.
Vino (Gnome VNC) Needs better security than 8 character passwords
Written by mikedep333 the 23 Sep 09 at 22:18.
Related project: Vinagre Remote Desktop Viewer .
New
The ancient protocol behind the VNC remote desktop system, RFB, only supports passwords 8 characters long. This means that any password is easily brute forced unless you use other criteria to make it secure (eg a mix of special characters, upper/lowercase letters and numbers.) This is the way that Vino, the GNOME VNC Server (System > Preferences > Remote Desktop,) and Vinagre, the GNOME VNC client, work for password authentication. (Vino also lets the local users manually approve connections.)
Small gnome password applet.
Written by danielpublicsweden the 8 Aug 09 at 20:29.
Related project: Gnome .
New
Since it seems like people are using the same passwords half across the internets and maybe even their own computer. :(
I would like to see a gnome applet that:
1. You use a master password. (One good, strong password to remember!) Even if this password is compromised, and thanks to the use of "description values", if this password is "lost", it do not threaten all your passwords.
You could even have an extra description values like "sausage"/"flower"/"badger", to get even higher security.
2. Generates your password through algorithms and descriptions on what you use it for. Site url/file/tags/etc. Plus possibilty to use extra personal values for heightened security.
3. _No storage_ of any passwords on disk. (No need for backup) Only descriptions is stored in a encrypted file. (See solution #2)
4. Should be easy to generate new strong passwords.
5. Should be able to autocomplete.
6. Should be useful when using another computer (Public/job) by use of "online" script, which is run locally from browser. Which is achieved by masterpassword + descriptions (as in the url+username/other values, for the site to access) As in:
http://passwordmaker.org/passwordmaker.html
How it could work:
The password to use are generated by a master password and "description values" (url/username/tags/file/date/etc.) -> one way hash algorithm (
http://en.wikipedia.org/wiki/Cryptographic_hash_function )= message digest(
http://www.rsa.com/rsalabs/node.asp?id=2176 )=password to use. READ ON PLEASE! :D
[....]
Solution #1:
Passwordmaker
Maybe inner workings of applet _based_ on something like this approach?
http://passwordmaker.sourceforge.net (GPL)
Solution #2:
Passwordmaker and "description values/autocomplete" backup.
Since the description values of the "file/url/tag/etc." is a big part for generating the password through the one-way hash algorithm. (masterpassword+description values=message digest=password)
Its maybe not easy to remember exactly what values that was used for generating the password.
How could/should the backup be performed?
Suggestion: Compress it with in a encrypted LZMA (7zip), upload it to some site, put a generated password on it, upload function something like the excellent FEBE (
http://customsoftwareconsult.com/extensions/febe/febe.html ), which uses
http://box.net . Upon addition of autocomplete/generation of new password, give reminder of backup. As in: "Do you want to backup and upload now?"/"Remind me in x days".
Since the description values of the "file/url/tag/etc." is a big part for generating the password through the one-way hash algorithm. (masterpassword+description values=message digest=password)
Its maybe not easy to remember exactly what values that was used for generating the password.
How could/should the backup be performed?
Suggestion: Compress it with in a encrypted LZMA (7zip), upload it to some site, put a generated password on it, upload function something like the excellent FEBE (http://customsoftwareconsult.com/extensions/febe/febe.html ), which uses http://box.net . Upon addition of autocomplete/generation of new password, give reminder of backup. As in: "Do you want to backup and upload now?"/"Remind me in x days".