Mojave: EXC_BAD_ACCESS (SIGSEGV) after importing about csvkeychain

[lifepillar]

Nice 🙂 This should be reported to Apple as a critical issue. It may be that my script sends bad input to KA, but in no way should the app crash.

I’ll try to reproduce it. Do you have any idea what could be the culprit? E.g., have you tried importing just a few records at a time to narrow down which ones may cause trouble?

[caramdache]

It's a little difficult to debug given there are 667 entries in the keychain unfortunately. BTW, is there a reason that out of these 667 entries, only 521 appear in the exported CSV file? And is there any way to restrict the export to only certain types, like Internet Password?

[caramdache]

And how I import the entries into the iCloud keychain instead? I've always found weird that Apple has kept both and don't quite understand why some entries endup in one or the other keychain for no obvious reason.

[lifepillar]

is there a reason that out of these 667 entries, only 521 appear in the exported CSV file?

Things that are not exported are likely not passwords, e.g., certificates, private keys, etc…

is there any way to restrict the export to only certain types, like Internet Password?

Currently, there isn't. But you can post-process the CSV output, e.g., in Numbers or Excel.

And how I import the entries into the iCloud keychain instead?

iCloud keychain uses a completely different format. CSVKeychain uses the system's security command-line tool to import/export items, and AFAIK it does not work with iCloud keychains. What you can do is

• create a new keychain (Keychain Access > File > New Keychain…);
• import items in the newly created keychain;
• select and copy the imported items (or the ones that you want to copy into iCloud);
• select the iCloud keychain and paste.

You will likely be asked to insert a password for each pasted item: when the first dialog appears, you may launch the script in the Readme to automate the process.