Using the same file as input and output produces a corrupt result without notice. about age HOT 7 CLOSED

For reference, I implemented this check in str4d/rage#202 (after agreeing to change rage -o to match age's behaviour and overwrite existing files in str4d/rage#168).

from age.

Ping @FiloSottile

from age.

I implemented it and pushed a pull request. Feel free to try it. I'm already using it.

from age.

I have (likely) the same issue using armored encoding.

Will the PR fixing this be merged?

Thanks for the update.

from age.

Given that this regrettable characteristic irremediably corrupts original files, it's really scary that this is still active in the current release (1.1.1) one year after initial report... 🤷‍♂️

from age.

Thank you for the report. We can't save the user if they use the shell's < or >, but we now detect what we can.

from age.

@FiloSottile #523 ?

from age.