Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
You have to add A to the trusted hosts on A just as you had to add B to trusted hosts. That is to say a host does not automatically "trust" itself - it has no way of knowing when you open the connection that it is originating internally. (Well it could if they wrote it to trace it but why would they bother when you can just add a trust relationship - it saves a lot of unnecessary coding.)
Remember also the trust is not just machine to machine but user to user. So if you try to ssh from user bob to user bill on host A it doesn't matter if you've given trust for root to root on host A.
I do NOT suggest doing it as root as those directions suggest however. Most (hopefully all) servers have ssh configured not to allow root to login through ssh. You can use the same directions, just where ever it says to generate the key as root, do it as your regular user.
It sounded from his original post that he already has generated the keys. He stated he is doing host B to A successfully and vice-versa. His issue is he trying to do A to A or B to B so as I said he probably just didn't realize he needs to setup a trust relationship within the host if it's doing ssh to itself.
Before you say he shouldn't I'll point out he's doing scripting. A good example of why one might do this is if they had Oracle EBusiness running on a host with an Oracle Database. The admin user for the Database is typically different than the Admin user for the Ebusiness but when shutting them down you want to shutdown first the Ebusiness then the Database. Allowing the DBAs to do trusts like this prevents System Admins (a/k/a the bane of DBA existence ) from having to give them root to switch users. This is exactly what this SA did to the DBAs at a prior job.
By shutting down I mean stopping the app and the database. Of course if it were the OS one could make an init script for the purpose and bypass all of this.
Last edited by MensaWater; 02-19-2007 at 10:46 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
) from having to give them root to switch users. This is exactly what this SA did to the DBAs at a prior job.
