Hi Rahul, It is till Friday in Canada, but I note the time you are responding. I complement you on your dedication.
Yes, in response to your question, I filed bugs, and yes, there are some keyboard changes coming after go live.
As for being able to shutdown from any account. It says that Core5 cannot be used as a server and also have another guest user who could issue that command. I should not have to modify the halt / shutdown / reboot stuff to add security. If I want a guest end user to do a shutdown, I want to extend that privledge to him. This last point is philosophical (I have a UPS to prevent power spike generated shutdowns, and on the otherhand, any user can issue a shutdown request.)
GNOME project is saying they can control access to what is shown on a user's menu. Perhaps that is the way to do it, to prevent access to restricted software.
Message: 17 Date: Sat, 11 Mar 2006 00:57:17 +0530 From: Rahul Sundaram sundaram@fedoraproject.org Subject: Re: One week delay To: For testers of Fedora Core development releases fedora-test-list@redhat.com Message-ID: 4411D315.3080403@fedoraproject.org Content-Type: text/plain; charset=us-ascii; format=flowed
Leslie Satenstein wrote:
There are many rough edges to the Core5 release. I personally would want the extra week(s) spent on cleaning up.
My nuances I found XEN version will not power off after a shutdown command
Did you file a bug report on this?
I found that any user, including guest, could issue a shutdown command
This one is not a bug.
I found that there are still keyboard definition problems that are not
solved
Any bug reports?
Leslie Satenstein wrote:
Hi Rahul, It is till Friday in Canada, but I note the time you are responding. I complement you on your dedication.
Well its actually 3 AM at Saturday for me ;-)
Yes, in response to your question, I filed bugs, and yes, there are some keyboard changes coming after go live.
If you did file bug reports, kindly do provide the links to those bug reports for reference when you talk about them
As for being able to shutdown from any account. It says that Core5 cannot be used as a server and also have another guest user who could issue that command. I should not have to modify the halt / shutdown / reboot stuff to add security. If I want a guest end user to do a shutdown, I want to extend that privledge to him.
This has already been discussed in the lists before. If a person has physical access to the system, he can always turn it off or set your system on fire, so merely controlling the ability to turn off or reboot the system doesnt provide any real security and is a hiderance to getting work done. This is by no means a blocker bug that needs to be dealt with one week before a release anyway.
On 3/10/06, Rahul Sundaram sundaram@fedoraproject.org wrote:
This has already been discussed in the lists before. If a person has physical access to the system, he can always turn it off or set your system on fire, so merely controlling the ability to turn off or reboot the system doesnt provide any real security and is a hiderance to getting work done. This is by no means a blocker bug that needs to be dealt with one week before a release anyway.
I wonder.... would it be possible for a local admin to write a custom pam stack which made the issue of a "guest" getting these "console" permission... without getting into the whole discussion of the underlying pointlessness of it to protect against malicious users intent on turning off a system.
It maybe ultimately pointless, but its not worth arguing about. If there is a way right now to rewrite pam related configurations to make this issue go away.. i think we should just write it down in the wiki and point anyone complaining about this to the wiki.
-jef"You can't talk sense into a local sysadmin intent on perverting your worldview as to what correct behavior is... just appease them as quickly as possible and move on"spaleta
On Friday 10 March 2006 15:52, Rahul Sundaram wrote:
As for being able to shutdown from any account. It says that Core5 cannot be used as a server and also have another guest user who could issue that command. I should not have to modify the halt / shutdown / reboot stuff to add security. If I want a guest end user to do a shutdown, I want to extend that privledge to him.
This has already been discussed in the lists before. If a person has physical access to the system, he can always turn it off or set your system on fire, so merely controlling the ability to turn off or reboot the system doesnt provide any real security and is a hiderance to getting work done.
-- Rahul
Surely a remote user is prohibited, by default, from shutting down a computer in a locked facility, no?
Regards, Mike KLinke
On 3/10/06, Mike Klinke lsomike@futzin.com wrote:
Surely a remote user is prohibited, by default, from shutting down a computer in a locked facility, no?
at no point in this discussion has the word...remote.. been used.
-jef
On Friday 10 March 2006 16:27, Jeff Spaleta wrote:
On 3/10/06, Mike Klinke lsomike@futzin.com wrote:
Surely a remote user is prohibited, by default, from shutting down a computer in a locked facility, no?
at no point in this discussion has the word...remote.. been used.
-jef
If the conversation Rahul is referring to includes this message, then indeed it has ...
http://marc.theaimsgroup.com/?l=fedora-test-list&m=114126977632141&w...
Regards, Mike Klinke
On Fri, 2006-03-10 at 16:23 -0600, Mike Klinke wrote:
On Friday 10 March 2006 15:52, Rahul Sundaram wrote:
Surely a remote user is prohibited, by default, from shutting down a computer in a locked facility, no?
Yes. The user gets permissions only when he's the only logged in user on the machine's console. That is, not ssh and not a remote X session.
This has been this way *for years*.
On Fri, 2006-03-10 at 13:46 -0800, Leslie Satenstein wrote:
As for being able to shutdown from any account. It says that Core5 cannot be used as a server and also have another guest user who could issue that command. I should not have to modify the halt / shutdown / reboot stuff to add security. If I want a guest end user to do a shutdown,
Can you tell me exactly how a non-root user can initiate a shutdown? Aside from say the gnome shutdown menu...
Jesse Keating wrote:
On Fri, 2006-03-10 at 13:46 -0800, Leslie Satenstein wrote:
As for being able to shutdown from any account. It says that Core5 cannot be used as a server and also have another guest user who could issue that command. I should not have to modify the halt / shutdown / reboot stuff to add security. If I want a guest end user to do a shutdown,
Can you tell me exactly how a non-root user can initiate a shutdown? Aside from say the gnome shutdown menu...
the "poweroff" or "reboot" commands?
-Dan
On Fri, 2006-03-10 at 17:14 -0500, Jesse Keating wrote:
On Fri, 2006-03-10 at 13:46 -0800, Leslie Satenstein wrote:
As for being able to shutdown from any account. It says that Core5 cannot be used as a server and also have another guest user who could issue that command. I should not have to modify the halt / shutdown / reboot stuff to add security. If I want a guest end user to do a shutdown,
Can you tell me exactly how a non-root user can initiate a shutdown? Aside from say the gnome shutdown menu...
The _console_ user can do a shutdown from the gnome Desktop menu.
Same applies for anyone with physical access to the console even if the user is not logged in. (As long as no one is logged in on the console with the screen locked.) The option is on the console login screen.
This is part of why the stress on security _includes_ physical access limitations.