From: Jari Ruusu <jariruusu@users.sourceforge.net>
To: netguru <netguru@home.nl>
Cc: linux-crypto@vger.kernel.org, linux-crypto@nl.linux.org
Subject: Re: Util linux 2.17, loop-aes patch
Date: Wed, 20 Jan 2010 16:59:50 +0200 [thread overview]
Message-ID: <4B571A66.CB1A074A@users.sourceforge.net> (raw)
In-Reply-To: 1194867068.20100119201108@home.nl
netguru wrote:
> i was wondering wether there will be a working patch for
> util-linux-2.17 anytime soon. I have ported it over to 2.17, and will
> happily supply the patch for those interested. I cannot guarantee its
> a 100 % Ok though. I feel more comfortable with the official patches
> from maintainers :-)
http://loop-aes.sourceforge.net/updates/util-linux-ng-2.17-20100120.diff.bz2
http://loop-aes.sourceforge.net/updates/util-linux-ng-2.17-20100120.diff.bz2.sign
--
Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD
-
Linux-crypto: cryptography in and on the Linux system
Archive: http://mail.nl.linux.org/linux-crypto/
prev parent reply other threads:[~2010-01-20 14:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-19 19:11 Util linux 2.17, loop-aes patch netguru
2010-01-20 14:59 ` Jari Ruusu [this message]
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=4B571A66.CB1A074A@users.sourceforge.net \
--to=jariruusu@users.sourceforge.net \
--cc=linux-crypto@nl.linux.org \
--cc=linux-crypto@vger.kernel.org \
--cc=netguru@home.nl \
/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.