All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dawid Ciezarkiewicz <dpc@asn.pl>
To: "Stephen J. Bevan" <stephen@dino.dnsalias.com>
Cc: netdev@vger.kernel.org
Subject: Re: [RFC] Ethernet Cheap Cryptography
Date: Wed, 18 Oct 2006 16:31:40 +0200	[thread overview]
Message-ID: <200610181631.41433.dpc@asn.pl> (raw)
In-Reply-To: <200610181115.12471.dpc@asn.pl>

On Wednesday, 18 October 2006 11:15, Dawid Ciezarkiewicz wrote:

> > * Given your desire not to change the size of the payload you have no
> >   space for MAC.  This makes it easier (but by no means easy) to alter
> >   the payload in such a way that it is still decrypted and considered
> >   valid.
> 
> Could you explain it more? I don't understand. You mean MAC as ... ?

Oh. Sorry. You mean message authentication code. Well - ccrypt have to live 
without it. From the start I knew that integrity will be the weakest point of 
ccrypt.

  reply	other threads:[~2006-10-18 14:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-15 16:20 [RFC] Ethernet Cheap Cryptography Dawid Ciezarkiewicz
2006-10-15 21:35 ` James Morris
2006-10-15 22:15   ` Dawid Ciezarkiewicz
2006-10-18  3:21 ` Stephen J. Bevan
2006-10-18  3:25   ` David Miller
2006-10-18  9:51     ` Dawid Ciezarkiewicz
2006-10-18 10:16       ` David Miller
2006-10-18 11:35         ` Dawid Ciezarkiewicz
2006-10-18  9:15   ` Dawid Ciezarkiewicz
2006-10-18 14:31     ` Dawid Ciezarkiewicz [this message]
2006-10-19  3:57     ` Stephen J. Bevan
2006-10-19 15:58       ` Pawel Foremski
2006-10-20  2:18         ` Stephen J. Bevan
2006-10-20  2:59           ` David Miller
2006-10-21  2:17             ` Stephen J. Bevan
2006-10-21  2:20               ` David Miller
2006-10-20 20:18           ` Pawel Foremski
2006-10-21  1:58             ` Stephen J. Bevan
2006-10-21  2:28               ` Stephen Hemminger
2006-10-21 15:33                 ` Pawel Foremski
2006-10-21 15:12               ` Pawel Foremski
2006-10-22  0:05                 ` Stephen J. Bevan
2006-10-20 19:50       ` Dawid Ciezarkiewicz

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=200610181631.41433.dpc@asn.pl \
    --to=dpc@asn.pl \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@dino.dnsalias.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.