enh: Ubuntu Security Center

Created an attachment (id=1732)
A glade-2 mock-up to give the devs an idea of the basic concept

Just a glade-2 mock-up. Look at it, it's ugly, it does nothing, don't bother
compiling it. Basically it's a drawing, an orthographic projection,
blueprints, a concept design.

The administrative apps for users and groups and such are beautiful in Ubuntu,
can't you spark the same design into a security center? :)

Created an attachment (id=1841)
Usability feedback on first draft mockup (575 words)

These notes may be useful if the eventual program uses the glade mockup at all.

I'd hope the eventual program would look more like the Users and Groups app we
have, or be an extension of said :)

I was only doing the mock-up as a visual aid because I suck horribly at UI
design. But here's some blowback:

-General-
 You're right, on all of it. It generally sucks.

-SetUID-
* This tab would make more sense as a "Security" tab in the "Users
    and Groups" control panel.
 Additionally, a lot of this would make sense if you extended the
 control application to "Users, Groups, and Security," since Users and
 Groups are used effectively for access control, which is security.
* Translate <XXX> into english
 Yes. Do that, all of it.
* If possible, combine "use 'at'" and "use cron" into a single
    option, "Set tasks to be performed at scheduled times".
 The 'at' program has its own separate implications from 'cron'

-Accounts-
* I have no idea what "BSD r-tools" are, and Google's no help.
    Explain.
 It was in bastille. I don't know what it was either.
* Checkboxes aren't for determining whether something's off,
 Reverse the logic
* "Restrict who can use cron" to ... what?
 Twas in bastille. Restrict it to users allowed to use cron :)
* "Restrict default file permissions to user" what? This looks
    like an incomplete sentence.
 default umask should be 0700 instead of 0755
* Translate "Restrict root account to sudo only" into English.
    Again I can't help because I don't understand what this means.
 This we already do. You can't log in as root, only as a user with
 sudo access.

Booting
* Call it "Startup" instead.
 I prefer "boot" instead of "startup," because people need to get on
 the same page with the vocabulary. Better to learn what it's called,
 than to break it and go into a channel like "I can't get the boot to
 the computer and i need you to upload a new windows" (i've had that
 happen, I couldn't help the person at first because I couldn't
 understand wtf he was saying until 10 minutes of gibberish later).
 This isn't a huge barrier.
* Use a header, "Ask for password before:", followed by checkboxes
    for "Starting up" and "Restarting".
 The password in the boot loader is to keep people from using custom
 startup settings, such as {scroll to menu entry, e, kernel line, e,
 init=/bin/sh} to get instant root access. Passwords for shutting
 down are to prevent people from shutting down of course.

-Resources-
* "No core files"? How is this a security feature? Explain, in
    the GUI.
 Core files are dumps of memory. A technician can fish out
 frobnicated (foo XOR 0x42424242) root passwords and credit card
 numbers and defrobnicate them easily. Also, core files accumulate
 and eat up space when things repetedly crash. This can cause a
 denial of service attack (full disk). Most users just leave these
 things laying around for lack of knowing or caring what they are.

-PaX-
* This tab is meaningless to someone who doesn't know what PaX is,
    which is most people. Explain, in the GUI.
 Yeah, and on non-PaX systems like default ubuntu, this will be
 meaningless. Eventulaly Ubuntu will support PaX. This configuration
 would need to be around to control it. This would include t...

oops. Thought that was about half the length. :/

I'd like to see this myself, but I doubt the devs have time...