You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@vr-varad - thanks for taking interest in the project. It is open for contribution, if you're able to support.
The thinking here is that the CLI (in packages/cli) should allow users to specify a file path during the encrypt command.
This can be done by either introducing a new flag or by performing a fuzzy file check if the input string 'looks' like I filepath. I prefer the former, as it is safer and more intentional.
# fuzzy/implicit# if there is a matching file path, encrypt the contents and store# if there is not a matching file path, encrypt the literal string and store (default string encryption behavior)
cryptfyi encrypt ./some-file-path.txt
# explicit
cryptfyi encrypt -f ./some-file-path.txt
The encrypt command should read the contents of the file and use that as the input for encryption.
Conversely, in the decrypt method, if the contents after decryption are determined to be a file, save it to a sane location. This might just be the current directory or the downloads folder.
Another option on the decrypt side is to prompt the user for where to send the file.
Make sure to use the node standard library to maintain a platform agnostic implementation.
allow a local file to be provided to
@crypt.fyi/cli
The text was updated successfully, but these errors were encountered: