<?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"
	>
<channel>
	<title>Comments on: On the Safari shell script exploit</title>
	<atom:link href="http://boredzo.org/blog/archives/2006-02-22/on-the-safari-shell-script-exploit/feed" rel="self" type="application/rss+xml" />
	<link>http://boredzo.org/blog/archives/2006-02-22/on-the-safari-shell-script-exploit</link>
	<description>The personal weblog of Peter Hosey.</description>
	<pubDate>Fri, 29 Aug 2008 05:18:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Mac-arena the Bored Zo</title>
		<link>http://boredzo.org/blog/archives/2006-02-22/on-the-safari-shell-script-exploit#comment-19</link>
		<dc:creator>Mac-arena the Bored Zo</dc:creator>
		<pubDate>Fri, 24 Feb 2006 21:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://boredzo.org/blog/archives/2006-02-22/on-the-safari-shell-script-exploit#comment-19</guid>
		<description>the size of the badge I'm imagining is one-quarter the size of the document icon.

maybe cap it to 16- or 24-pt (either centered within the quadrant, or fixed at the corner), simply because huge badges seem self-contradictory somehow.</description>
		<content:encoded><![CDATA[<p>the size of the badge I'm imagining is one-quarter the size of the document icon.</p>
<p>maybe cap it to 16- or 24-pt (either centered within the quadrant, or fixed at the corner), simply because huge badges seem self-contradictory somehow.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://boredzo.org/blog/archives/2006-02-22/on-the-safari-shell-script-exploit#comment-18</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Fri, 24 Feb 2006 06:32:00 +0000</pubDate>
		<guid isPermaLink="false">http://boredzo.org/blog/archives/2006-02-22/on-the-safari-shell-script-exploit#comment-18</guid>
		<description>Number 1 is similar to the idea I had to get around - although yours would be less obtrusive, since it would only apply to certain executables.

I thought badging all files that are executables would be the way to go, similar to how aliases are badged now.

The 'flaw' in your idea, would be that app icons are designed to be bigger than just a badge. A terminal icon at the size of a badge would just look like an ugly black dot.

Ryan's idea of having a confirmation dialog when running items in the terminal is a good idea. Standard users aren't going to be using the terminal much, and as long as there is a preference to turn it 'off' for people who use the terminal more, it's all good :)</description>
		<content:encoded><![CDATA[<p>Number 1 is similar to the idea I had to get around - although yours would be less obtrusive, since it would only apply to certain executables.</p>
<p>I thought badging all files that are executables would be the way to go, similar to how aliases are badged now.</p>
<p>The 'flaw' in your idea, would be that app icons are designed to be bigger than just a badge. A terminal icon at the size of a badge would just look like an ugly black dot.</p>
<p>Ryan's idea of having a confirmation dialog when running items in the terminal is a good idea. Standard users aren't going to be using the terminal much, and as long as there is a preference to turn it 'off' for people who use the terminal more, it's all good :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Littlefield</title>
		<link>http://boredzo.org/blog/archives/2006-02-22/on-the-safari-shell-script-exploit#comment-17</link>
		<dc:creator>Ryan Littlefield</dc:creator>
		<pubDate>Wed, 22 Feb 2006 12:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://boredzo.org/blog/archives/2006-02-22/on-the-safari-shell-script-exploit#comment-17</guid>
		<description>It would make a lot of sense to do badging. Because the primary interface for both opening files and launching executables (and in the case of a script, both) is through double clicking an icon/name, information about which action you are taking should be given.

In my opinion, a sensible default would be to have all applications sport a pencil-paintbrush-ruler badge until after the initial launch. All files should be badged with whatever opens them, but scripts should have some special indicator.

Terminal or Finder would also do well to default to giving an additional dialog along the lines of "Hey, are you sure you want to run this?". Maybe that gets in the way, but if you wanted a fast way to running your scripts you'd be on the command line already, where there is a clear distinction between executing something and opening it.</description>
		<content:encoded><![CDATA[<p>It would make a lot of sense to do badging. Because the primary interface for both opening files and launching executables (and in the case of a script, both) is through double clicking an icon/name, information about which action you are taking should be given.</p>
<p>In my opinion, a sensible default would be to have all applications sport a pencil-paintbrush-ruler badge until after the initial launch. All files should be badged with whatever opens them, but scripts should have some special indicator.</p>
<p>Terminal or Finder would also do well to default to giving an additional dialog along the lines of "Hey, are you sure you want to run this?". Maybe that gets in the way, but if you wanted a fast way to running your scripts you'd be on the command line already, where there is a clear distinction between executing something and opening it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

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