-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 a
On Thu, Jan 20, 2011 at 10:34 AM, Sorin Srbu sorin.s...@orgfarm.uu.se wrote:
-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
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
2011/1/18 Drew Weaver drew.wea...@thenap.com:
Because the installer doesn't have drivers for the onboard and all of our
installs are PXE and in general it removes a lot of confusion by just
disabling the onboard NIC and having one single NIC for everything.
Drew, out of curiosity (I have a
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
Hi all,
Has anyone successfully applied the LTTng patch to CentOS 5.4 kernel?
According to the LTTng compatibility table patch28-2.6.18-lttng-0.6.41
is the one that should be used but a number of the patch files did not
apply cleanly. It generated a number of rejects.
If anyone has
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 if there is an
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
Hello listmates,
I've got this Centos 5.5 box which I am trying to configure as an
OpenVPN server. Now 2.1.4 seems to have added pkcs11 support and that
stops me from creating the CA and other necessary files:
[root@gw5fl 2.0]# . ./vars
bash:
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 Wednesday, January 19, 2011 06:38:12 pm Scott Robbins wrote:
Boot has to be huge in Fedora for the preupgrade to have a chance of
working--having given up on it several releases ago, I have no idea if
it's been improved or not.
This is obviously straying from the topicality of this list,
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
Lamar Owen wrote:
On Wednesday, January 19, 2011 06:38:12 pm Scott Robbins wrote:
Boot has to be huge in Fedora for the preupgrade to have a chance of
working--having given up on it several releases ago, I have no idea if
it's been improved or not.
This is obviously straying from the
On Thu, Jan 20, 2011 at 5:46 PM, Lamar Owen lo...@pari.edu wrote:
This is obviously straying from the topicality of this list, but yes the
mechanism has been improved at least between F13 and F14, as I did do a
preupgrade on my development/testing box, which will likely go to CentOS 6 or
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
On Thu, Jan 20, 2011 at 11:46 AM, Lamar Owen lo...@pari.edu wrote:
On Wednesday, January 19, 2011 06:38:12 pm Scott Robbins wrote:
Boot has to be huge in Fedora for the preupgrade to have a chance of
working--having given up on it several releases ago, I have no idea if
it's been improved or
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'
[root@gw5fl 2.0]# . ./vars
bash: /usr/share/doc/openvpn-2.1.4/easy-rsa/2.0/whichopensslcnf:
Permission denied
See that error above? Make that script executable... It's a bash script
`vars` is calling and not able to execute.
___
CentOS mailing list
On 1/20/2011 10:53 AM, Parshwa Murdia wrote:
On Thu, Jan 20, 2011 at 5:46 PM, Lamar Owenlo...@pari.edu wrote:
This is obviously straying from the topicality of this list, but yes the
mechanism has been improved at least between F13 and F14, as I did do a
preupgrade on my
On Thu, Jan 20, 2011 at 12:03 PM, Joseph L. Casale
jcas...@activenetwerx.com wrote:
[root@gw5fl 2.0]# . ./vars
bash: /usr/share/doc/openvpn-2.1.4/easy-rsa/2.0/whichopensslcnf:
Permission denied
See that error above? Make that script executable... It's a bash script
`vars` is calling and not
Thanks, did that though this did not fix my problem - I still get the
same error message.
The only error I saw was a lack of ability to run whichopensslcnf.
pkitool is a shell script which should be executable and in that folder as
well. Is it executable?
On Thu, Jan 20, 2011 at 12:25 PM, Joseph L. Casale
jcas...@activenetwerx.com wrote:
Thanks, did that though this did not fix my problem - I still get the
same error message.
The only error I saw was a lack of ability to run whichopensslcnf.
pkitool is a shell script which should be executable
Boris Epstein wrote:
On Thu, Jan 20, 2011 at 12:03 PM, Joseph L. Casale
jcas...@activenetwerx.com wrote:
[root@gw5fl 2.0]# . ./vars
bash: /usr/share/doc/openvpn-2.1.4/easy-rsa/2.0/whichopensslcnf:
Permission denied
See that error above? Make that script executable... It's a bash script
`vars`
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
On Thu, Jan 20, 2011 at 12:39 PM, m.r...@5-cent.us wrote:
Boris Epstein wrote:
On Thu, Jan 20, 2011 at 12:03 PM, Joseph L. Casale
jcas...@activenetwerx.com wrote:
[root@gw5fl 2.0]# . ./vars
bash: /usr/share/doc/openvpn-2.1.4/easy-rsa/2.0/whichopensslcnf:
Permission denied
See that error
Hi everyone.
I just wondered what's the difference between
/var/log/dmesg, and /var/log/messages?
Why do we have 2 log files that are similar?
Kind Regards,
Keith Roberts
-
Websites:
http://www.karsites.net
dmesg is everything sent from the kernel for logging (ie. the historical
content of the dmesg(8) command).
messages is basically a syslog fall-through (a bit like /var/log/syslog)
On 21/01/2011, at 7:02 AM, Keith Roberts wrote:
Hi everyone.
I just wondered what's the difference between
On Fri, 21 Jan 2011, Cameron Kerr wrote:
dmesg is everything sent from the kernel for logging (ie. the
historical content of the dmesg(8) command).
messages is basically a syslog fall-through (a bit like /var/log/syslog)
See /etc/rc.sysinit for dmesg invocation that writes to
On Thu, 20 Jan 2011, Paul Heinlein wrote:
To: CentOS mailing list centos@centos.org
From: Paul Heinlein heinl...@madboa.com
Subject: Re: [CentOS] dmesg and messages differences
On Fri, 21 Jan 2011, Cameron Kerr wrote:
dmesg is everything sent from the kernel for logging (ie. the
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
Boris Epstein wrote:
On Thu, Jan 20, 2011 at 12:39 PM, m.r...@5-cent.us wrote:
Boris Epstein wrote:
On Thu, Jan 20, 2011 at 12:03 PM, Joseph L. Casale
jcas...@activenetwerx.com wrote:
[root@gw5fl 2.0]# . ./vars
bash: /usr/share/doc/openvpn-2.1.4/easy-rsa/2.0/whichopensslcnf:
Permission denied
On 01/20/11 10:02 AM, Keith Roberts wrote:
Hi everyone.
I just wondered what's the difference between
/var/log/dmesg, and /var/log/messages?
/var/log/dmesg is a dump of the output of the dmesg command shortly
after boot by rc.sysinit. this is done because the kernel message
buffer that
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
On Jan 18, 2011, at 5:40 AM, Pasi Kärkkäinen wrote:
On Mon, Jan 17, 2011 at 04:46:49PM -0800, aurfal...@gmail.com wrote:
Hi all,
I'm running Centos 5.5 with Xen 4.0.1
Would like to use a USB key (not a block device) in my domU.
Dom0 lsusb yields;
Bus 002 Device 004: ID 064f:0bd8
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 11:52:48 am m.r...@5-cent.us wrote:
Lamar Owen wrote:
mechanism has been improved at least between F13 and F14, as I did do a
preupgrade on my development/testing box, which will likely go to CentOS 6
or SL6 some time RSN.
snip
Could you define improved? My
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/20/2011 01:39 PM, m.r...@5-cent.us wrote:
Boris Epstein wrote:
On Thu, Jan 20, 2011 at 12:39 PM, m.r...@5-cent.us wrote:
Boris Epstein wrote:
On Thu, Jan 20, 2011 at 12:03 PM, Joseph L. Casale
jcas...@activenetwerx.com wrote:
[root@gw5fl
On Thursday, January 20, 2011 11:53:52 am Parshwa Murdia wrote:
You say for SL6, would it sometimes prove better than stable CentOS?
As Les said, it depends by what you consider to be 'better.' I consider them
to be roughly equivalent, with SL having some advantages (mostly of perception
in
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
chcon -t bin_t -R /usr/share/doc/openvpn-2.1.4/easy-rsa
Will prpbably fix.
-BEGIN PGP SIGNATURE-
Just tried that, thanks.
Unfortunately, it did not.
Boris.
___
CentOS mailing list
CentOS@centos.org
Lamar Owen wrote:
On Thursday, January 20, 2011 11:52:48 am m.r...@5-cent.us wrote:
Lamar Owen wrote:
mechanism has been improved at least between F13 and F14, as I did do
a
preupgrade on my development/testing box, which will likely go to
CentOS 6 or SL6 some time RSN.
snip
Could you
Boris,
Are you using bash?
Try this:
/bin/bash
. ./vars
--
Peter
On 01/20/2011 08:28 AM, Boris Epstein wrote:
Hello listmates,
I've got this Centos 5.5 box which I am trying to configure as an
OpenVPN server. Now 2.1.4 seems to have added pkcs11 support and that
stops me from creating the
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.
On 1/20/2011 12:58 PM, Lamar Owen wrote:
mechanism has been improved at least between F13 and F14, as I did do a
preupgrade on my development/testing box, which will likely go to CentOS 6
or SL6 some time RSN.
snip
Could you define improved? My wish list would include I (fedora) will
On Thu, Jan 20, 2011 at 2:46 PM, Peter Blajev pbla...@ucsd.edu wrote:
Boris,
Are you using bash?
Try this:
/bin/bash
. ./vars
--
Peter
Peter,
Yes, I am using bash:
[root@gw5fl 2.0]# echo $SHELL
/bin/bash
[root@gw5fl 2.0]#
Boris.
___
CentOS
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
On Thu, Jan 20, 2011 at 06:28:35PM +, Keith Roberts wrote:
On Thu, 20 Jan 2011, Paul Heinlein wrote:
To: CentOS mailing list centos@centos.org
From: Paul Heinlein heinl...@madboa.com
Subject: Re: [CentOS] dmesg and messages differences
On Fri, 21 Jan 2011, Cameron Kerr 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
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
Keith Keller wrote:
snip
Specifically, man syslog.conf for that file's syntax; man syslogd talks
more about its invocation and signalling.
And the difference can be *very* important. For example, last night, one
of our servers had a h/d crap out, and dropped to ro. However, all of them
copy the
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
Hi, I have a centos 5 (current) mail server that I have compiled
dovecot/postfix and installed some packages like mysql etc. These packages
have been configured and changed to my liking. How can I now save all this
and install it on another server without having to do all the work of
compiling
PA wrote:
Hi, I have a centos 5 (current) mail server that I have compiled
dovecot/postfix and installed some packages like mysql etc. These
packages have been configured and changed to my liking. How can I now
save all this and install it on another server without having to do
all the
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
I guess what I was asking for is to take a already configured server and put
it on multiple CD's DVD's and then use that to install on another server.
-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf
Of Corey A Johnson
Sent: Thursday,
On 1/20/2011 2:47 PM, PA wrote:
Hi, I have a centos 5 (current) mail server that I have compiled
dovecot/postfix and installed some packages like mysql etc. These
packages have been configured and changed to my liking. How can I now
save all this and install it on another server without having
Hi all,
I'm having fun getting to know xfs_quotas.
I do notice some irregularities.
When running xfs_quota -s -c /dev/sdc1
And then running report -h, for user barney, his used space is 4.9G
while his soft/hard limit is 5G.
Since I set 5, all is well, but when I run du -hs on barnies dir,
1 - 100 of 125 matches
Mail list logo
