SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705
Rep:
sshd starting for no good reason?!
In my installation I allowed the config to set the ssh daemon to start. Later, I realized that this is not a good idea since I don't plan to use ssh at the moment.
From netstat I can see that ssh-agent is running, and when I issue a ps I can also see the process /usr/bin/ssh-agent -s running, and I have no idea how it gets started.
P.S. Yes, I restarted the system! And in the system log I can't see any indication that it's starting. Before I did the chmod I could see a line of output. But now no message is being produced.
The ssh is started by /etc/rc.inet2. If you want you could comment it out but since you change the x (excute flag)then it should not start. Another way would be to move the rc.ssh out of the rc.d directory into say /etc/rc.d/rc-tmp, this of course after you mkdir /etc/rc.d/rc-tmp.
My one question is why are fearing the ssh running? You password too simple? You keys are not there?
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705
Original Poster
Rep:
I'd like to understand how it gets started since it is not supposed to start. I don't like mysteries.
Why would I run a service if I don't plan to use it? That's just bad administration. And why would I have a door I don't plan to use? That's just bad security.
PS: You can always read the /etc/rc.d/* files to see what is going on - you would find that it only starts `sshd` as a background process and nothing to do with ssh-agent at all!
PPS: To get rid of it, remove the openssh package =)
PS: You can always read the /etc/rc.d/* files to see what is going on - you would find that it only starts `sshd` as a background process and nothing to do with ssh-agent at all!
PPS: To get rid of it, remove the openssh package =)
Piete does it again!
Beleive it or not, I did spend a long time looking over /etc/rc.d and I was just unable to spot the problem because I had just read a post about chmod +x, -x etc. to stop scripts from running and I didn't know what to look for. I'll have another try. But this looks like a good agent so I guess it should let it live in case I use gnupg. I'll have to research this a little- thanks very much for the lini.
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705
Original Poster
Rep:
Quote:
Originally Posted by uselpa
Are you using xfce?
Yes, it struck me as a good intermediate choice, so I didn't install KDE/KDEI/GNOME packages. I have it set up pretty much the way I want at the moment, although I can't get my touchpad to work. I read a ton of posts and tried many things but nothing worked.
Is there a connection between xfce and the ssh-agent?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.