<?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: 1Password is not for me: Doesn&#8217;t work with third-party applications</title>
	<atom:link href="http://www.contentious.com/2009/03/01/1password-is-not-for-me-doesnt-work-with-third-party-applications/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.contentious.com/2009/03/01/1password-is-not-for-me-doesnt-work-with-third-party-applications/</link>
	<description>Amy Gahran's news and musings on how we communicate in the online age.</description>
	<lastBuildDate>Thu, 09 Feb 2012 16:36:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Aaron</title>
		<link>http://www.contentious.com/2009/03/01/1password-is-not-for-me-doesnt-work-with-third-party-applications/comment-page-1/#comment-1231406</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Fri, 17 Sep 2010 21:21:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.contentious.com/?p=2382#comment-1231406</guid>
		<description>Sorry, Ms Gahran.  I referred to you incorrectly as &quot;he&quot; in my post.  My apologies. :)</description>
		<content:encoded><![CDATA[<p>Sorry, Ms Gahran.  I referred to you incorrectly as &#8220;he&#8221; in my post.  My apologies. <img src='http://www.contentious.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://www.contentious.com/2009/03/01/1password-is-not-for-me-doesnt-work-with-third-party-applications/comment-page-1/#comment-1231405</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Fri, 17 Sep 2010 21:20:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.contentious.com/?p=2382#comment-1231405</guid>
		<description>I disagree with the criticism of the author that he was basically &quot;saying 1P is not perfect, therefore it is no good.&quot;  Being able to efficiently paste a password into a 3rdParty app is not a stretch.  It is an oversight that the Cmd-C behavior only copies the record, and there is no shortcut to copy the password.  Browsers are only a part of the landscape when it comes to passwords.  1P handles browsers well.  Is there room for improvement, sure, but it does do a good job there.  That it can&#039;t do an average job supporting 3rdParty apps is a disappointment.  Like the author, 1P is not for me.</description>
		<content:encoded><![CDATA[<p>I disagree with the criticism of the author that he was basically &#8220;saying 1P is not perfect, therefore it is no good.&#8221;  Being able to efficiently paste a password into a 3rdParty app is not a stretch.  It is an oversight that the Cmd-C behavior only copies the record, and there is no shortcut to copy the password.  Browsers are only a part of the landscape when it comes to passwords.  1P handles browsers well.  Is there room for improvement, sure, but it does do a good job there.  That it can&#8217;t do an average job supporting 3rdParty apps is a disappointment.  Like the author, 1P is not for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BradH</title>
		<link>http://www.contentious.com/2009/03/01/1password-is-not-for-me-doesnt-work-with-third-party-applications/comment-page-1/#comment-1231353</link>
		<dc:creator>BradH</dc:creator>
		<pubDate>Sun, 12 Sep 2010 18:50:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.contentious.com/?p=2382#comment-1231353</guid>
		<description>Thanks for writing this article. It&#039;s helped me decide whether I should get 1password or not. I&#039;ve been searching for information about the differences between Keychain Access (i.e. the Mac OS X default) and 1Password, but it hasn&#039;t been easy to find neutral comparisons. For the benefit of anyone else who might be trying to compare 1Password and the Mac default, here&#039;s what I&#039;ve found:


Features that both the Mac default and 1Password have:

-Saves and Autofills passwords
-Encrypts your information
-Can be locked manually or automatically to secure your information
-Can store bank information/other important information


Advantages of 1Password:

-Autofills credit card information
-Allows for multiple &quot;Identities&quot; when filling out personal information
-Advertises that it integrates with more websites than the default (I haven&#039;t verified this)
-iPhone integration (only works internally with the 1Password app, though it does sync your 1Password passwords from your Mac)


Advantages of the Mac default:

-Non-browser application support (as mentioned in the article)
-Integration with MobileMe


Whether or not the $40-$70 spent on 1Password is worth it is based entirely on your preferences. Keep in mind that both utilities will perform adequately (when used properly) to protect your information from hackers and from identity theft if someone steals your Mac.</description>
		<content:encoded><![CDATA[<p>Thanks for writing this article. It&#8217;s helped me decide whether I should get 1password or not. I&#8217;ve been searching for information about the differences between Keychain Access (i.e. the Mac OS X default) and 1Password, but it hasn&#8217;t been easy to find neutral comparisons. For the benefit of anyone else who might be trying to compare 1Password and the Mac default, here&#8217;s what I&#8217;ve found:</p>
<p>Features that both the Mac default and 1Password have:</p>
<p>-Saves and Autofills passwords<br />
-Encrypts your information<br />
-Can be locked manually or automatically to secure your information<br />
-Can store bank information/other important information</p>
<p>Advantages of 1Password:</p>
<p>-Autofills credit card information<br />
-Allows for multiple &#8220;Identities&#8221; when filling out personal information<br />
-Advertises that it integrates with more websites than the default (I haven&#8217;t verified this)<br />
-iPhone integration (only works internally with the 1Password app, though it does sync your 1Password passwords from your Mac)</p>
<p>Advantages of the Mac default:</p>
<p>-Non-browser application support (as mentioned in the article)<br />
-Integration with MobileMe</p>
<p>Whether or not the $40-$70 spent on 1Password is worth it is based entirely on your preferences. Keep in mind that both utilities will perform adequately (when used properly) to protect your information from hackers and from identity theft if someone steals your Mac.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nunuv Yurbiz</title>
		<link>http://www.contentious.com/2009/03/01/1password-is-not-for-me-doesnt-work-with-third-party-applications/comment-page-1/#comment-1229490</link>
		<dc:creator>Nunuv Yurbiz</dc:creator>
		<pubDate>Wed, 11 Nov 2009 07:19:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.contentious.com/?p=2382#comment-1229490</guid>
		<description>Yeah, I&#039;m not sure the author&#039;s criticisms make any sense. Basically, the author is saying that 1P is not perfect, that it does not solve all problems (related to passwords), so therefore it&#039;s no good. That doesn&#039;t make sense to me. It&#039;s better than the built-in keychain, which has its own limitations. 

The question then becomes is it worth the price. I&#039;m currently using the 3.0 beta. 1P really needs to be able to better handle multi-page logins (ID on one page, password on the other). And those stupid questions that some sites make you answer if, say, you login from an unrecognized IP address. The questions are stupid because it&#039;s the same questions on just about every site! Arrrgh. Now everyone knows the name of my first pet, where I was born, the make of my first car, my favorite teacher (seriously?), etc., etc. Forget marketing questionnaires, which no one will answer, just require the info as part of &quot;security.&quot;</description>
		<content:encoded><![CDATA[<p>Yeah, I&#8217;m not sure the author&#8217;s criticisms make any sense. Basically, the author is saying that 1P is not perfect, that it does not solve all problems (related to passwords), so therefore it&#8217;s no good. That doesn&#8217;t make sense to me. It&#8217;s better than the built-in keychain, which has its own limitations. </p>
<p>The question then becomes is it worth the price. I&#8217;m currently using the 3.0 beta. 1P really needs to be able to better handle multi-page logins (ID on one page, password on the other). And those stupid questions that some sites make you answer if, say, you login from an unrecognized IP address. The questions are stupid because it&#8217;s the same questions on just about every site! Arrrgh. Now everyone knows the name of my first pet, where I was born, the make of my first car, my favorite teacher (seriously?), etc., etc. Forget marketing questionnaires, which no one will answer, just require the info as part of &#8220;security.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David A Teare</title>
		<link>http://www.contentious.com/2009/03/01/1password-is-not-for-me-doesnt-work-with-third-party-applications/comment-page-1/#comment-1226667</link>
		<dc:creator>David A Teare</dc:creator>
		<pubDate>Mon, 02 Mar 2009 16:36:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.contentious.com/?p=2382#comment-1226667</guid>
		<description>Thanks for the post! While I&#039;m not happy to hear 1Password did not meet your expectations, I&#039;m thankful you took the time to explain why so we can try to improve. 

Unfortunately, the main two items you identified are not something we can do much about as we are not allowed to. Let me explain.

First, the OS X Keychain is an OS X system service that all applications have access to. It would be very difficult for us to remove this service and replace it with our own. While I do see the usefulness of this approach, it would be incredibly fragile and likely break a lot more things then it fixes. Interestingly enough, we used to store our data in the OS X Keychain (using our own keychain separate from the login keychain), and it worked well, but we found for our purposes we needed to develop our own solution. This is not to say the OS X Keychain is bad, but rather it did not fit the needs of 1Password. For example, the OS X Keychain was designed to store 1 or 2 items per application, whereas 1Password needed to store thousands of items. Because our needs were so vastly different, we found many of the design choices made by the OS X Keychain team did not fit our needs so we designed our own. 

With that said, the OS X Keychain is still a secure place to store your account passwords (assuming your login password is strong) so you shouldn&#039;t fear using it. You can allow applications like Twhirl and Tweetdeck to store your generated password into the OS X Keychain, and also keep the password in 1Password as a Wallet item or Secure Note. The benefit here is if you ever reset your login keychain, or setup a brand new machine and don&#039;t want to migrate your old keychain, you will have access to the passwords.

As for the iPhone, there are a different set of limitations that we need to abide by. Sadly we are not allowed to extend the Mobile Safari application on iPhone; if we did we would be kicked out of the App Store for violating Apple&#039;s terms of service. If we could, we certainly would have added the 1P icon to Mobile Safari just like we do on Mac. 

Since we are not allowed to change Safari, what we do instead is to allow you to browse your sites inside the 1Password application itself. Simply find your Login, click on the URL, and we open up a browser (inside 1Password) to log you into the site. We actually use the same WebKit browser that Safari uses.

Anyway, I just wanted to shed some light on the issues you reported and why we elected to do things the way we did. 

Thank you for trying 1Password and I hope your friends who recommended 1Password to you help me change your mind :)

Cheers!

--Dave Teare
Co-author of 1Password</description>
		<content:encoded><![CDATA[<p>Thanks for the post! While I&#8217;m not happy to hear 1Password did not meet your expectations, I&#8217;m thankful you took the time to explain why so we can try to improve. </p>
<p>Unfortunately, the main two items you identified are not something we can do much about as we are not allowed to. Let me explain.</p>
<p>First, the OS X Keychain is an OS X system service that all applications have access to. It would be very difficult for us to remove this service and replace it with our own. While I do see the usefulness of this approach, it would be incredibly fragile and likely break a lot more things then it fixes. Interestingly enough, we used to store our data in the OS X Keychain (using our own keychain separate from the login keychain), and it worked well, but we found for our purposes we needed to develop our own solution. This is not to say the OS X Keychain is bad, but rather it did not fit the needs of 1Password. For example, the OS X Keychain was designed to store 1 or 2 items per application, whereas 1Password needed to store thousands of items. Because our needs were so vastly different, we found many of the design choices made by the OS X Keychain team did not fit our needs so we designed our own. </p>
<p>With that said, the OS X Keychain is still a secure place to store your account passwords (assuming your login password is strong) so you shouldn&#8217;t fear using it. You can allow applications like Twhirl and Tweetdeck to store your generated password into the OS X Keychain, and also keep the password in 1Password as a Wallet item or Secure Note. The benefit here is if you ever reset your login keychain, or setup a brand new machine and don&#8217;t want to migrate your old keychain, you will have access to the passwords.</p>
<p>As for the iPhone, there are a different set of limitations that we need to abide by. Sadly we are not allowed to extend the Mobile Safari application on iPhone; if we did we would be kicked out of the App Store for violating Apple&#8217;s terms of service. If we could, we certainly would have added the 1P icon to Mobile Safari just like we do on Mac. </p>
<p>Since we are not allowed to change Safari, what we do instead is to allow you to browse your sites inside the 1Password application itself. Simply find your Login, click on the URL, and we open up a browser (inside 1Password) to log you into the site. We actually use the same WebKit browser that Safari uses.</p>
<p>Anyway, I just wanted to shed some light on the issues you reported and why we elected to do things the way we did. </p>
<p>Thank you for trying 1Password and I hope your friends who recommended 1Password to you help me change your mind <img src='http://www.contentious.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Cheers!</p>
<p>&#8211;Dave Teare<br />
Co-author of 1Password</p>
]]></content:encoded>
	</item>
</channel>
</rss>

