1Password 4 for Mac is here(blog.agilebits.com) |
1Password 4 for Mac is here(blog.agilebits.com) |
I'm doubting that I'll actually do this because I'm so steamed about the disabling of perfectly working features.
http://blog.agilebits.com/2013/08/08/1password-3-dropbox-syn...
They claim that Dropbox deprecated their existing API, so the software broke on it's own. AgileBits did not disable the integration, upsteam changed.
In the same way that Netscape 4 can't talk to SPDY-only websites, 1Password 3 can't talk to the new dropbox API.
I haven't found the doc from Dropbox that describes an API change on Sept 1 - They did do a V0-V1 change this year, however, and AgileBits' story is plausible.
The new feature in 1Password 4 for Mac that has me interested is shared vaults. Now you can finally use 1Password as a password sharing solution for a business. This has been on my wishlist for years.
http://learn.agilebits.com/1Password4/Security/keychain-desi...
Not every version. We've only charged for three upgrades in our history.
1Password 2 for Mac to 1Password 3 for Mac
1Password 3 for Mac to 1Password 4 for Mac
1Password 3 for iOS to 1Password 4 for iOS
So, two of the three updates happened in the last year for the latest release (1Password 4). All other updates were free for existing users.
That's over 4 years between releases with no charges for users who purchased on launch day. Now, not every user purchased on launch day obviously, but I think we've been pretty fair with the upgrades. We go out of our way to try to help users who purchased prior to the new version too. We gave every user who purchased 1Password 3 for iOS a free upgrade to 1Password 4 within a 30 day window from 1Password 4 release.
This is the App Store we're talking about, which doesn't provide a mechanism for giving the app away free (while having it a paid app). Unless you count those 50 app store promo codes you get each release... (that's cost of app + 30% hit from Apple). I don't know of any other company that would do that on the scale we did. We tried VERY hard to give our users the best we could while going to a new app.
Kyle
AgileBits Support
1Password 4 is a big leap for me in terms of usability (vs. v.3): the mini application can be quickly accessed via a key chord, similarly to what you can do within a browser. Very helpful for things like VPN access, encrypted HDs, and other non-web softwares.
The security audit is a great feature too: it can tell you where you are using weak passwords, or even repeated passwords. If you have used the same password on many sites, and one of those sites is compromised, you might want to change that password elsewhere, or better, make sure you use a unique strong password everywhere; so knowing what sites could be compromised is a huge help.
If you want to feel safe in the web, 1Password's high usability and new features will help you get there.
In my browsers, 1Password 4 still works less reliably than 1Password 3. Manual completion (I don't use auto competition) sometimes works and sometimes doesn't. In the former case, the user credentials get listed but not inserted. The issues occurs more often in Chrome than in Firefox. It might be just me of course.
In any case, I am already in contact with the great AgileBits support team. AgileBits is one of the companies where your support mails are taken seriously.
Kyle
AgileBits Support
I also use it to store secure account information like bank accounts and CC numbers. Ever needed your credit card or some account number but only had your phone on you? With services like 1Password that's no problem.
The auto-fill functionality seems greatly improved: there are many JS based lightbox or hidden-until-you-click logins that 1pass3 couldnt autofill. 1pass4 just works.
It's also a bit disappointing that I had to buy direct to get cross-platform support, which is the reason I chose 1Password, but then that means I have to pay for this upgrade. If I had paid them half the price via the Mac App Store, minus Apple's 30% no less, I would get the upgrade for free. Not sure what they are trying to tell me there.
Sorry to hear you feel it isn't worth the upgrade. I'd suggest trying the demo at least to see if there's anything there worth using. Personally, the new browser extension is amazing and I have a hard time going back to help users in support :)
You didn't have to buy direct to get cross platform support. We offer coupons to users who purchase on the Mac App Store and want to buy our Windows application as well. We match the price at the time of purchase. So, normally the Mac app is $50, we offer the Mac + Win bundle for $70. If you bought at $50 on the Mac App Store, we give a coupon to get the Windows app for the same price as our website bundle. We just need proof of purchase from the Mac App Store.
If you have concerns though, email us, support at company url. Mention me here and someone will add me to the ticket and we can discuss directly. I'll be happy to help however I can.
Kyle
AgileBits Support
My only suggestion is that you might want to document this somewhere, because I had no idea this was an option at the time I purchased in July 2012, and still don't see it on the store web pages.
Btw, my upgrade was free at the App Store.
Quick observations;
* Snappy and Fast.
* iCloud Sync will make it easier to sync between Devices - iOS and Mac OS X. Dropbox sync wasn't that great if I don't open the app often. (I hope I don't regret saying this.)
* Finally, "CMD + SHIFT + c" copies password to clipboard. Been asking that for ages.
* Security Audit is cool.
Hmmmmm;
* I wish I could choose the backup location.
* Allow me to create custom categories.
Overall, nice upgrade.
On my Non-American keyboard, CMD + \ equals CMD + Alt + Shift + / …
I have never used the setting so far. The current setting in 1Password on the Mac I am using right now is CMD + S, that does not work of course. I guess I changed it years ago since AgileBits is very unlikely to have chosen CMD + S as shortcut for Non-American keyboards. I changed the shortcut now to CMD + ALT + 7 …
Yes, there's a dedicated key for backslash on US keyboards: https://en.wikipedia.org/wiki/QWERTY#United_States
We had trouble with 1Password 3 and non-US keyboards, but the new app should be MUCH better at handling non-US keyboard layouts. So change that shortcut however you see fit :)
I just can't promise a t-shirt for your chosen replacement of the shortcut (see our blog.agilebits.com header for this one).
Kyle
AgileBits Support
It's one of the reasons I can get my parents to use 1P at all.
I've spent less money on other apps that I actually spend more time using daily. Guess I'll start searching for some alternatives before they start dropping support for v3.
— All website customers who purchased 1Password for Mac in 2013 get v4 for free. Yes, that’s a nine-month free upgrade window
— Launch sale price for new customers: $39.99 – that’s 20% off the regular price of $49.99
— Launch upgrade sale price for website customers who bought before 2013: $24.99 – that’s $10 off our regular upgrade price of $34.99".
It's available as an early beta and pretty promising. Competition is always good and Apple will pushing AgileBits further when they release Mavericks with the iCloud Keychain.
Still waiting for seamless Linux integration though. It's one of my killer apps that keeps me on OS X, connecting via ssh to headless Linux machines or VMs, as opposed to using the Linux desktop. And yes, I realize that there are other password managers out there for Linux. The point is that I already have my passwords and many notes in 1Password, and anything I switch to would have to sync with OS X and iOS.
Noted. We can't promise Linux support. It's hard to provide paid software on Linux and be able to pay for the development and technical support. The user base is tricky, many are used to free software via their favorite package manager. Serious professionals are likely to pay I think, but how many of those are there?
We'd love to support Linux in some way, and we just hired a guy who primarily works in Linux. We never say never, but we certainly can't promise Linux support. All that said, I'll pass your feedback along :)
I'd agree, I want our Windows application to get a make over and try to gain feature parity with our Mac app. We're a very small team though so focus tends to be on Mac and iOS since that's where a vast majority of our user base is. That's not to say we don't want the other platforms to be better. Example: We're working on a brand new Android application that should blend both our look and feel with Android's look and feel.
We'll get the Windows application there, just give it some time. :)
Kyle
AgileBits Support
Personally, I just use a variant of:
one-way-hash(master-password + site-domain)
Seems to work really well, doesn't require special software, allows me to replicate all my passwords on any computer, and passwords are unique to each website and seemingly-random. Use a strong master password and it seems like an ideal solution to me and you only have to remember one master password and use no special software.* For extra security, perhaps base85-encode the output and truncate it if you want a password with special characters in, and use a slower function (e.g. bcrypt with a high work factor?) to prevent brute force attacks if you're using a simple password.
[* Note, SuperGenPass basically does just this, but has security issues since it runs as JavaScript in the browser as a bookmarklet. My personal solution is a script which does something similar, run using a quick hot-key, that grabs the domain from my front-most web browser window and grabs my master password from the system keychain and then puts the generated password on my clipboard.]
Would be very grateful if someone could point out any security flaws in this method that haven't occurred to me!
Are there any good alternatives to 1Password? I need OSX, Windows, and Android versions, and it needs to work in Chrome and Safari. I'd also need synchronization between multiple machines/browsers. I'm not sure what I think of a web version like LastPass - my 1Password keychain is in my dropbox, so it's not like I have it locked-away and protected. But it still feels a bit odd to have my passwords in a single service like LastPass - for some reason I have more confidence in Dropbox's security than LastPass's.
All this "iCloud Keychain" hype looks like just a sync functionality on top of current implementation.
iCloud Keychain is a better experience on iOS because only Apple can extend Safari - If you're using 1Password on iOS, you can't do the equivalent of "CMD+\" - you have to use the launch the 1P app - which breaks the workflow.
I don't see me moving away from 1Password anytime soon - though the ability to have multiple agile keychains in a single 1P session would have me pulling out my wallet - been waiting for that for awhile.
I've already added "perform 1Password security audit" to my monthly to-do list.
Early adopters of 1Password 3 must wait a few more days in order to purchase a v4 upgrade from the web store.
Yes, I know appstore doesn't support paid upgrades, but at least they could have made it a little cheaper for us.
I guess I'll go dig it out of Time Machine ....
Sync- it's possible with Keychain Access + Dropbox, but not seamless
Easy password generation- no switching to Keychain Access, copying, etc.
iOS access- up until iCloud sync, passwords were not easily transferred to devices
Support for Windows browsers
Form filling- Keychain will do addresses, but not credit cards
On the other hand, the new keychain access will have direct Mobile Safari integration.
It will also allow you to share passwords (via Dropbox) between Macs and Windows machines. It can generate strong passwords as well.
I will probably switch soon given the current state of their Android app, but maybe this OSX update is a hint at a visual refresh for all of their products?
For a price you can use it on mobile, too.
It seems like the most secure way to use it, assuming you've enabled back ups in 1Password to iCloud or DropBox.
Whenever I need a password I just grab my phone and look it up, then type it in. Sure, I have to manually type passwords, and my randomized passwords all have a minimum 18 character length, so it takes a bit longer. It's a plus though, because over time I memorize my passwords through repetition. If you have the program on a desktop and it just copies/pastes your password, you'll never memorize it.
For me, not-memorizing it is the whole point of 1Password. 1Password lets me generate and store passwords which are MUCH longer/more random than normal people can memorize.
I store them on my PC, and lock/unlock them with a strong master password - They're synced via local network to my phone, and never travel outside my network. Where possible, accounts are additionally secured via 2-factor auth.
This seems like a much better solution than variations on song-lyrics, cat names, 'P4zzw0Rd', which is the 'standard' solution to passwords.
FWIW, passwords are something I'd consider a 'hair on fire' problem. The current solutions are very very broken.
Passwords are terrible. 1Password and related software make having to live with them significantly less terrible.
But when I go to the Mac App Store it says $39.99. What gives?
One password flaw: some sites have weird restrictions (probably your bank, for instance). A hashing solution is unlikely to meet those requirements, meaning you have to store the value securely somewhere, so why not store them all? On the other hand, if the output can meet the requirements, it's probably partly based on the requirements. If the requirements ever change, your password now doesn't match.
I know I've thought of others previously, but the short version of it all is that at some point you'll probably have to have secure storage for something that doesn't work with the hashing system you have. Once you have that secure storage, why not just use it instead, since it can resolve nearly all of the problems?
The "one password flaw" has never been an issue, but my bank uses proper two-factor authentication with a physical card-reading device, so maybe that's why... I've never actually encountered a website that places problematic restrictions on passwords except (weirdly) Microsoft.
But they're just personal anecdotes that those flaws haven't been an issue for me, but I agree they exist and could be show-stoppers for others. I certainly wouldn't recommend it to anyone non-tech-literate. If I did need secure storage outside of that system (which, you're right, does happen–mostly for wifi passwords and the like) then I just use the system keychain as intended.
But I do still have concerns about the overall security of the system simply because I don't understand it well enough...
> Once you have that secure storage, why not just use it instead, since it can resolve nearly all of the problems?
Because I don't want to pay for 1Password licenses, or be caught out if I'm using someone else's computer, or if all my backups catastrophically fail :)
Seriously, use cryptographically random passwords.
I appreciate the input and advice anyway. Security being a system of compromises, my current stance is that the security offered by a system like this, despite its flaws, is greater than a password database system (with truly random passwords) because then both I need to keep the database physically secure and trust that e.g. 1Password have designed it properly (or that my cloud provider is capable of keeping it secure). Since 1Password has apparently had potential issues in the past I don't have too much faith, but perhaps I'm being overly cynical.
Comments like yours and Groxx's help me re-evalute what I'm doing though, so maybe I will switch to proper random passwords in future. So thanks again for the input!
http://blog.agilebits.com/2012/11/08/dont-trust-a-password-m...
I suspect you'll find that at least somewhat useful :)
Kyle
AgileBits Support
But it's not just me using a system like this. Everyone using SuperGenPass is using something similar too. That's why I think it's important to talk about it more.
However, I can share some inspiration to get started:
SuperGenPass (the original place I saw the idea): http://supergenpass.com
A fork of SuperGenPass using bcrypt/base85: https://github.com/cmcnulty/SuperGenPass
I wouldn't use either of the above because they're JavaScript-based, but someone has implemented it in Python: https://github.com/gfxmonk/supergenpass
I took that script as inspiration, modified it to use bcrypt, and then used the Python "keyring" module for access to the OS X keychain, and calling "osascript" to use an AppleScript one-liner to get Safari's front-most URL as an input.
It does potentially have the side-benefit of protecting against phishing attacks too, since if the domain is different, the password is different, so you can't be fooled into giving your password to the wrong website.
I have yet to find any alternative that is even remotely as user-friendly. LastPass does legitimately seem to be well run and secure, but the browser-extension UI is horrible at omg levels. KeePass(X/etc) also looks decent, but it's .NET (for what appear to be good reasons, but still), has slightly scary code (lots of reimplementing builtin classes), and again, omg-horrible UI.
I'd love a reasonable alternative, 1Password is unfortunately getting too pricy as time goes on, though it has been hands-down the best.
Kyle
AgileBits Support
I'll put this on my todo list to see if we can get it handled soon.
That said, if you email us support at company url, maybe I can make it up to you in some way or another. Just mention my name and remind me of this discussion.
> All this "iCloud Keychain" hype looks like just a sync functionality on top of current implementation.
There's Keychain Access and a preference pane in Safari for web passwords. It is exactly a sync feature added to the keychain implementation that exists in Mountain Lion and earlier.
I find it all very interesting so I try to learn where I can, but I leave the security stuff to our resident Chief Defender Against the Dark Arts (Jeff in the blog post). He's the guy who understands all of the security implications. He talks and I listen and try to absorb everything I can.
I figured that article was at least worth mentioning here.
Kyle
AgileBits Support
Thought of another problem: when you're forced to change your password. How do you encode that? Just add a version-N marker to the site name (which you have to remember)?
I'm not trying to sell you on 1Password, just point out problems with hash-only approaches :) And the storage-less nature is certainly a (big) plus when it works out, you're right.
--
And one possibly-significant danger you should be aware of: assuming you do something simple (which has the advantage of being buildable from scratch on any system, and easy to remember how), if your password is not globally unique then your security partly relies on the security of whoever else uses your password. If they lose it, anyone who knows that and guesses your username anywhere gets proof that you use the same password, so they can go test a bajillion sites immediately and with perfect success rates.
The standard technique for mitigating this is to salt the hash... but this is just another secret you have to store somewhere or memorize, so we're back where we started.
Also, you mention having to keep it physically secure. I don't think that's true; you can use anything you want to encrypt it, from passwords to smart cards to whatever.
You mention you have a long and cryptographically random password. I'm guessing (hoping?) that it consists of a bunch of words that are easier to remember, since humans are pretty bad at remembering things with sufficient entropy to count, particularly if they come in the form of unintelligible junk :)
I won't purchase the upgrade to 4 immediately. 1Password 3 is still working fine. Shared vaults look to be a nice feature, but other than that I don't think I need any of the changes.
Besides that, I'd like to see how good the iCloud Keychain will work in Mavericks/iOS (although it is not a cross-platform solution, Agilebits' Windows and Windows Phone apps haven't been stellar either).
Paid upgrades aren't a terrible thing. They allow you to continue to fund development on improved/better versions.
Without that, you risk ending up up like Sparrow or TextMate.
I don't expect a t-shirt from you but maybe you could provide a template?
https://www.merchline.com/agilebits/category.6106.c.php
They're "at cost" so we're not making money on the shirts but our users really loved them so we found a way to at least make them available at a reasonable price.
Kyle
AgileBits Support
I guess they could have sold yet another version of 1password 3 with the update for a lower fee, but that's confusing. At one point, with the upgrade from v2 to v3, agilebits had something like 4 or 5 versions of 1password in the app store (iphone/ipad/iphone & ipad combined version/v3) and while it offered better value, it was also confusing and off-putting for new customers.
I can't remember - does the iOS app store allow devs to charge for version upgrades? Or do you just have to create an all-new sku?
"However, considering that we need to be able to feed our families, it is likely that 1Password 5 will be sold as a separate paid app, like we did for 1Password 4 in the iOS App Store. We just decided to make 1Password 4 for Mac an exception to this." http://discussions.agilebits.com/discussion/16268/what-shoul...
It's clearer if there is one app per platform. Getting my wife to use a password manager is tough enough - Having to explain why there are 14 variations in the store would just add to the burden.
But as to why it was a new version in the first place.. This is Apple's supported answer for paid upgrades. They did the same for Logic Pro X.
But as an end-user who only owns an iPhone, the only "feature" I notice in 1Password 4 for iOS is "Dropbox syncing still works". Not very compelling.
Yes, this is basically it.
It was hard to pull our good friend 1Password 3 from sale, it still exists in the App Store, just not for sale. This allows purchasers to still download it, but it isn't for sale for new users.
One app is much easier than several. We had previously:
* 1Password for iPhone
* 1Password for iPad
* 1Password Pro (the two above as a universal app)
We did this because we released the iPhone app when they provided an SDK, and then the iPad was released but some users just wanted to pay for the iPad version, not the iPhone app again. So, we made it so users could do that, trying to provide a better price point for those users. For new users we stressed Pro for it's universal nature.
But, this was all very confusing. I can't tell you how many emails I answered that were from confused customers asking which one they would buy.
Having three apps was very hard.
This probably isn't the best place for this due to comment threading, but updating 1Password 3 for the newer Dropbox API would've taken a LOT of developer time. We did not use the Dropbox SDK because when we wrote 1Password 3's original code base an SDK did not exist, or if it did come out shortly after it wasn't acceptable for use for a variety of reasons, usually performance related. If I recall our developers correctly via various chats.
And if we did update for the newer Dropbox API then we'd be supporting two platforms (3 and 4) and it's just hard to do. Plus, the much bigger issue was we wanted to move the features of 1Password forward, for example, custom fields and sections. To get this support in 1Password 3 we would've had to have basically rewritten the entire data model and at that point all that's the same from the old app is the interface :)
The even bigger issue for a new app is supporting older platforms. Some devices can't run iOS 6, which 1Password 4 requires. Such as the iPad 1, which many users continue to use and love. If we had updated the app inline, those users would've lost the ability to download a working version if they needed to. This seems to have changed recently, as you can now download the last version to work for a particular iOS release. But this didn't exist last December, or leading up to release for months prior.
Now, hindsight being 20/20, many developers are doing new apps with regard to iOS 7 because it's a cleaner "break" and requiring more significant rewrites and provides a natural point at which to make a new app and charge for it. So, many developers are going through the same thing we did with iOS 6, but they're doing it with iOS 7.
Hope that provides some level of insight.
Kyle
AgileBits Support