From: Werner Koch <wk@gnupg.org>
Subject: Re: 2002-01-08 / sending encrypted, but storing plain
Date: Thu, 09 Jan 2003 12:14:46 +0100 [thread overview]
Message-ID: <87fzs2y3q1.fsf@alberti.g10code.de> (raw)
In-Reply-To: <avi8bd$gd9$1@main.gmane.org> (Andreas Fuchs's message of "Wed, 8 Jan 2003 22:22:37 +0000 (UTC)")
On Wed, 8 Jan 2003 22:22:37 +0000 (UTC), Andreas Fuchs said:
> somebody could a) read them and, worse, b) launch a known-plaintext
> attack on your messages and find out your private key without your
> knowledge. Two bad things, IMHO.
Modern crypto protocols are in any practically aspects safe against
known-plaintext attacks. Furthermore the messages are encrypted using
random session keys and they are not stored anywhere.
Salam-Shalom,
Werner
next prev parent reply other threads:[~2003-01-09 11:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 16:38 Jochen_Hayek
2003-01-08 22:22 ` Andreas Fuchs
2003-01-09 11:14 ` Werner Koch [this message]
[not found] <m3iswzfuwm.fsf@HayekA.Hayek.com>
2003-01-08 19:39 ` Werner Koch
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fzs2y3q1.fsf@alberti.g10code.de \
--to=wk@gnupg.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 NNTP newsgroup(s).