Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

1Password migrants thread

twb01_98 said:
I'll probably get flamed for asking, but why not use keychain??
Click to expand...
I wouldn’t flame you, but I will note that you could have found answers to your question posted up-thread.

I’m sorry I ever used iCloud Password, because I haven’t been able to permanently delete some entries. (Ref: Post #2,041 in this thread.) This is a security issue because if someone ever broke into my iCloud account, they would have up to two of the three pieces of information they need to log into one of my un-deletable accounts. (The three pieces of information are the website, username (email address), and the password, and I’ve changed any password that was ever in iCloud.)

I am now using Codebook on both my Mac and iPhone, and storing passwords locally and syncing via WiFi. Unlike from what I understand about doing this with Bitwarden, which sounds a bit complicated and inconvenient for the average person, setting up the syncing was very quick and easy. Although the syncing is manual with Codebook, I don’t find this to be much of a burden as I don’t add or change entries that often, and mostly work on my Mac. Additionally, the syncing process takes me less than 30 seconds. Finally, the syncing process appears to be very secure, and I rest better at night knowing that none of my passwords have ever been on any server. (Codebook is not included in my iPhone backups.)
 
  • Like
Reactions: MacBH928
berb said:
1Password 7.9.11 can use standalone vaults, sorry if I described it poorly.

Release notes:
Click to expand...

Okay, then you still are safe. I'd stay on 1PW 7 for as long as you can keep it running, especially if you're not wanting to move your vaults to a SaaS. I know I didn't want that, especially given the breaches various hosts have had; I was a 1PW 6 user, so I migrated away.

BL.
 
any one checked proton pass yet?

I gave it a go but has a lot of limits. Feels more like Keychain
 
bsmr said:
What about Enpass in comparison? WIFI Sync - no cloud (or only your own) - looks quite interesting.
Click to expand...

I use Enpass. Its like a 1password wannabe. Here are critisim:-

1) Autofill intelligence needs improvement.
2) Developers seem to be small in number and hardly address issues
3) Needs "polishing"
4) Wifi sync is not seamless (but so was 1password)
5) The fact that its "closed" source and is not popular might raise some security concerns. I do not trust security from smaller vendors.

Best thing is to give it a shot and see if you like it. I really wanted Enpass to be the new "safe haven" from 1password migrants but the developers did not put the proper effort in.
 
  • Like
Reactions: TwoBytes, drumcat and bsmr
That Google sheet was awesome. I feel like I've checked out everything at this point. I've made a decision on how I'll be going forward. Not that you asked, but I'll share my reasons:

The winner is Strongbox. Even though I already own Minimalist lifetime, I'm going to set them aside. Honestly, it just comes down to the fact they have removed the perpetual license option. It's also Mac-only, which doesn't affect me much at the moment, but it does mean I can't use it on Windows, and that's inconvenient.

For anyone new to this thread, the main advantage (IMO) to Strongbox is that they use an existing format - the keepass database. (*.kdbx) This allows the database you use to be opened by FOSS such as MacPass and KeePassXC. 1Password wasn't exactly holding my passwords "hostage", but I'm very glad to know that I will never be in a proprietary database again.

Strongbox handles iOS and all of the sync, and seems to do it all very well. I've had no issues as expected. Yes, there is a free version same as the others, but I'm not interested in those limitations.

Pros:
- Integration with Apple Watch, FaceID, TouchID
- Handles anything you throw at it
- Seems to import ok
- Open source format
- Lifetime, perpetual license

It's not all perfect of course...

Credit cards, passports, identifications… all a ball ache. This has a lot to do with the format of the .kdbx - it handles everything, so there isn't templates yet. You have to enter your information fairly manually. Strongbox has said it's on their roadmap to implement these templates, but they aren't there yet. That's the one big miss for me.

So I will continue to mix Keychain and Strongbox, which was never ideal and still isn't. Credit cards will be filled out by the OS. iOS won't write passwords into Strongbox, so that's obviously a downside - but that's universal.

