<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Linux Noob &#187; root</title>
	<atom:link href="http://thelinuxnoob.com/tag/root/feed/" rel="self" type="application/rss+xml" />
	<link>http://thelinuxnoob.com</link>
	<description>Fixin' issues one ticket at a time!</description>
	<lastBuildDate>Wed, 28 Jul 2010 16:51:23 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>pty, ptyp, and tty errors</title>
		<link>http://thelinuxnoob.com/linux/pty-ptyp-and-tty-errors/</link>
		<comments>http://thelinuxnoob.com/linux/pty-ptyp-and-tty-errors/#comments</comments>
		<pubDate>Mon, 02 Nov 2009 16:49:31 +0000</pubDate>
		<dc:creator>Clayton</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[SSH]]></category>
		<category><![CDATA[Tutorial]]></category>
		<category><![CDATA[root]]></category>
		<category><![CDATA[vps]]></category>

		<guid isPermaLink="false">http://thelinuxnoob.com/?p=25</guid>
		<description><![CDATA[So I came across this error for the first time today when trying to SSH directly into a clients VPS. login as: root root@server&#8217;s password: Server refused to allocate pty stdin: is not a tty After a quick google search I came across the fix. [root@node /]# vzlist -a VEID      NPROC STATUS  IP_ADDR         HOSTNAME 1337]]></description>
			<content:encoded><![CDATA[<p>So I came across this error for the first time today when trying to SSH directly into a clients VPS.</p>
<blockquote><p>login as: root<br />
root@server&#8217;s password:<br />
Server refused to allocate pty<br />
stdin: is not a tty</p></blockquote>
<p>After a quick google search I came across the fix.</p>
<blockquote><p>[root@node /]# vzlist -a<br />
VEID      NPROC STATUS  IP_ADDR         HOSTNAME<br />
1337         78 running 69.10.59.80     grumpy.thelinuxnoob.com<br />
[root@node /]# vzctl exec 1337 /sbin/MAKEDEV ptyp<br />
[root@node /]# vzctl exec 1337 /sbin/MAKEDEV tty<br />
[root@node /]# vzctl exec 1337 /sbin/MAKEDEV pty</p></blockquote>
<p>The issue should now be resolved and you can SSH into the VPS.</p>
]]></content:encoded>
			<wfw:commentRss>http://thelinuxnoob.com/linux/pty-ptyp-and-tty-errors/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Disable root SSH access</title>
		<link>http://thelinuxnoob.com/linux/disable-root-ssh-access/</link>
		<comments>http://thelinuxnoob.com/linux/disable-root-ssh-access/#comments</comments>
		<pubDate>Wed, 21 Oct 2009 02:38:05 +0000</pubDate>
		<dc:creator>Clayton</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[SSH]]></category>
		<category><![CDATA[Tutorial]]></category>
		<category><![CDATA[root]]></category>
		<category><![CDATA[su]]></category>

		<guid isPermaLink="false">http://69.10.59.80/~thelinux/?p=16</guid>
		<description><![CDATA[Allowing the root user to login directly is a major security issue, we’ll show you how to disable it so you can still login as root but just not directly, reducing the security issue. This will force a hacker to have to guess 2 seperate passwords to gain root access. (you do have 2 seperate]]></description>
			<content:encoded><![CDATA[<p>Allowing the root user to login directly is a major security issue, we’ll show you how to disable it so you can still login as root but just not directly, reducing the security issue.</p>
<p>This will force a hacker to have to guess 2 seperate passwords to gain root access.<br />
(you do have 2 seperate passwords for admin and root right?)<br />
What happens is you’ll first need to login as your <em>admin </em>user in <abbr title="Secure Shell">SSH</abbr>, then switch to the super user with the <em>su</em> command to get root.</p>
<p>We also will be forcing the use of <abbr title="Secure Shell">SSH</abbr> protocol 2, which is a newer, more secure <abbr title="Secure Shell">SSH</abbr> protocol<br />
Just a couple more ways to help your server stay safe from the bad guys. If you’re using cPanel make sure you add your admin user to the ‘<em>wheel</em>‘ group so that you will be able to ‘<em>su -</em>‘ to root, otherwise you may lock yourself out of root.</p>
<blockquote><p><strong>1.</strong> <abbr title="Secure Shell">SSH</abbr> into your server as ‘<em>admin</em>‘ and gain root access by <em>su</em></p>
<p><strong>2.</strong> Copy and paste this line to edit the file for <abbr title="Secure Shell">SSH</abbr> logins<br />
<em>pico -w /etc/<abbr title="Secure Shell">ssh</abbr>/sshd_config</em></p>
<p><em></em><strong>3.</strong> Find the line<br />
<em>Protocol 2, 1</em></p>
<p><strong>4.</strong> Uncomment it and change it to look like<br />
<em>Protocol 2</em></p>
<p><em></em><strong>5.</strong> Next, find the line<br />
<em>PermitRootLogin yes</em></p>
<p><em></em><strong>6.</strong> Uncomment it and make it look like <em>PermitRootLogin no</em></p>
<p><em></em><strong>7.</strong> Save the file <em>Ctrl+X</em> then <em>Y</em> then <em>enter</em></p>
<p><strong>8.</strong> Now you can restart <abbr title="Secure Shell">SSH</abbr><br />
<em>/etc/rc.d/init.d/sshd restart</em></p></blockquote>
<p><em></em>Now, no one will be able to login to root with out first loggin in as admin and ’su -’ to root, and you will be forcing the use of a more secure protocol. Just make sure you remember both passwords!</p>
]]></content:encoded>
			<wfw:commentRss>http://thelinuxnoob.com/linux/disable-root-ssh-access/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
