on 13:11 Fri 21 Jan, Michael Gliwinski (michael.gliwin...@henderson-group.com)
wrote:
On Thursday 20 Jan 2011 22:26:08 Bob Eastbrook wrote:
On Wed, Jan 19, 2011 at 12:18 PM, m.r...@5-cent.us wrote:
But the locked screensaver wants the *same* password that you log in
with. I'm having
-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
Behalf Of Joshua Baker-LePain
Sent: Thursday, January 20, 2011 4:49 PM
To: CentOS mailing list
Subject: Re: [CentOS] How to disable screen locking system-wide?
I was going to leave this alone, but I
-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
Behalf Of Mike McCarty
Sent: Thursday, January 20, 2011 9:08 PM
To: CentOS mailing list
Subject: Re: [CentOS] How to disable screen locking system-wide?
OTOH, I have cats :-)
Funny you should mention
On Thu, Jan 20, 2011 at 11:52 AM, Rudi Ahlers r...@softdux.com wrote:
On Thu, Jan 20, 2011 at 6:44 PM, Tom H tomh0...@gmail.com wrote:
You clearly work in an insecure environment.
By who's definition? The fact that you're PC is connected to the
internet place you in the same environment :)
On Thu, Jan 20, 2011 at 12:45 PM, Giles Coochey gi...@coochey.net wrote:
And in those nine years you claim to have had at least one major security
incident.
It beggars my belief
You now publicly declare that your company not just advocates the sharing of
passwords, but certainly
On Thu, Jan 20, 2011 at 5:53 PM, Ross Walker rswwal...@gmail.com wrote:
On Thu, Jan 20, 2011 at 12:03 PM, m.r...@5-cent.us wrote:
I can beat that: I read, a month or so ago, how a bunch of elementary
school kids discovered that wet Gummi Bears would hold a fingerprint,
*and* (they didn't
Greetings,
On 1/21/11, JohnS jse...@gmail.com wrote:
On Thu, 2011-01-20 at 20:13 -0600, Mike McCarty wrote:
This is on software which ran as POS stuff.
hmm... how about a vlock -a (or inverse thereof) wrapper?
Regards,
Rajagopal
___
CentOS
On Thursday 20 Jan 2011 22:26:08 Bob Eastbrook wrote:
On Wed, Jan 19, 2011 at 12:18 PM, m.r...@5-cent.us wrote:
But the locked screensaver wants the *same* password that you log in
with. I'm having trouble understanding the problem... or is it that many
of the users *never* log out?
On Thursday, January 20, 2011 05:53:14 pm Ross Walker wrote:
I haven't heard of someone lifting a latent oil print
and creating a fake out of that. I'm sure with enough ingenuity it can
be done.
Let me repeat: that is exactly what MythBusters did in the episode I
referenced, 'Crime and
Rajagopal Swaminathan wrote:
Greetings,
On 1/21/11, JohnS jse...@gmail.com wrote:
On Thu, 2011-01-20 at 20:13 -0600, Mike McCarty wrote:
This is on software which ran as POS stuff.
hmm... how about a vlock -a (or inverse thereof) wrapper?
We wanted to log the user out of the POS
-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
Behalf Of Joshua Baker-LePain
Sent: Wednesday, January 19, 2011 8:47 PM
To: CentOS mailing list
Subject: Re: [CentOS] How to disable screen locking system-wide?
By default, CentOS v5 requires
to disable screen locking system-wide?
By default, CentOS v5 requires a user's password when the system wakes
up from the screensaver. This can be disabled by each user, but how
can I disable this system-wide? Many of my users forget to do this,
which results in workstations being locked up
On Wed, Jan 19, 2011 at 10:35 PM, Keith Keller
kkel...@wombat.san-francisco.ca.us wrote:
For the OP: what's the goal behind preventing an X session from locking?
Perhaps there is a more elegant solution than simply disabling it.
--keith
--
kkel...@wombat.san-francisco.ca.us
It probably
-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
Behalf Of Rudi Ahlers
Sent: Thursday, January 20, 2011 9:55 AM
To: CentOS mailing list
Subject: Re: [CentOS] How to disable screen locking system-wide?
By default, CentOS v5 requires a user's
On Thu, 20 Jan 2011, Rudi Ahlers wrote:
I don't know about you, but a user leaving his desk (for any purpose,
other than going home) doesn't cause a security risk. I trust all our
staff, and when Andrew goes on lunch I expect him to leave his PC
unlocked.
I think I see things differently.
On Thu, Jan 20, 2011 at 12:00 PM, John Hodrien j.h.hodr...@leeds.ac.uk wrote:
I think I see things differently. Allowing others to access your account *is*
a security risk. It potentially opens confidential data open to other people,
and leaves that specific user open to abuse through
On 20/01/2011 11:55, Rudi Ahlers wrote:
On Thu, Jan 20, 2011 at 12:00 PM, John Hodrienj.h.hodr...@leeds.ac.uk wrote:
I think I see things differently. Allowing others to access your account *is*
a security risk. It potentially opens confidential data open to other people,
and leaves that
On Thu, 20 Jan 2011, Rudi Ahlers wrote:
I think I see things differently. Allowing others to access your account *is*
a security risk. It potentially opens confidential data open to other people,
and leaves that specific user open to abuse through people using their
machine. You might as
On 19/01/2011 21:35, Keith Keller wrote:
Are the screensavers not smart enough to intercept ctrl-alt-bksp?
For the OP: what's the goal behind preventing an X session from locking?
Perhaps there is a more elegant solution than simply disabling it.
Screensavers can't intercept... X gets the
On Thu, Jan 20, 2011 at 4:00 AM, Rudi Ahlers r...@softdux.com wrote:
It probably depends on his environment. If it's an office where people
actually work for money and need to address client issues then I'm
sure your colleagues won't be please if you make them loose all their
work just to be
On Thu, 2011-01-20 at 11:05 +, John Hodrien wrote:
An account is a personal account that should not be shared.
+1
Also, at least in the United States, locking a PC / workstation after 15
minutes of idle is a requirement of PCI/DSS - which your company almost
certainly agreed to if you
-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
Behalf Of Tom H
Sent: Thursday, January 20, 2011 1:03 PM
To: CentOS mailing list
Subject: Re: [CentOS] How to disable screen locking system-wide?
In our environment, leaving your desk without locking
On Thu, 20 Jan 2011, Sorin Srbu wrote:
-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
Behalf Of Tom H
Sent: Thursday, January 20, 2011 1:03 PM
To: CentOS mailing list
Subject: Re: [CentOS] How to disable screen locking system-wide?
In our
On Thu, Jan 20, 2011 at 7:55 AM, Sorin Srbu sorin.s...@orgfarm.uu.se wrote:
-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
Behalf Of Tom H
Sent: Thursday, January 20, 2011 1:03 PM
To: CentOS mailing list
Subject: Re: [CentOS] How to disable screen
On 20/01/2011 13:12, Adam Tauno Williams wrote:
On Thu, 2011-01-20 at 11:05 +, John Hodrien wrote:
An account is a personal account that should not be shared.
+1
Also, at least in the United States, locking a PC / workstation after 15
minutes of idle is a requirement of PCI/DSS - which
-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
Behalf Of John Hodrien
Sent: Thursday, January 20, 2011 2:02 PM
To: CentOS mailing list
Subject: Re: [CentOS] How to disable screen locking system-wide?
I don't know the exact path but you can use
On 01/20/2011 02:55 AM, Rudi Ahlers wrote:
I don't agree with that, sorry.
A few years ago one of our staff members decided his salary isn't good
enough so he started a side-line business, on our company time. He
stole some of our client's data (contact details, emails, and even
contracts)
On Thu, 20 Jan 2011, Tom H wrote:
Yes but someone's posted a global gconftool-2 recipe.
Run gconf-editor as root and you can edit the global mandatory rules too.
jh
___
CentOS mailing list
CentOS@centos.org
On Thu, 2011-01-20 at 14:08 +0100, Giles Coochey wrote:
On 20/01/2011 13:12, Adam Tauno Williams wrote:
On Thu, 2011-01-20 at 11:05 +, John Hodrien wrote:
An account is a personal account that should not be shared.
+1
Also, at least in the United States, locking a PC / workstation
On Jan 19, 2011, at 2:44 PM, Bob Eastbrook baconeater...@gmail.com wrote:
By default, CentOS v5 requires a user's password when the system wakes
up from the screensaver. This can be disabled by each user, but how
can I disable this system-wide? Many of my users forget to do this,
which
On Jan 19, 2011, at 2:44 PM, Bob Eastbrook baconeater...@gmail.com wrote:
By default, CentOS v5 requires a user's password when the system wakes
up from the screensaver. This can be disabled by each user, but how
can I disable this system-wide? Many of my users forget to do this,
which
On Thu, 20 Jan 2011, Ross Walker wrote:
On Jan 19, 2011, at 2:44 PM, Bob Eastbrook baconeater...@gmail.com wrote:
By default, CentOS v5 requires a user's password when the system wakes
up from the screensaver. This can be disabled by each user, but how
can I disable this system-wide? Many
Adam Tauno Williams wrote:
On Thu, 2011-01-20 at 14:08 +0100, Giles Coochey wrote:
On 20/01/2011 13:12, Adam Tauno Williams wrote:
On Thu, 2011-01-20 at 11:05 +, John Hodrien wrote:
An account is a personal account that should not be shared.
snip
While such standards are much-maligned I
On Jan 20, 2011, at 9:18 AM, John Hodrien j.h.hodr...@leeds.ac.uk wrote:
On Thu, 20 Jan 2011, Ross Walker wrote:
On Jan 19, 2011, at 2:44 PM, Bob Eastbrook baconeater...@gmail.com wrote:
By default, CentOS v5 requires a user's password when the system wakes
up from the screensaver. This
On Jan 20, 2011, at 9:23 AM, m.r...@5-cent.us wrote:
Adam Tauno Williams wrote:
On Thu, 2011-01-20 at 14:08 +0100, Giles Coochey wrote:
On 20/01/2011 13:12, Adam Tauno Williams wrote:
On Thu, 2011-01-20 at 11:05 +, John Hodrien wrote:
An account is a personal account that should not be
Ross Walker wrote:
On Jan 20, 2011, at 9:18 AM, John Hodrien j.h.hodr...@leeds.ac.uk wrote:
On Thu, 20 Jan 2011, Ross Walker wrote:
On Jan 19, 2011, at 2:44 PM, Bob Eastbrook baconeater...@gmail.com
wrote:
By default, CentOS v5 requires a user's password when the system wakes
up from the
Ross Walker wrote:
On Jan 20, 2011, at 9:23 AM, m.r...@5-cent.us wrote:
Adam Tauno Williams wrote:
On Thu, 2011-01-20 at 14:08 +0100, Giles Coochey wrote:
On 20/01/2011 13:12, Adam Tauno Williams wrote:
On Thu, 2011-01-20 at 11:05 +, John Hodrien wrote:
An account is a personal account
On Thursday 20 January 2011 09:14, Ross Walker wrote:
On Jan 19, 2011, at 2:44 PM, Bob Eastbrook baconeater...@gmail.com wrote:
By default, CentOS v5 requires a user's password when the system wakes
up from the screensaver. This can be disabled by each user, but how
can I disable this
By default, CentOS v5 requires a user's password when the system wakes
up from the screensaver. This can be disabled by each user, but how
can I disable this system-wide? Many of my users forget to do this,
which results in workstations being locked up.
Instead of removing the lock on your
-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
Behalf Of Ross Walker
Sent: Thursday, January 20, 2011 3:27 PM
To: CentOS mailing list
Cc: CentOS mailing list
Subject: Re: [CentOS] How to disable screen locking system-wide?
I wonder
On Thu, 20 Jan 2011 at 11:00am, Rudi Ahlers wrote
It probably depends on his environment. If it's an office where people
actually work for money and need to address client issues then I'm
sure your colleagues won't be please if you make them loose all their
work just to be an arrogant IT
On 1/20/2011 8:18 AM, John Hodrien wrote:
KDE has a multi-user x login feature that allows another user to start a new
session keeping the existing session active.
It might take a little config mod'ing to get it working, but it works. It
works best if there is lots of RAM.
So does gnome
Joshua Baker-LePain wrote:
On Thu, 20 Jan 2011 at 11:00am, Rudi Ahlers wrote
It probably depends on his environment. If it's an office where people
snip
situations, and it certainly doesn't make me arrogant or unprofessional.
As others have pointed out, there are industries and workplaces
On Thu, 20 Jan 2011, m.r...@5-cent.us wrote:
Excuse me, but when I was in college, I heard the spiel about not leaving
workstations unlocked, if only because some idiots would get cute and do
something from your terminal to embarrass you, and/or aggravate someone
else.
cat .bashrc EOF
echo
On Thu, Jan 20, 2011 at 3:47 PM, Jerry Franz jfr...@freerun.com wrote:
On 01/20/2011 02:55 AM, Rudi Ahlers wrote:
I don't agree with that, sorry.
A few years ago one of our staff members decided his salary isn't good
enough so he started a side-line business, on our company time. He
stole
On Thu, 20 Jan 2011, Rudi Ahlers wrote:
Benjamin, I'm sorry to say this, but you're wrong!
I'm fairly sure he's not.
Now, since we're doing the name-calling thing, let's get that out of the way.
Sometimes you need to access a PC of a staff member who is busy with
something right now. And
On Thursday, January 20, 2011 03:54:45 am Rudi Ahlers wrote:
Yup, and it totally defeats the purpose of what the OP actually wanted
todo. Imagine your account being busy with your year-end books, and
has to run to the toilet (she is a bit sick) now you come and press
CTRL+ALT+Bksp and loose
On 20/01/2011 17:11, Rudi Ahlers wrote:
The message I'm trying to bring across is that users in the company
shouldn't have passwords which admin doesn't know, or can't access.
The PC's and data, well at least in our company, is the property of
the company. Making it more difficult for an
On 1/20/2011 10:11 AM, Rudi Ahlers wrote:
Benjamin, I'm sorry to say this, but you're wrong!
Now, since we're doing the name-calling thing, let's get that out of the way.
Sometimes you need to access a PC of a staff member who is busy with
something right now. And I'm not talking about
On Thursday, January 20, 2011 06:02:38 am Giles Coochey wrote:
Data and Accounts are distinct, and the policies regarding their use
should be distinct too.
+1.
The third 'A' of triple-A (AAA) is accountability. If you share accounts you
defeat accountability. This has nothing to do with
Rudi Ahlers wrote:
On Thu, Jan 20, 2011 at 3:47 PM, Jerry Franz jfr...@freerun.com wrote:
On 01/20/2011 02:55 AM, Rudi Ahlers wrote:
snip
If you don't have full administrative access to the machine
*independent* of people's day-to-day login accounts you are doing it
wrong and need to hire a
On Thu, Jan 20, 2011 at 11:11 AM, Rudi Ahlers r...@softdux.com wrote:
Sometimes you need to access a PC of a staff member who is busy with
something right now. And I'm not talking about administrative access.
Sure, I can access any PC via root login, and frankly for that matter
I can also
On Thu, Jan 20, 2011 at 6:29 PM, Giles Coochey gi...@coochey.net wrote:
On 20/01/2011 17:11, Rudi Ahlers wrote:
The message I'm trying to bring across is that users in the company
shouldn't have passwords which admin doesn't know, or can't access.
The PC's and data, well at least in our
On Thu, Jan 20, 2011 at 9:06 AM, John Hodrien j.h.hodr...@leeds.ac.uk wrote:
On Thu, 20 Jan 2011, Tom H wrote:
Yes but someone's posted a global gconftool-2 recipe.
Run gconf-editor as root and you can edit the global mandatory rules too.
Very true, as long as you can run a GUI app as root.
On Thu, Jan 20, 2011 at 6:44 PM, Tom H tomh0...@gmail.com wrote:
You clearly work in an insecure environment.
By who's definition? The fact that you're PC is connected to the
internet place you in the same environment :)
No one should have access to anyone else's login. I have no admin
On Thursday, January 20, 2011 09:36:09 am Ross Walker wrote:
With Amazon's cloud services now I guess they'll have to cut it down to 7
days, or require finger print or retinal eye scans...
Fingerprints are too easily faked. Mythbusters did it in a 'Crime and
Mythdemeanors' episode a few
Lamar Owen wrote:
On Thursday, January 20, 2011 09:36:09 am Ross Walker wrote:
With Amazon's cloud services now I guess they'll have to cut it down to
7 days, or require finger print or retinal eye scans...
Fingerprints are too easily faked. Mythbusters did it in a 'Crime and
Mythdemeanors'
And in those nine years you claim to have had at least one major security
incident.
It beggars my belief
You now publicly declare that your company not just advocates the sharing of
passwords, but certainly encourages it, if not make it compulsory.
If you were to have another security
Giles Coochey wrote:
And in those nine years you claim to have had at least one major security
incident.
It beggars my belief
From: Rudi Ahlers r...@softdux.com
On Thu, Jan 20, 2011 at 6:29 PM, Giles Coochey gi...@coochey.net wrote:
On 20/01/2011 17:11, Rudi Ahlers wrote:
snip
I'm
On Thursday, January 20, 2011 12:03:27 pm m.r...@5-cent.us wrote:
Lamar Owen wrote:
Fingerprints are too easily faked. Mythbusters did it in a 'Crime and
Mythdemeanors' episode a few years ago.
I can beat that: I read, a month or so ago, how a bunch of elementary
school kids discovered
Lamar Owen wrote:
On Thursday, January 20, 2011 12:03:27 pm m.r...@5-cent.us wrote:
Lamar Owen wrote:
Fingerprints are too easily faked. Mythbusters did it in a 'Crime and
Mythdemeanors' episode a few years ago.
I can beat that: I read, a month or so ago, how a bunch of elementary
school
On Thursday, January 20, 2011 01:57:54 pm m.r...@5-cent.us wrote:
We (the Feds) are using PIV cards, which have passkeys, and, of course,
the username. I prefer what I have from my employer: the RSA keyfobs. No
trouble at all, *and* you need the username, keyfob and a pin.
Our co-lo site is
Lamar Owen wrote:
On Thursday, January 20, 2011 01:57:54 pm m.r...@5-cent.us wrote:
We (the Feds) are using PIV cards, which have passkeys, and, of course,
the username. I prefer what I have from my employer: the RSA keyfobs. No
trouble at all, *and* you need the username, keyfob and a pin.
John Hodrien wrote:
On Thu, 20 Jan 2011, Rudi Ahlers wrote:
I don't know about you, but a user leaving his desk (for any purpose,
other than going home) doesn't cause a security risk. I trust all our
staff, and when Andrew goes on lunch I expect him to leave his PC
unlocked.
I think I
On Thu, Jan 20, 2011 at 09:51:28AM -0500, Robert Spangler wrote:
On Thursday 20 January 2011 09:14, Ross Walker wrote:
KDE has a multi-user x login feature that allows another user to start a
new session keeping the existing session active.
And if that doesn't work you could always;
Rudi Ahlers wrote:
On Thu, Jan 20, 2011 at 12:00 PM, John Hodrien j.h.hodr...@leeds.ac.uk
wrote:
I think I see things differently. Allowing others to access your account
*is*
a security risk. It potentially opens confidential data open to other
people,
and leaves that specific
Giles Coochey wrote:
[...]
A user account should belong to the person who has been assigned that
account. They are the only person who should be able to use that
You are conflating access and ownership. The company should
own the machine and the data. Only persons authorized by the
company
Giles Coochey wrote:
[...]
I can't speak for HIPPA, SOX etc... but automatic locking is part of IT
best practice.
I can. I did a contract job a few years ago to achieve HIPPA compliance
with some pharmacy software. I inserted time limits with logout, screen
information blanking, and RAM
Mike McCarty wrote:
John Hodrien wrote:
On Thu, 20 Jan 2011, Rudi Ahlers wrote:
snip
At home, I keep my keyboard locked the instant I leave it because
of potential security breaches, using the little lock screen (sic)
button on the pop up menu on the left. Just about the only GUI button
I
Mike McCarty wrote:
Giles Coochey wrote:
[...]
I can't speak for HIPPA, SOX etc... but automatic locking is part of IT
best practice.
I can. I did a contract job a few years ago to achieve HIPPA compliance
with some pharmacy software. I inserted time limits with logout, screen
Rudi Ahlers wrote:
[...]
User accounts also doesn't mean much to me. I know how it sounds, but
I care more about the data than the user's account. As long as I can
access whatever I want, whenever I want.
ISTM that you have control issues. Access to data is what counts,
and you've got that
Sorin Srbu wrote:
-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
Behalf Of Tom H
Sent: Thursday, January 20, 2011 1:03 PM
To: CentOS mailing list
Subject: Re: [CentOS] How to disable screen locking system-wide?
In our environment, leaving
Mike McCarty wrote:
[...]
IANAL, but I suggest that anyone who has any intellectual
property (patents, trade secrets, trade marks) get a lawyer
Oops! Forgot copyright. Those are the ones in the USA.
There may be others in other countries. I don't know.
Anyway, trade secrets are very hard to
On Thursday, January 20, 2011 03:11:00 pm Mike McCarty wrote:
That does not preclude access to the machine's content. Anyone
with root access should be able to do that. You shouldn't
have to log in AS THAT USER in order to access the computer's
content.
Although I have seen in the case of
On Wed, Jan 19, 2011 at 12:18 PM, m.r...@5-cent.us wrote:
But the locked screensaver wants the *same* password that you log in with.
I'm having trouble understanding the problem... or is it that many of the
users *never* log out?
Yes, users will sign onto a workstation, and then disappear
On Thu, Jan 20, 2011 at 12:03 PM, m.r...@5-cent.us wrote:
Lamar Owen wrote:
On Thursday, January 20, 2011 09:36:09 am Ross Walker wrote:
With Amazon's cloud services now I guess they'll have to cut it down to
7 days, or require finger print or retinal eye scans...
Fingerprints are too
On Thu, 2011-01-20 at 14:18 -0600, Mike McCarty wrote:
Giles Coochey wrote:
[...]
I can't speak for HIPPA, SOX etc... but automatic locking is part of IT
best practice.
I can. I did a contract job a few years ago to achieve HIPPA compliance
with some pharmacy software. I inserted
On Thu, Jan 20, 2011 at 2:00 AM, John Hodrien j.h.hodr...@leeds.ac.uk wrote:
For gnome how about something like:
gconftool-2 --direct \
--config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --type bool \
--set /apps/gnome-screensaver/lock_enabled false
Many thanks. That did the
On 01/20/2011 02:53 PM, Ross Walker wrote:
Fortunately I don't go sticking my fingers in wet gummy bears, so that
risk is mitigated!
While finger prints can be faked, it often requires access to the
finger to fake. I haven't heard of someone lifting a latent oil print
and creating a fake out
JohnS wrote:
On Thu, 2011-01-20 at 14:18 -0600, Mike McCarty wrote:
Giles Coochey wrote:
[...]
I can't speak for HIPPA, SOX etc... but automatic locking is part of IT
best practice.
I can. I did a contract job a few years ago to achieve HIPPA compliance
with some pharmacy software. I
On Thu, 2011-01-20 at 20:13 -0600, Mike McCarty wrote:
This is on software which ran as POS stuff.
Yea but the catch is it is left up to YOU being responsible for what
happens on that network. Very candid HIPPA states only `data at rest`
does not have to be. In my state I live in I am the
On Wed, 19 Jan 2011 at 11:44am, Bob Eastbrook wrote
By default, CentOS v5 requires a user's password when the system wakes
up from the screensaver. This can be disabled by each user, but how
can I disable this system-wide? Many of my users forget to do this,
which results in workstations
On Wed, Jan 19, 2011 at 9:46 PM, Joshua Baker-LePain jl...@duke.edu wrote:
On Wed, 19 Jan 2011 at 11:44am, Bob Eastbrook wrote
By default, CentOS v5 requires a user's password when the system wakes
up from the screensaver. This can be disabled by each user, but how
can I disable this
On Wed, 19 Jan 2011 at 9:49pm, Rudi Ahlers wrote
On Wed, Jan 19, 2011 at 9:46 PM, Joshua Baker-LePain jl...@duke.edu wrote:
On Wed, 19 Jan 2011 at 11:44am, Bob Eastbrook wrote
By default, CentOS v5 requires a user's password when the system wakes
up from the screensaver. This can be
On 1/19/11 11:49 AM, Rudi Ahlers wrote:
On Wed, Jan 19, 2011 at 9:46 PM, Joshua Baker-LePain jl...@duke.edu wrote:
On Wed, 19 Jan 2011 at 11:44am, Bob Eastbrook wrote
By default, CentOS v5 requires a user's password when the system wakes
up from the screensaver. This can be disabled by
Sean Hart wrote:
On 1/19/11 11:49 AM, Rudi Ahlers wrote:
On Wed, Jan 19, 2011 at 9:46 PM, Joshua Baker-LePain jl...@duke.edu
wrote:
On Wed, 19 Jan 2011 at 11:44am, Bob Eastbrook wrote
By default, CentOS v5 requires a user's password when the system wakes
up from the screensaver. This can
On Wed, Jan 19, 2011 at 03:18:37PM -0500, m.r...@5-cent.us wrote:
Sean Hart wrote:
On 1/19/11 11:49 AM, Rudi Ahlers wrote:
I believe that CTRL-ALT-Bksp will restart X, not the computer. On
restart of X you should be welcomed with the login screen.
Note that in later versions of X,
On Wed, Jan 19, 2011 at 03:18:37PM -0500, m.r...@5-cent.us wrote:
But the locked screensaver wants the *same* password that you log in with.
I'm having trouble understanding the problem... or is it that many of the
users *never* log out?
The locked screensaver will be killed along with the
On Wed, 2011-01-19 at 15:29 -0500, Scott Robbins wrote:
On Wed, Jan 19, 2011 at 03:18:37PM -0500, m.r...@5-cent.us wrote:
Sean Hart wrote:
On 1/19/11 11:49 AM, Rudi Ahlers wrote:
I believe that CTRL-ALT-Bksp will restart X, not the computer. On
restart of X you should be
89 matches
Mail list logo