Cons:
- Import isn't perfect with many types requiring custom fields
- Credit cards still need the OS
- Organisation within the database is generally manual
- Icons available, but not automatic

And I drop all of this now because they are going to be 20% off all their stuff starting later today (I think; Black Friday sale).

This isn't intended to be a "this one's best for everyone" statement. My constraints were always there. #1 for me is perpetual licensing - I did not look at any applications which required renting. I won't do monthly or annual payments, especially for something like passwords. They are the ultimate "hostage", and I refuse to play that game. And the fact that FOSS can open the database means I'm never beholden to a company again. Looking at you, FragileBits.

I hope this helps someone out there.

EDIT: Adding to this. I've found that when creating a main database for yourself, it's worthwhile to create "Templates". For example, fill out a blank entry, but add Credit Card Number, expiration, Code, etc. etc. to the custom fields. Then save it and put it in a group called "Templates". When you have a new entry, duplicate the specialised template, and you can enter everything into the custom fields. It saves a bunch of time.
 
Last edited:
  • Like
Reactions: Michaelgtrusa, max2 and TwoBytes
If strong box has robust import/export , and an assistant app akin to Enpass/1password I might switch. I actually I think I will switch.
 
Mr. Heckles said:
I’m trying it and it’s not bad. I don’t like I don’t have custom fields and other little things.
Click to expand...
It's templates that are the missing part. There's any number of custom fields. The catch is you have to enter them.

What's easy for me is you can actually create "blank" entries, and duplicate them. So for example, you make a "Credit Card Template" entry with all the custom fields done, but empty. Then duplicate it and make that your entry. Then create a Group called Templates, and leave them all in there.

I'm sort of baffled why this isn't already a thing. Just make a dozen of these in every database, hide them, and then have them as an option when making a new one.
 
Last edited:
  • Like
Reactions: mailbuoy
drumcat said:
It's templates that are the missing part. There's any number of custom fields. The catch is you have to enter them.

What's easy for me is you can actually create "blank" entries, and duplicate them. So for example, you make a "Credit Card Template" entry with all the custom fields done, but empty. Then duplicate it and make that your entry. Then create a Group called Templates, and leave them all in there.

I'm sort of baffled why this isn't already a thing. Just make a dozen of these in every database, hide them, and then have them as an option when making a new one.
Click to expand...
Yes, the templates. With 1Password, I can have 4 vaults and they all show as one when I open it. I don’t have to remember which vault a certain password is in. I wish I could do this with Strongbox.
 
Mr. Heckles said:
Yes, the templates. With 1Password, I can have 4 vaults and they all show as one when I open it. I don’t have to remember which vault a certain password is in. I wish I could do this with Strongbox.
Click to expand...
You have the ability to search each vault for key word(s) that will trigger you finding the password you want. Granted, that is not the same as what you are speaking of but, it works.
 
Apple_Robert said:
You have the ability to search each vault for key word(s) that will trigger you finding the password you want. Granted, that is not the same as what you are speaking of but, it works.
Click to expand...
I’m sorry, I meant databases. Am I able to search databases all at once? 1Password calls then vaults.
 
gregmac19 said:
You have at least these choices left: Codebook, Enpass, eWallet, and Sticky Password.

Edit: I use and like Codebook, but it doesn’t yet support credit cards. They are planning on adding this capability either as an upgrade to the current release (Codebook 4) or in the next major release (Codebook 5).

StickyPassword looks promising, but I don't like that it doesn’t have biometric authentication for MacOS. I contacted the company, and the support person said that this is coming.
Click to expand...
I am replying to my own post, because what I said about Codebook not supporting credit cards is not accurate. While it is true that autofill for credit cards is not supported on iOS and Android, you can use Codebook’s “Secret Agent” helper application on macOS and Windows to autofill credit card information. I regret this error, which wouldn’t have happened had I read the clear directions more carefully.
 
  • Like
Reactions: drumcat
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back