Files are decoded as binary

[vjousse]

Hi,

We're trying to setup transcrypt in our team, everything works fine except for one member who gets the file content (json) as binary.

Some information about the versions installed on his Mac:

And the Mac version:

Another team member with an M2 Mac doesn't have problems.

Any idea how we could try to debug what's going on?

Thanks!

[jmurty]

Hi,

I haven’t seen this problem before.

I’m suspicious of the warning message after initialising transcrypt saying that “Executing command … git … timed out”

Are the encrypted files large?
And is the Homebrew-installed git version run during init of transcrypt the same as the “Apple Git-145” reported in the later screenshot?

[paulboosz]

Hi,

Are the encrypted files large?

No they are 0.4 mb

And is the Homebrew-installed git version run during init of transcrypt the same as the “Apple Git-145” reported in the later screenshot?

I updated git when troubleshooting from 2.39.3 to 2.47.1. I retried from a clean dir with the new git version 2.47.1, it failed as well.

I still have the [WARN] - (starship::utils): Executing command "/opt/homebrew/bin/git" timed out.
I don't have any reports about git in Console on Mac

[vjousse]

@jmurty we finally found the issue. The problem is that transcrypt doesn't fail when the password is not the good one.
We are calling transcrypt in a bash script using this command: transcrypt -y -c aes-256-cbc -p "$TRANSCRYPT_KEY"

If $TRANSCRYPT_KEY is not set for whatever reason, the command executed will be transcrypt -y -c aes-256-cbc -p "" and transcrypt is ok with that. It says The repository has been successfully configured by transcrypt. but the encrypted files are shown as binary.

[jmurty]

Hi @vjousse thanks for following up, it should have occurred to me that binary junk is a likely outcome of using the wrong password when decrypting files. Unfortunately transcrypt doesn't recognise when the password is incorrect and producing rubbish.

Recognising an incorrect password would be difficult so isn't a feature I'm likely to add. But transcrypt should refuse to do any work when it gets an empty value for the password, since that is obviously and always wrong. I'll aim to improve transcrypt's handling of this situation.

[jmurty]

I have added a safety check to fail command with error message "empty password" if an empty password is provided to the -p or --password options