<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Firefox on BAFM</title><link>https://christian.blog.pakiheim.de/tags/firefox/</link><description>Recent content in Firefox on BAFM</description><generator>Hugo -- 0.160.1</generator><language>en</language><lastBuildDate>Tue, 12 Oct 2010 17:52:37 +0000</lastBuildDate><atom:link href="https://christian.blog.pakiheim.de/tags/firefox/index.xml" rel="self" type="application/rss+xml"/><item><title>Locking down Firefox</title><link>https://christian.blog.pakiheim.de/posts/2010-10-12_locking-down-firefox/</link><pubDate>Tue, 12 Oct 2010 17:52:37 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=3581</guid><description>&lt;p&gt;Once again, I had the task of locking down Firefox, so users couldn&amp;rsquo;t use it to do any harm on a terminal server. Thankfully there&amp;rsquo;s the guide over at the &lt;a href="http://www.engineering.uwaterloo.ca/twiki/bin/view/Linux/FirefoxLockdown"&gt;Faculty of Engineering of the University of Waterloo&lt;/a&gt; (by David Collie), who shows which parts to modify.&lt;/p&gt;
&lt;p&gt;However, finding the particular part in the Javascript is rather hindersome, so here a short Unix-Diff (for thos who&amp;rsquo;re able to read unified diffs) as well as the whole file.&lt;/p&gt;</description></item></channel></rss>