Skip to content

GPG output - much smaller files. Delete --armor option for GPG call from CryptSync. #134

Description

@GoogleCodeExporter
What steps will reproduce the problem?
1. Enabling GPG option.

What is the expected output? What do you see instead?
Binary GPG output. ASCII-armored GPG output.

What version of the product are you using? On what operating system?
CryptSync 1.2.0. GPG 1.4.18. Windows 7 Enterprise x64.

Please provide any additional information below.
If we need armored output we can type gpg --version and see where gpg home 
folder is. Put there simple text file - gpg.conf with one string - armor, and 
enable ASCII-Armored output. But we can't disable it anyhow because GPG read 
parameters reads Cryptic Sync call parameters firstly, then reads gpg.conf 
file. Video 22 mb: 
https://mega.co.nz/#!NYYx3L6Z!REu7SQNpkLDmmdDTxjGIzEKEBW3HzL0XhUHuSanqG1I 


Original issue reported on code.google.com by avmats...@gmail.com on 27 Nov 2014 at 6:36

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions