<?xml version="1.0" encoding="UTF-8"?><rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
> <channel><title>Comments on: OpenSSH Root user account restriction &#8211; revisited</title> <atom:link href="http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html/feed" rel="self" type="application/rss+xml" /><link>http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html</link> <description>This is a Linux sys admin journal by Vivek about sys admin work, Linux tips &#38; tricks, hacks, news and more.</description> <lastBuildDate>Fri, 10 Feb 2012 20:37:43 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>By: Olivier</title><link>http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-178925</link> <dc:creator>Olivier</dc:creator> <pubDate>Tue, 24 Jan 2012 07:55:39 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-178925</guid> <description>It works for me, but is there any way to tune the denied access message when a user is not allowed to connect ?
Something like : “access denied for user joe from host xxx.xxx.xxx.xxx” for example instead of the brutal “Connection closed by xxx.xxx.xx.xx”
Thanks</description> <content:encoded><![CDATA[<p>It works for me, but is there any way to tune the denied access message when a user is not allowed to connect ?</p><p>Something like : “access denied for user joe from host xxx.xxx.xxx.xxx” for example instead of the brutal “Connection closed by xxx.xxx.xx.xx”</p><p>Thanks</p> ]]></content:encoded> </item> <item><title>By: olivier</title><link>http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-178399</link> <dc:creator>olivier</dc:creator> <pubDate>Wed, 11 Jan 2012 22:03:45 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-178399</guid> <description>This message is not really friendly for user when the don&#039;t access :
&quot;Connection closed by xxx.xxx.xx.xx&quot;
Is there any way to tune the denied access message ?
Something like : &quot;access denied for user joe from host xxx.xxx.xxx.xxx&quot; for example ?</description> <content:encoded><![CDATA[<p>This message is not really friendly for user when the don&#8217;t access :<br
/> &#8220;Connection closed by xxx.xxx.xx.xx&#8221;</p><p>Is there any way to tune the denied access message ?</p><p>Something like : &#8220;access denied for user joe from host xxx.xxx.xxx.xxx&#8221; for example ?</p> ]]></content:encoded> </item> <item><title>By: danny</title><link>http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-176286</link> <dc:creator>danny</dc:creator> <pubDate>Thu, 01 Dec 2011 22:51:55 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-176286</guid> <description>Thanks for the info!  Don&#039;t forget to add :
+ : root : localhost.locadomain cron crond LOCAL
Otherwise, your cronjons will not work.</description> <content:encoded><![CDATA[<p>Thanks for the info!  Don&#8217;t forget to add :</p><p>+ : root : localhost.locadomain cron crond LOCAL</p><p>Otherwise, your cronjons will not work.</p> ]]></content:encoded> </item> <item><title>By: Solaris</title><link>http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-155064</link> <dc:creator>Solaris</dc:creator> <pubDate>Fri, 16 Apr 2010 09:06:44 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-155064</guid> <description>You can use
AllowUsers vivek@10.10.10.12 root@10.10.10.12 user2
in /etc/ssh/sshd_config
to allow user2 from anywhere and vivek and root from only that ip
then
$ sudo /etc/init.d/ssh reload</description> <content:encoded><![CDATA[<p>You can use<br
/> AllowUsers <a
href="mailto:vivek@10.10.10.12">vivek@10.10.10.12</a> <a
href="mailto:root@10.10.10.12">root@10.10.10.12</a> user2</p><p>in /etc/ssh/sshd_config</p><p>to allow user2 from anywhere and vivek and root from only that ip</p><p>then<br
/> $ sudo /etc/init.d/ssh reload</p> ]]></content:encoded> </item> <item><title>By: Peter L</title><link>http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-152409</link> <dc:creator>Peter L</dc:creator> <pubDate>Mon, 21 Dec 2009 23:19:29 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-152409</guid> <description>I found that the order of entries in /etc/pam.d/sshd matters.  Line &quot;account required pam_access.so&quot; must be prepended, not appended to the end of the file.  It must appear before the other &quot;account&quot; lines.  Otherwise great guide - thanks dude!</description> <content:encoded><![CDATA[<p>I found that the order of entries in /etc/pam.d/sshd matters.  Line &#8220;account required pam_access.so&#8221; must be prepended, not appended to the end of the file.  It must appear before the other &#8220;account&#8221; lines.  Otherwise great guide &#8211; thanks dude!</p> ]]></content:encoded> </item> <item><title>By: Max</title><link>http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-149125</link> <dc:creator>Max</dc:creator> <pubDate>Wed, 24 Jun 2009 23:50:07 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-149125</guid> <description>How do you edit the access line to accept a group name with a space in it?:
-:ALL EXCEPT Domain Users :ALL seems to read the groups as Domain and Users. adding &quot;quotes&quot; didn&#039;t work either.</description> <content:encoded><![CDATA[<p>How do you edit the access line to accept a group name with a space in it?:<br
/> -:ALL EXCEPT Domain Users :ALL seems to read the groups as Domain and Users. adding &#8220;quotes&#8221; didn&#8217;t work either.</p> ]]></content:encoded> </item> <item><title>By: James</title><link>http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-148836</link> <dc:creator>James</dc:creator> <pubDate>Thu, 04 Jun 2009 20:52:30 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-148836</guid> <description>@Thorne
Actually, OpenSSH does support a multitude of Allow/Deny mechanisms, though I believe they are all ANDed together.  Thus, obtaining the behavior described in the intro to this page is not possible with OpenSSH alone.  Here are the Allow/Deny mechanisms supported by OpenSSH.
AllowGroups
AllowTcpForwarding
AllowUsers
DenyGroups
DenyUsers</description> <content:encoded><![CDATA[<p>@Thorne</p><p>Actually, OpenSSH does support a multitude of Allow/Deny mechanisms, though I believe they are all ANDed together.  Thus, obtaining the behavior described in the intro to this page is not possible with OpenSSH alone.  Here are the Allow/Deny mechanisms supported by OpenSSH.</p><p> AllowGroups<br
/> AllowTcpForwarding<br
/> AllowUsers<br
/> DenyGroups<br
/> DenyUsers</p> ]]></content:encoded> </item> <item><title>By: Khandakar Ashfaqur Rahman</title><link>http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-147749</link> <dc:creator>Khandakar Ashfaqur Rahman</dc:creator> <pubDate>Thu, 19 Mar 2009 05:59:01 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-147749</guid> <description>Good Solution.
Regards,
Rigan</description> <content:encoded><![CDATA[<p>Good Solution.</p><p>Regards,<br
/> Rigan</p> ]]></content:encoded> </item> <item><title>By: Thorne Lawler</title><link>http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-146683</link> <dc:creator>Thorne Lawler</dc:creator> <pubDate>Wed, 14 Jan 2009 02:52:40 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-146683</guid> <description>How should this (fairly obvious, common) restriction be implemented on systems which do not use PAM?
I&#039;m quite disappointed with the OpenSSH dev team for this: A multitude of other Allow/Deny mechanisms have supported this kind of behaviour for longer than I&#039;ve been alive. Why the great leap backwards?</description> <content:encoded><![CDATA[<p>How should this (fairly obvious, common) restriction be implemented on systems which do not use PAM?</p><p>I&#8217;m quite disappointed with the OpenSSH dev team for this: A multitude of other Allow/Deny mechanisms have supported this kind of behaviour for longer than I&#8217;ve been alive. Why the great leap backwards?</p> ]]></content:encoded> </item> <item><title>By: Matthew Feinberg</title><link>http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-12411</link> <dc:creator>Matthew Feinberg</dc:creator> <pubDate>Tue, 03 Oct 2006 18:26:12 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-12411</guid> <description>That&#039;s because pam_access scans access.conf for the first entry that matches the (user, host) combination.  Your line does not match any address except 10.10.10.12, so you have denied all users except root from logging in from 10.10.10.12.  The line does not effect connections from any other host.</description> <content:encoded><![CDATA[<p>That&#8217;s because pam_access scans access.conf for the first entry that matches the (user, host) combination.  Your line does not match any address except 10.10.10.12, so you have denied all users except root from logging in from 10.10.10.12.  The line does not effect connections from any other host.</p> ]]></content:encoded> </item> <item><title>By: nixcraft</title><link>http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-6040</link> <dc:creator>nixcraft</dc:creator> <pubDate>Wed, 30 Aug 2006 14:31:47 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-6040</guid> <description>The file name changes from one Linux distro to another. So it may be ssh or sshd.</description> <content:encoded><![CDATA[<p>The file name changes from one Linux distro to another. So it may be ssh or sshd.</p> ]]></content:encoded> </item> <item><title>By: jeremiah</title><link>http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-6037</link> <dc:creator>jeremiah</dc:creator> <pubDate>Wed, 30 Aug 2006 14:03:31 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-6037</guid> <description>You have to modify /etc/pam.d/ssh not /etc/pam.d/sshd</description> <content:encoded><![CDATA[<p>You have to modify /etc/pam.d/ssh not /etc/pam.d/sshd</p> ]]></content:encoded> </item> <item><title>By: jeremiah</title><link>http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-6036</link> <dc:creator>jeremiah</dc:creator> <pubDate>Wed, 30 Aug 2006 14:02:30 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-6036</guid> <description>You state that one should edit /etc/pam.d/sshd to enable the access.conf file. But this is not really what you should advise. What you should say is that one has to edit /etc/pam.d/ssh and add a line forcing usage of /etc/security/access.conf. If one just hacks on /etc/pam.d/sshd then anyone can still login since you have not configured PAM access.conf!</description> <content:encoded><![CDATA[<p>You state that one should edit /etc/pam.d/sshd to enable the access.conf file. But this is not really what you should advise. What you should say is that one has to edit /etc/pam.d/ssh and add a line forcing usage of /etc/security/access.conf. If one just hacks on /etc/pam.d/sshd then anyone can still login since you have not configured PAM access.conf!</p> ]]></content:encoded> </item> <item><title>By: Planet Malaysia Blog &#187; Blog Archive &#187; SSH Root Access Login Control</title><link>http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-4022</link> <dc:creator>Planet Malaysia Blog &#187; Blog Archive &#187; SSH Root Access Login Control</dc:creator> <pubDate>Thu, 03 Aug 2006 05:08:09 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-4022</guid> <description>[...] After read &#8220;OpenSSH Root user account restriction &#8211; revisited&#8221; article, I did a test on my testing server. [...]</description> <content:encoded><![CDATA[<p>[...] After read &#8220;OpenSSH Root user account restriction &#8211; revisited&#8221; article, I did a test on my testing server. [...]</p> ]]></content:encoded> </item> <item><title>By: Planet Malaysia</title><link>http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-4021</link> <dc:creator>Planet Malaysia</dc:creator> <pubDate>Thu, 03 Aug 2006 04:53:34 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-4021</guid> <description>I found a solution:
vi /etc/security/access.conf and added this 2 lines
- : root : ALL
+ : root : 10.10.10.52.
and save.</description> <content:encoded><![CDATA[<p>I found a solution:<br
/> vi /etc/security/access.conf and added this 2 lines<br
/> - : root : ALL<br
/> + : root : 10.10.10.52.<br
/> and save.</p> ]]></content:encoded> </item> <item><title>By: Planet Malaysia</title><link>http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-4020</link> <dc:creator>Planet Malaysia</dc:creator> <pubDate>Thu, 03 Aug 2006 03:56:13 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/openssh-root-user-account-restriction-revisited.html#comment-4020</guid> <description>Weird! I added &quot;account required pam_access.so&quot; into  &quot;/etc/pam.d/sshd&quot; and modify &quot;/etc/security/access.conf&quot; to
&quot;-:ALL EXCEPT root:10.10.10.12&quot; but I still managed ssh login from other IP Address(e.g: 10.10.10.2, 10.10.10.3)</description> <content:encoded><![CDATA[<p>Weird! I added &#8220;account required pam_access.so&#8221; into  &#8220;/etc/pam.d/sshd&#8221; and modify &#8220;/etc/security/access.conf&#8221; to<br
/> &#8220;-:ALL EXCEPT root:10.10.10.12&#8243; but I still managed ssh login from other IP Address(e.g: 10.10.10.2, 10.10.10.3)</p> ]]></content:encoded> </item> </channel> </rss>
