<?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: Transifex and SSH keys</title>
	<atom:link href="http://dimitris.glezos.com/weblog/2007/07/26/transifex-ssh-keys/feed" rel="self" type="application/rss+xml" />
	<link>http://dimitris.glezos.com/weblog/2007/07/26/transifex-ssh-keys</link>
	<description>A greek/geek weblog</description>
	<lastBuildDate>Mon, 01 Feb 2010 14:23:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: Δημήτρης Γλέζος</title>
		<link>http://dimitris.glezos.com/weblog/2007/07/26/transifex-ssh-keys/comment-page-1#comment-6505</link>
		<dc:creator>Δημήτρης Γλέζος</dc:creator>
		<pubDate>Thu, 26 Jul 2007 18:47:20 +0000</pubDate>
		<guid isPermaLink="false">http://dimitris.glezos.com/weblog/2007/07/26/transifex-ssh-keys/#comment-6505</guid>
		<description>&lt;p&gt;Right, besides imposing ACLs on the VCS side, module maintainers have the choice to do so on the transifex side with a regex. This way, only the relevant files (eg. &lt;code&gt;po/*.po&lt;/code&gt;, &lt;code&gt;po/Changelog&lt;/code&gt;, &lt;code&gt;po/LINGUAS&lt;/code&gt;) are presented to the translator.&lt;/p&gt;

&lt;p&gt;Of course, as you already mentioned, this is orthogonal to the SSH keys: it works just in the web system. But it certainly controls a lot what one can and cannot do in the standard procedures of the web system.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Right, besides imposing ACLs on the VCS side, module maintainers have the choice to do so on the transifex side with a regex. This way, only the relevant files (eg. <code>po/*.po</code>, <code>po/Changelog</code>, <code>po/LINGUAS</code>) are presented to the translator.</p>
<p>Of course, as you already mentioned, this is orthogonal to the <acronym title="Secure SHell (encrypted protocol replaces telnet and FTP)">SSH</acronym> keys: it works just in the web system. But it certainly controls a lot what one can and cannot do in the standard procedures of the web system.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Colin Walters</title>
		<link>http://dimitris.glezos.com/weblog/2007/07/26/transifex-ssh-keys/comment-page-1#comment-6473</link>
		<dc:creator>Colin Walters</dc:creator>
		<pubDate>Thu, 26 Jul 2007 02:47:32 +0000</pubDate>
		<guid isPermaLink="false">http://dimitris.glezos.com/weblog/2007/07/26/transifex-ssh-keys/#comment-6473</guid>
		<description>&lt;p&gt;Not sure if this was mentioned (or implemented) before but - somewhat orthogonal to your concerns about SSH keys, I would try to ensure that the system limits what can be committed; e.g. only changes to po/*.po.&lt;/p&gt;

&lt;p&gt;If you implement this as a separate process (the one with access to the ssh keys), it seems reasonably safe.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Not sure if this was mentioned (or implemented) before but &#8211; somewhat orthogonal to your concerns about <acronym title="Secure SHell (encrypted protocol replaces telnet and FTP)">SSH</acronym> keys, I would try to ensure that the system limits what can be committed; e.g. only changes to po/*.po.</p>
<p>If you implement this as a separate process (the one with access to the ssh keys), it seems reasonably safe.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.260 seconds -->

