In current version it’s not possible to specify wildcards for files, so encrypting single file is the only option with –symmetric command.Ĭmd> gpg2 -batch -yes -passphrase mysecret -output "D:\ETL\MYBACKUP.BAK" -decrypt "D:\TEMP\4win for Windows 10 - Full description ![]() With –output switch we’re telling gpg where to write encrypted file – this parameter always precedes command (–symmetric in this case), otherwise we get an error. We’re telling gpg2 that we’re running command in batch mode (–batch), that we don’t want to compress data since input file is already compressed (-z 0) and that we wan’t to use AES128 encryption. Here is an example of encrypting single file with gpg2:Ĭmd> gpg2 -batch -yes -passphrase mysecret -z 0 -cipher-algo AES128 -output "D:\TEMP\" -symmetric "D:\ETL\MYBACKUP.BAK" SET PATH=C:\Program Files (x86)\GNU\GnuPG %PATH% Make sure that you have Gpg4win binaries in PATH (try to run gpg2), if they’re not then add to your path: Current version Gpg4win 2.2.21 is shipping GnuPG 2.0.22. ![]() Fortunately, Windows port is well maintained and for simple batch use it’s enough to install Gpg4win-vanilla package from. GnuPG is installed on every Linux box that I work with. This is a short note about using GnuPG on Windows 7/2008R2 to encrypt file(s) with symmetric AES encryption.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |