On Thursday 15 March 2007 20:32, Jonas Karlsson wrote: > > I don't like this. If someone insists on shooting themselves in the > > foot, they should already know how to do so, without any help from the > > installer. On the topic of the user screens, I noticed that if the two > > passwords don't match, the installer flashes a warning, but permits the > > installation to continue. The correct behavior should be to not enable > > the "Next" button until both passwords match. > > That's my idea as well. I also think that we should have a minimun > level of password security and a warning should be issued if this > level is not reached ( http://bugs.gobolinux.org/view.php?id=56 ). > About the "no extra users" see my reply to Hisham as well as the > following bug report ( http://bugs.gobolinux.org/view.php?id=57 ). How about a replicate of KDE's password strength meter? (I think that Firefox and Thunderbird also have something like this as well.) I haven't really tested it, but I imagine that it takes into account whether there are both upper and lower case letters, numbers, and other characters. Here's a JavaScript implementation (works in Firefox, but not in Konqueror) that looks to do about the same thing: http://www.gerd-riesselmann.net/examples/testprogress.html
> > Requested functionality for 015 (but maybe add the hooks in the 014 > > installer): encrypt hard drive partitions. After doing some tests, I'm > > withdrawing my previous support for EncFS; it's fine for encrypted > > directories, but not for encrypting entire partitions. LUKS seems to be a > > much better choice, and also has the added bonus that with FreeOTFE > > (http://www.freeotfe.org) encrypted Linux partitions can be mounted in > > Windows (should someone for some strange reason still have Windows). > > What's bad about EncFS? My view was that it wasn't for encrypting > entire partitions, but only for users $HOME, to be used together with > PAM. I like the idea of having an encryption scheme that's also > reachable from other OSes. I'll look into LUKS when I get some extra > time on my hands as I do believe that we should support encryption. KDE bails when $HOME is encrypted with EncFS; I corresponded with the author of EncFS, and he attributed it to the fact that FUSE can't handle lock() calls. I've tried several different workarounds, but to no success; the only way to get it to work is if $HOME/.kde is not encrypted using EncFS, which is obviously not a solution, given what's stored there. :Peter _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
