On 2/20/2017 7:40 PM, Peter Mc Donough wrote:

Am 21.02.2017 um 00:48 schrieb Yamaban:

...

On Tue, 21 Feb 2017 00:23, Peter Mc Donough wrote:

...

Tonight I needed magic sysrequest <AlT><Print> reisub. System Tumbleweed, up-to-date It didn't work.

Yast tells me, it is enabled.

Any other switch to check?

Hints from here (Disabled by Default): https://forums.opensuse.org/showthread.php/510867-Is-Alt-SysRq-REISUB-disabl...

From there: You can enable it in YaST->Security and Users->Security Center and Hardening e.g.

That is where I had already checked. With a little experiment I found something I didn't expect:

Green hook = disabled red cross = enabled

I love when a developer or ui designer or really anyone but me decides to assign a value judgement on toggles like that. -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 2017-02-21 00:40, Peter Mc Donough wrote:

From there: You can enable it in YaST->Security and Users->Security Center and Hardening e.g.

That is where I had already checked. With a little experiment I found something I didn't expect:

Green hook = disabled red cross = enabled

for the security center it actually makes sense, when you think Green hook = disabled = secure red cross = enabled = insecure -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 2/21/2017 8:53 AM, Stefan Seyfried wrote:

On 21.02.2017 07:50, Bernhard M. Wiedemann wrote:

...

for the security center it actually makes sense, when you think Green hook = disabled = secure red cross = enabled = insecure

Oh, the old urban legend (I argued for years with the "security" team until I gave up).

"Disabling sysrq makes a system more secure". WRONG. Because you also disable the Secure Access Key.

One of the top-voted annoying SUSE features around here, the top three being * disabling sysrq * grub2 branding * plymouth default active

(all centered around servers / cloud / SLES, but still annoying to me as a private person using tumbleweed)

ding ding ding yes, yes, and yes. Although for me the 0th item before these 1, 2, & 3, is systemd. ;) -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Am Mittwoch, 22. Februar 2017, 13:58:11 schrieb Brian K. White:

On 2/21/2017 1:50 AM, Bernhard M. Wiedemann wrote:

...

On 2017-02-21 00:40, Peter Mc Donough wrote:

...

From there: You can enable it in YaST->Security and Users->Security Center and Hardening e.g.

That is where I had already checked. With a little experiment I found something I didn't expect:

Green hook = disabled red cross = enabled

for the security center it actually makes sense, when you think Green hook = disabled = secure red cross = enabled = insecure

I understood the reasoning. That's what I meant about value judgements. It's out of place to say one way or the other is good or bad or wrong or right. Even in a security dialog.

Well, that's the "Security Overview" dialog. So the checkmarks tell the security status. (whether it's considered to be safer to have it enabled or disabled security-wise is a different story though, I suppose) The proper place to configure this is "Miscellanous Settings" in the same module or the "Kernel Settings" module (in "Hardware"), I think. Although, I agree that the "Configure" is misleading and maybe a bug. Other things do have an Enable/Disable option there... Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Tue, 21 Feb 2017 02:27, Jan Engelhardt wrote:

On Tuesday 2017-02-21 00:48, Yamaban wrote:

...

On Tue, 21 Feb 2017 00:23, Peter Mc Donough wrote:

...

Tonight I needed magic sysrequest <AlT><Print> reisub. System Tumbleweed, up-to-date It didn't work.

Yast tells me, it is enabled.

Any other switch to check?

It's stored in sysctl, as kernel.sysrq, check via "/usr/sbin/sysctl -a --pattern kernel.sysrq" (works as normal user) a value of "0" (zero) means disabled, a value of "1" (one) means enabled.

No, check your books. This is not a boolean, it's a bitmask, and "1" is usually not getting you the basic set that openSUSE has had enabled in the default install in the past.

Oh, right, derp on my side. Good docu here: https://fedoraproject.org/wiki/QA/Sysrq But the most imporant point is: "1 - enable all functions of sysrq" - Yamaban. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 21.02.2017 02:27, Jan Engelhardt wrote:

No, check your books. This is not a boolean, it's a bitmask, and "1" is usually not getting you the basic set that openSUSE has had enabled in the default install in the past.

Well, what was enabled default in the past was totally useless anyway, so "1" gives you the useful configuration you got 10 years ago with "SYSRQ=yes" in sysconfig or "sysrq=yes" on the install command line -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org