- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- ssh needs to be restarted to enable the pam stack ...
Operating System - Linux
1820561
Members
1991
Online
109626
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-01-2009 03:22 AM
тАО07-01-2009 03:22 AM
The pam stack is (a)pam_radius.so(b)pam_unix.so
2. ssh to admin (user at radius server)
Result: Successful as expected.
3. The pam stack is (a) pam_ldap.so (b)pam_radius.so(c)pam_unix.so
4. Restart ssh
5. ssh to admin
Result: Successful as expected. Ldap server contacted
6.The pam stack is (a)pam_radius.so(b)pam_unix.so
7. ssh to admin
Result: Successful as expected. LDAP server contacted
8. Restart ssh( This is unexpected)
9. ssh admin LDAp server not contacted
Result: Successful as expected.
-----
Removing ladp module from pam stack at step # 6 traffic is at LDAP server on ssh to admin (user at radius server) at step # 7. And after restart ssh at #8 it is not the case as expected. My concern is unnecessary server traffic at LDAP server at step # 7.
Can anyone comment on this? Do we need to restart ssh on every step of removing and adding ldap module in pam stack?
Thanks,
MKS
2. ssh to admin (user at radius server)
Result: Successful as expected.
3. The pam stack is (a) pam_ldap.so (b)pam_radius.so(c)pam_unix.so
4. Restart ssh
5. ssh to admin
Result: Successful as expected. Ldap server contacted
6.The pam stack is (a)pam_radius.so(b)pam_unix.so
7. ssh to admin
Result: Successful as expected. LDAP server contacted
8. Restart ssh( This is unexpected)
9. ssh admin LDAp server not contacted
Result: Successful as expected.
-----
Removing ladp module from pam stack at step # 6 traffic is at LDAP server on ssh to admin (user at radius server) at step # 7. And after restart ssh at #8 it is not the case as expected. My concern is unnecessary server traffic at LDAP server at step # 7.
Can anyone comment on this? Do we need to restart ssh on every step of removing and adding ldap module in pam stack?
Thanks,
MKS
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-01-2009 03:54 AM
тАО07-01-2009 03:54 AM
Solution
Shalom,
No you do not need to restart ssh at every step.
I think you can safely do all the work on the pam stack and then restart ssh
SEP
No you do not need to restart ssh at every step.
I think you can safely do all the work on the pam stack and then restart ssh
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-01-2009 04:54 AM
тАО07-01-2009 04:54 AM
Re: ssh needs to be restarted to enable the pam stack changes
Thanks SEP!
For <>
I have concern why traffic is going on LDAP server even after removing ladp madoule from pam stack
Can you please let me know issue is at pam configuration side or ssh side? It does make sense to look from ssh perspective in this case?
Thanks ,
MKS
For <
I have concern why traffic is going on LDAP server even after removing ladp madoule from pam stack
Can you please let me know issue is at pam configuration side or ssh side? It does make sense to look from ssh perspective in this case?
Thanks ,
MKS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-01-2009 06:38 AM
тАО07-01-2009 06:38 AM
Re: ssh needs to be restarted to enable the pam stack changes
Shalom again,
For <>
Valid concern. If you start getting user login problems during the change steps, restart sshd daemon.
I have concern why traffic is going on LDAP server even after removing ladp madoule from pam stack
Issue as I see it:
As you make changes to the pam stack, your new user login process will be changing. Existing sessions should not be impacted unless you leave sshd down for a period of time.
So if you make a change to the pam stack that somehow disables new logins, users will suddenly not be able to log in.
pam stands for plugable authentication module, once you are authenticated it should not effect open sessions, changes here effect new authentications or logins.
Hope this helps.
SEP
For <
Valid concern. If you start getting user login problems during the change steps, restart sshd daemon.
I have concern why traffic is going on LDAP server even after removing ladp madoule from pam stack
Issue as I see it:
As you make changes to the pam stack, your new user login process will be changing. Existing sessions should not be impacted unless you leave sshd down for a period of time.
So if you make a change to the pam stack that somehow disables new logins, users will suddenly not be able to log in.
pam stands for plugable authentication module, once you are authenticated it should not effect open sessions, changes here effect new authentications or logins.
Hope this helps.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP