brysontyrrell / encryptedstrings Goto Github PK

Encrypted values return "bad magic number" when attempting to decrypt on macOS Sonoma 14.2b3

Hello,

Using the script I can generate a credential on macOS Big Sur and macOS Monterey, however trying to decrypt the credentials on Ventura seems to fail with a Bad Decrypt error, likely because of a different version of the openssl binary on Ventura versus the others.

Cheers

In policy parameters isn't 1 - 3 reserved? Should calling ${4} be considerd the first parameter definable?

Thanks in advanced!

Hi, thank you so much for creating this!

I've found that it doesn't work in our environment because the password for the user that needs to be added to Filevault has a "!" in it. The script fails with an error. I know that's the reason because I tested with one computer, manually changing the password locally, and then creating the encrypted strings accordingly - and it worked.

Would you happen to know of a workaround so that this would work if there is an exclamation mark within the password string?

Thanks!
-Scott

When using the DecryptString function, if there is a non-native openssl installed and earlier in the PATH than the native openssl, the function fails with the error "Bad magic number".

The PR #5 fixes this.