<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:thr="http://purl.org/syndication/thread/1.0">
    <title>Comments for Input Managers and Leopard</title>
    <link rel="alternate" type="text/html" href="http://bradchoate.com/weblog/2008/03/01/input-managers-and-leopard" />
    <link rel="self" type="application/atom+xml" href="http://bradchoate.com/weblog/2008/03/01/input-managers-and-leopard" />
    <id>tag:bradchoate.com,2011://4-</id>
    <updated>2008-03-10T20:58:25Z</updated>
    <subtitle>The man, the legend.</subtitle>
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.2-en</generator>
 

<entry>
    <id>tag:bradchoate.com,2008://4.2683-comment:22756</id>
    <thr:in-reply-to ref="tag:bradchoate.com,2008://4.2683" href="http://bradchoate.com/weblog/2008/03/01/input-managers-and-leopard"/>
 
    <link rel="alternate" type="text/html" href="http://bradchoate.com/weblog/2008/03/01/input-managers-and-leopard#c22756" />
    <title>Comment from waffle.wootest.net on 2008-03-02</title>
    <author>
        <name>waffle.wootest.net</name>
        <uri>http://waffle.wootest.net/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://waffle.wootest.net/">
        <![CDATA[<p>The thing is that Apple doesn't want to address this. It wants all these hacks to go away on their own since the technology used for its original purpose has been superseded and everything else is just used to duct tape things onto other applications. (They may be *useful* hacks and I use a few myself, but they still inject code into every Cocoa app, which isn't all that good from a security and stability point of view, and practically nullifies any upside to signed apps since you still can't trust that code.)</p>

<p>Letting InputManagers live to see another day was clearly a small concession, and the draconian rules work as a deterrent. Putting it in /Library was probably one way of making sure you had administrator privileges to install it. They need to be owned by root and have certain permissions too, but you can set any file you own to those.</p>

<p>Apple isn't interested in fixing this or any other problem, because Apple doesn't want them to keep living. I'm not exactly jealous of them right now since they'll have to kill off a useful but insecure venue for extending apps.</p>

<p>/Jesper (since, apparently, my OpenID name is just my URL; hmm)</p>]]>
    </content>
    <published>2008-03-02T09:28:29Z</published>
</entry>

<entry>
    <id>tag:bradchoate.com,2008://4.2683-comment:33685</id>
    <thr:in-reply-to ref="tag:bradchoate.com,2008://4.2683" href="http://bradchoate.com/weblog/2008/03/01/input-managers-and-leopard"/>
 
    <link rel="alternate" type="text/html" href="http://bradchoate.com/weblog/2008/03/01/input-managers-and-leopard#c33685" />
    <title>Comment from Andrew on 2011-01-19</title>
    <author>
        <name>Andrew</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>I guarantee this will be gone by OS X 10.8, and thats only if they include it in Lion. Apple are dumb for thinking that forcing all input managers to have system wide acces constitutes as a 'fix'</p>

<p>Why do Apple think that asking for your password is anything more than a minor security step. Everything asks for a password these days, from accessing your mail, to moving folders on your account. People no longer equate password protection to potentially dangerous access, they just see it as an obstacle between you and what you were trying to do before it appeared.</p>]]>
    </content>
    <published>2011-01-19T18:53:04Z</published>
</entry>


</feed>
