5 ms·

you know its trival to export, right? There's nothing more secure than Keychain if you're in the Apple ecosystem. Nothing gets more scrutiny from the entire ind

you know its trival to export, right? There's nothing more secure than Keychain if you're in the Apple ecosystem. Nothing gets more scrutiny from the entire industry, at least.

recursive 3y ago
The "ecosystem" comes as non-several package. Like for instance, my pet issue "if" I'm in the ecosystem, I'd have to give up my headphone jack. And all the rest of it. The "if" is probably most of the problem.
- hot_gril 3y ago
  Indeed the jack removal was the first thing that ever made me think of switching. That was a scam.
- acheron 3y ago
  > I’d have to give up my headphone jack Not to mention your 3.5” floppy drive!
  - recursive 3y ago
    I don't really have much use for that. Usb drives totally replace them for my use cases. Do you understand the advantages that headphone jacks have? If not, you could start there.
  - hot_gril 3y ago
    If jack is floppy drive then Bluetooth is wax cylinder
lxgr 3y ago
If you know of a way to export a passkey from iCloud Keychain to a non-Apple device, please do share it! Otherwise I'd call that lock-in as well.
- hot_gril 3y ago
  It's easy on a Mac since Safari has a CSV export feature. No such thing on an iPhone.
  - lxgr 3y ago
    Have you tried exporting a passkey that way? Last time I did, I only got passwords out, not passkeys (not that there is an interoperable standard for them anyway).
    - hot_gril 3y ago
      Oh, I didn't realize passkeys and totp aren't the same thing. Totp secrets go into the CSV. Don't think I even have any passkeys to test with. And supposedly 1Password doesn't let you export either. This seems bogus. I'd rather simply use a random per-site password; looks like passkeys are the same except non-interoperable.
      - lxgr 3y ago
        Bitwarden lets you export them as part of at least their JSON export, but unfortunately there's no specified interoperable format yet, so you can only import them back into Bitwarden (which you can at least self host; you could reimplement their serialization format if you're really determined). There's some movement in that area in the related FIDO working groups, but I think we'll (by design) never see something like CSV export, and it'll be more like a standardized account migration. > I'd rather simply use a random per-site password; looks like passkeys are the same except non-interoperable. They're significantly better than a random per-site password since they can't be compromised on the server side (due to being based on public key cryptography), unlike regular passwords and TOTPs.
        deleted 3y ago
        [deleted]
        hot_gril 3y ago

you know its trival to export, right? There's nothing more secure than Keychain if you're in the Apple ecosystem. Nothing gets more scrutiny from the entire industry, at least.

recursive 3y ago

The "ecosystem" comes as non-several package. Like for instance, my pet issue "if" I'm in the ecosystem, I'd have to give up my headphone jack. And all the rest of it. The "if" is probably most of the problem.

hot_gril 3y ago
Indeed the jack removal was the first thing that ever made me think of switching. That was a scam.
acheron 3y ago
> I’d have to give up my headphone jack Not to mention your 3.5” floppy drive!
- recursive 3y ago
  I don't really have much use for that. Usb drives totally replace them for my use cases. Do you understand the advantages that headphone jacks have? If not, you could start there.
- hot_gril 3y ago
  If jack is floppy drive then Bluetooth is wax cylinder

lxgr 3y ago

If you know of a way to export a passkey from iCloud Keychain to a non-Apple device, please do share it! Otherwise I'd call that lock-in as well.

hot_gril 3y ago
It's easy on a Mac since Safari has a CSV export feature. No such thing on an iPhone.
- lxgr 3y ago
  Have you tried exporting a passkey that way? Last time I did, I only got passwords out, not passkeys (not that there is an interoperable standard for them anyway).
  - hot_gril 3y ago
    Oh, I didn't realize passkeys and totp aren't the same thing. Totp secrets go into the CSV. Don't think I even have any passkeys to test with. And supposedly 1Password doesn't let you export either. This seems bogus. I'd rather simply use a random per-site password; looks like passkeys are the same except non-interoperable.
    - lxgr 3y ago
      Bitwarden lets you export them as part of at least their JSON export, but unfortunately there's no specified interoperable format yet, so you can only import them back into Bitwarden (which you can at least self host; you could reimplement their serialization format if you're really determined). There's some movement in that area in the related FIDO working groups, but I think we'll (by design) never see something like CSV export, and it'll be more like a standardized account migration. > I'd rather simply use a random per-site password; looks like passkeys are the same except non-interoperable. They're significantly better than a random per-site password since they can't be compromised on the server side (due to being based on public key cryptography), unlike regular passwords and TOTPs.
      - deleted 3y ago
        [deleted]
      - hot_gril 3y ago