<?xml version="1.0" encoding="ISO-8859-15"?>
<rss version="2.0"><channel>
<title>restricting SCP on per-user basis</title>
<link>http://sange.fi/~atehwa/cgi-bin/piki.cgi/</link>
<description>Recent changes in restricting SCP on per-user basis</description>
<item><title>restricting SCP on per-user basis</title>
<link>http://sange.fi/~atehwa/cgi-bin/piki.cgi/restricting%20SCP%20on%20per-user%20basis</link>
<guid>http://sange.fi/~atehwa/cgi-bin/piki.cgi/#1272382736</guid>
<description>&lt;p&gt;SSH server implementations are not known for &lt;del&gt;its&lt;/del&gt; 
&lt;ins&gt;their&lt;/ins&gt; flexibility in per-user configuration. However, they 
turn out to provide just enough infrastructure to make it possible to 
make "special" accounts that are &lt;del&gt;just&lt;/del&gt; &lt;ins&gt;only&lt;/ins&gt; used 
for a specific task. Here, I will concentrate on OpenSSH and 
restricting access to file transfer and only a particular type of file 
transfer. 

&lt;p&gt;First, the right place to tweak things is to use public key 
authentication and forced commands. So make a key pair for the account 
you want to give restricted access to, give the private key to the 
people who need to use the restricted &lt;del&gt;service,&lt;/del&gt; &lt;ins&gt;service 
(they need to invoke scp as scp -i path/to/private_key),&lt;/ins&gt; and drop 
the public key into the &lt;ins&gt;server&lt;/ins&gt; account's 
.ssh/authorized_keys. Then, add options to the beginning of the line so 
that the line reads something like &lt;ins&gt;this&lt;/ins&gt; (the line has been 
broken for readability but should be on one line without a backslash, 
newline or space character): 

&lt;p&gt;[...]

</description>
<pubDate>Tue, 27 Apr 2010 15:38:56 +0000</pubDate>
</item>

</channel></rss>
