When you encrypt multiple files in a folder, GnuPG encrypted files have no
icon. It is difficult to immediately identify which are the encrypted files.
Any specific reason why encrypted files have no icon?
...
RP
___
Gnupg-users mailing
Hi Werner and Justus - thank you for the info !!
Is this issue normally associated with a --passphrase-fd 0 command being used
with gpg2? I am doing the following:
v_recipient='RECIPIENT'
v_passphrase=`cat pfile.txt`
/usr/local/bin/gpg2 --batch --local-user $v_recipient
--passphrase
The problems always start with the words "public key"...
On 30/09/16 15:22, Werner Koch wrote:
>
> So for example "lock" and "private key" may be better.
"Lock and key" works for symmetric crypto, because you lock and unlock
with the same key. "Latch and key" is the best analogy I know of to
pub
On Fri, Sep 30, 2016 at 04:22:39PM +0200, Werner Koch wrote:
>
> The root of the problem might be the concept of "public key" and
> "private key". You need to educate users that these are very different
> things but still belong together.
There is one more: "secret key".
signature.asc
Descript
On 09/30/2016 08:24 AM, Robert J. Hansen wrote:
>> I'd start with -BEGIN PGP PUBLIC KEY BLOCK- :)
>
> You are technically correct (the best kind of correct!) [1] -- no, wait!
> That's "key block", not "keyblock"!
>
> I'm more technically correct! I win! :)
>
> In all seriousness, the
Hi Arbiel,
Arbiel (gmx):
> Hi
>
> Thank you Andrew.
>
> In the material I've been ready lately, all examples are written in a
> programming language and I only have abilities in bash scripting.
>
> Can somebody, please, direct me toward a url where they provide bash
> scripting examples.
[...]
On 09/30/2016 04:24 PM, Robert J. Hansen wrote:
>> I'd start with -BEGIN PGP PUBLIC KEY BLOCK- :)
>
> You are technically correct (the best kind of correct!) [1] -- no,
> wait! That's "key block", not "keyblock"!
>
> I'm more technically correct! I win! :)
>
> In all seriousness, the
> I'd start with -BEGIN PGP PUBLIC KEY BLOCK- :)
You are technically correct (the best kind of correct!) [1] -- no, wait!
That's "key block", not "keyblock"!
I'm more technically correct! I win! :)
In all seriousness, the only context in which I've seen "key block" has been
the begi
On Fri, 30 Sep 2016 14:46, r...@sixdemonbag.org said:
> https://www.gpg4win.org/doc/en/gpg4win-compendium_12.html
We had a long discussion many years ago on how to name the beast. The
compendium somewhat prioritizes S/MIME and thus we tried to unify the
terms by using "certificate" also for Open
On Fri, 30 Sep 2016 14:37, jus...@g10code.com said:
> fallback pinentry failed to open the terminal due to the fact that stdin
> of the gpg process is not connected to a terminal. The latter can
> happen for example when gpg is used in a pipe.
That does not matter. The pinentry opens the tty on
Hi
Thank you Andrew.
In the material I've been ready lately, all examples are written in a
programming language and I only have abilities in bash scripting.
Can somebody, please, direct me toward a url where they provide bash
scripting examples.
Arbiel
Le 28/09/2016 à 15:25, Andrew Gallagher a
On 09/30/2016 02:46 PM, Robert J. Hansen wrote:
>> In OpenPGP this is called a "keyblock".
>
> Where can I find this usage documented? In almost 25 years in the PGP
> community I've heard the word "key" used >95% of the time, "certificate"
> <5% of the time, and this is literally the first time I
> In OpenPGP this is called a "keyblock".
Where can I find this usage documented? In almost 25 years in the PGP
community I've heard the word "key" used >95% of the time, "certificate"
<5% of the time, and this is literally the first time I've heard the
word "keyblock".
Also see:
https://www.gn
Hello,
please don't drop the mailing list when replying.
Jim Ernst writes:
>> I am currently testing keys I created using gpg version 2 2.1.15 (libgcrypt
>> 1.7.3) and I am trying to encrypt a file using a shell script in a LINUX
>> environment. I am getting the following error when the comman
On 29/09/16 17:17, Robert J. Hansen wrote:
> I have to admit to being extremely annoyed with the state of the language we
> use.
IMO, TOFU has just made it even worse.
I tried to be really strict, talk about ownertrust and validity. Always trying
to keep them separate. Personally avoiding the wo
On Thu, 29 Sep 2016 12:23, gn...@jelmail.com said:
> * A Public-Key packet starts a series of packets that forms an OpenPGP
> key (sometimes called an OpenPGP certificate).
In OpenPGP this is called a "keyblock". The term certificate is used
only for some special thinks (revocation certificate).
Hi,
tim.dcl...@gmail.com:
> i am using GPA 0.9.9 to encrypt text file data. i copy/paste my text
> into the clipboard and hit encrypt. Im prompted to choose public key.
> After choosing, i get the following results (less the blah blahs).
>
> I would like to do this from a command line so i can do
> [1] http://www.ietf.org/mail-archive/web/openpgp/current/msg07712.html
>
> [2] ftp://ftp.pgpi.org/pub/pgp/6.5/docs/english/IntroToCrypto.pdf
>
Great link [1], very interesting. I think the language used hasn't
helped the uptake of this technology. The other thing mentioned in there
is trust vs
> I have to admit to being extremely annoyed with the state of the language we
> use. OpenPGP is hard enough to learn without having to be confused by
> multiple names for the same algorithms, confusing usage of "certificate",
> "key", and "Key", and every other bit of linguistic tomfoolery we
19 matches
Mail list logo
