On Sun Mar 30, 2003 at 01:43:11PM -0800, James Sparenberg wrote: [...] > > All the way around, this xinetd business is not really good and I'm itching > > to rip it out. That being said, I've just built 3.6p1 packages and put the > > key generation stuff from the initscript into the %post section of the > > openssh-server package. > > Logical move on your part. This does guarantee that it gets run right. > The big surprise was that it was possible to run like this. That and the > fact that no one in cooker noticed it... self included. Honestly I did > think it could be done... guess I was wrong. *grin*.
Honestly, I doubt anyone used the xinetd system for sshd. It's just too bizarre and would have a negative impact on speed. And if they did, ie. for a quick testing, I doubt they did it "fresh", ie. using xinetd without ever having used the initscript. You only need to run the initscript once for it to work. Now, you don't have to do that either. Anyways, I hadn't noticed it before because a) I wasn't told about the change and b) I've been too busy to really participate in cooker to the extent I would like to these last few months. I actually didn't realize Thierry had done that until I was upgrading to 3.6p1 today. -- MandrakeSoft Security; http://www.mandrakesecure.net/ Online Security Resource Book; http://linsec.ca/ "lynx -source http://linsec.ca/vdanen.asc | gpg --import" {FE6F2AFD : 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD}
pgp00000.pgp
Description: PGP signature
