LISTSERV - SCIENTIFIC-LINUX-USERS Archives

SCIENTIFIC-LINUX-USERS Archives

April 2011

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

	LISTSERV Archives
	SCIENTIFIC-LINUX-USERS Home
	SCIENTIFIC-LINUX-USERS April 2011

	Log In
	Register

	Subscribe or Unsubscribe

	Search Archives

Options:	Use Monospaced Font Show Text Part by Default Show All Mail Headers
Message:	[<< First] [< Prev] [Next >] [Last >>]
Topic:	[<< First] [< Prev] [Next >] [Last >>]
Author:	[<< First] [< Prev] [Next >] [Last >>]

Subject:	Upstream fault? sshd re-chkconfiging
From:	"Robert E. Blair" <[log in to unmask]>
Reply To:	Robert E. Blair
Date:	Thu, 21 Apr 2011 13:11:46 -0500
Content-Type:	multipart/signed
Parts/Attachments:	text/plain (926 bytes) , reb.vcf (446 bytes) , smime.p7s (6 kB)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have noticed several times now that when sshd gets updated it
chkconfig's itself to start at boot.  I need sshd on my laptop for some
occasions when I run atlas tdaq software (which communicates via ssh),
but I do not care to have it on by default.  Whenever there is an update
of openssh-server the update does an "chkconfig --add sshd".  Should
this be reported as a bug to redhat?  I'm sure I'm not the only one who
finds this annoying and potentially insecure.
- --
Robert E. Blair, Room C221, Building 360
Argonne National Laboratory (High Energy Physics Division)
9700 South Cass Avenue, Argonne, IL 60439, USA
Phone: (630)-252-7545  FAX: (630)-252-5782
GnuPG Public Key: http://www.hep.anl.gov/reb/key.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFNsHNhOMIGC6x7/XQRAmxVAKDBqI24kYRKm3qC3IdVaX9SouVJGwCfWij+
DAtG71EdZy3XxEdJ9U8hBkE=
=uuhn
-----END PGP SIGNATURE-----

ATOM RSS1 RSS2

LISTSERV.FNAL.GOV