dashohoxha at gmail.com
Mon Mar 21 16:49:41 CET 2016
Hi Bernhard, thanks for having a look at it.
On Mon, Mar 21, 2016 at 3:05 PM, Bernhard Reiter <bernhard at intevation.de>
> Hi Dashamir,
> On Friday 18 March 2016 at 09:49:16, Dashamir Hoxha wrote:
> > I am writting some shell scripts for making GnuPG more accessible and
> > easier to use:
> > - https://github.com/dashohoxha/egpg
> I like the goal of making gpg2 more accessible.
> However I am not sure that you are actually reaching the goal
> by using sh wrappers. When looking at the man pages, it seems
> that they are already long with a number of phrases to learn.
> Most of these commands are not much easier than the direct gpg2
> commands they are aiming to replace.
Yes, but the overall number of commands and options supported
is 10 times smaller than those of gpg2. Tutorials about egpg are also
much shorter. And the default values of the options are more suitable
for a beginner (at least in my opinion).
> Drawbacks I see with your approach:
> * people will have to learn a slightly different set of commands
> with egpg and gpg2 and sooner or later will use the gpg2 commands
> and then they will be confused or have extra learning efforts.
I hope that the transition will be smoother, once they are familiar with
> * shell scripts will not work on plattforms without a shell
> (e.g. Windows)
I have heard that you can use shell scripts on Windows (with cygwin).
> * I haven't looked into the .epgp directory, but it may have some configs
> and then the behaviour of other applications will depend on whoch config
> they use.
To switch from using egpg to using gpg2 you just need to change GNUPGHOME
from '~/.gnupg' to '~/.egpg/.gnupg'.
> * BTW: There is a potential name clash with
I don't think they clash because that is a contracted job this is a
> Ideas for improvements:
> * I you must, write wrappers code it in something more plattform
> e.g. in python3 (using pyme or pygpgme where appropriate)
The problem with Python is that I am not familar with it (and there may be
other problems too, that I don't know).
But if you could fork egpg and re-implement it in Python, it could be great.
> * Suggest and improve the original gpg2 command line interface, so that
> usage is easier and the more esotheric options will not be seen or used
> by default.
> * Write a beginners man page for the original gpg2, which covers only the
> use cases.
I guess these two are suggestions for EasyGpg2016.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gnupg-users