https://bugzilla.novell.com/show_bug.cgi?id=385159 User jsuchome@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=385159#c1 Jiří­ Suchomel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |lnussel@novell.com --- Comment #1 from Jiří­ Suchomel 2008-04-30 04:31:30 MST --- (In reply to comment #0 from Ludwig Nussel)

I'd like to suggest to change some defaults in the yast2-security module:

- don't put current working directory in $PATH by default. It's ok to offer this but we shouldn't set it

You mean, set CWD_IN_ROOT_PATH, CWD_IN_USER_PATH to "no" also for "Home Workstation", right?

- enable sysrq for "Home Workstation" or at least use "176" which is the package default

OK.

- use cracklib and obscure checks for password checking also for "Home Workstation" as ssh is still on by default

Currently, obscure checks are off for all predefined settings. But I could do the change, of course.

- run updatedb as nobody by default always

OK.

There are some settings that should not be modified at all such as password encryption or uid/gid ranges. Those have nothing to do with a more relaxed or more paranoid security policy.

But we want to offer some way to modify them, so why should we drop it? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=385159 User jsuchome@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=385159#c3 Jiří­ Suchomel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #3 from Jiří­ Suchomel 2008-04-30 05:03:30 MST --- Ranges & enc. method: I think it is fine when the predefined levels have the same values (they do). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.