From: Marcin Borkowski <mbork@wmi.amu.edu.pl>
To: help-gnu-emacs@gnu.org
Subject: Re: A question on encryption
Date: Thu, 28 Aug 2014 08:30:59 +0200 [thread overview]
Message-ID: <20140828083059.199359f5@aga-netbook> (raw)
In-Reply-To: <7zbnr5mesz.fsf@example.com>
Dnia 2014-08-28, o godz. 05:14:04
David Hume <David.Hume@hushmail.com> napisał(a):
> Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:
>
> > I created a test file (call it "test") with a single line of text
> > and did two things:
> >
> > 1. C-x C-f test RET, C-x C-w test.gpg RET
> >
> > Then I selected the key and hit ok.
> >
> > 2. From the command line:
> > gpg -e -r key-id -o test2.gpg test
> >
> > The two resulting files were different (difference in length of 3
> > bytes; find-file-literally and manual inspection showed that the
> > beginnings were identical, but the endings were not).
> >
>
> If you encrypt the same file twice, you don't get the same encrypted
> file. I think gpg will add random data to the end of the file. You
> could test that theory by encrypting the same file twice using your
> command line gpg. I am pretty sure I have done that in the past and
> observed that I did not get the same encryption twice.
Good point, that is true (which I've just checked experimentally) -
thanks for pointing that out! But - the *size* remains the same
(well, it did 4 times, at least). And with CLI gpg versus EPG, I also
get *consistently* differences in length (by a few bytes)!
Best,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University
next parent reply other threads:[~2014-08-28 6:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.7656.1409167662.1147.help-gnu-emacs@gnu.org>
[not found] ` <7zbnr5mesz.fsf@example.com>
2014-08-28 6:30 ` Marcin Borkowski [this message]
2014-08-29 3:22 ` A question on encryption Stefan Monnier
2014-08-29 12:28 ` Marcin Borkowski
2014-08-27 19:27 Marcin Borkowski
2014-08-28 0:22 ` Eric Abrahamsen
2014-08-28 1:00 ` Marcin Borkowski
2014-08-28 6:53 ` Alan Schmitt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140828083059.199359f5@aga-netbook \
--to=mbork@wmi.amu.edu.pl \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).