Am Di 30.07.2013, 14:28:49 schrieb Werner Koch:
> Sure. Here is a very basic one:
Took me some time to give that a try but...
> echo "OK - what's up?"
> while read cmd rest; do
> echo "cmd=$cmd rest=$rest" >&2
> case "$cmd" in
> \#*)
> ;;
> GETPIN)
> ech
Hello,
I have just been reading the man page of gpg-agent and found this:
--allow-loopback-pinentry
Allow clients to use the loopback pinentry features; see the option pinentry-
mode for details.
That made me curio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/10/2013 06:27 PM, Doug Barton wrote:
> On 12/10/2013 12:42 PM, Phillip Susi wrote: | So my old subkeys are
> about to expire so I created some new ones
>
> Why are you creating new ones instead of simply extending the
> expiry of the existing
Hello,
some time ago I had a discussion about what a really simple crypto GUI should
look like. This is the result:
http://www.crypto-fuer-alle.de/wishlist/simple-crypto-gui/index.en.html
It's just an HTML page which allows you to jump from screen to screen (for
most suggested features) via in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/10/2013 12:42 PM, Phillip Susi wrote:
| So my old subkeys are about to expire so I created some new ones
Why are you creating new ones instead of simply extending the expiry
of the existing ones?
-BEGIN PGP SIGNATURE-
Version: GnuPG v
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So my old subkeys are about to expire so I created some new ones at
home and exported them with --export-secret-subkeys. When I try to
import them at work, gpg just says I already have that key and stops.
Why isn't it merging the new subkeys? I ended
Am Di 10.12.2013, 15:42:40 schrieb Phillip Susi:
> So my old subkeys are about to expire so I created some new ones at
> home and exported them with --export-secret-subkeys. When I try to
> import them at work, gpg just says I already have that key and stops.
> Why isn't it merging the new subkeys
