L'octidi 28 messidor, an CCXXIV, Jonathan Dowland a écrit :
> Do not CC me, I am subscribed to the list. This is clear in the CoC
> for lists.debian.org,
Not CCing this once. I recently explained in great length why this point of
the CoC is broken and should be ignored.
> an
Do not CC me, I am subscribed to the list. This is clear in the CoC
for lists.debian.org, and it's prominently in the mail signature of
my mail you replied to.
On Fri, Jul 15, 2016 at 12:36:46PM +0200, Nicolas George wrote:
> L'octidi 28 messidor, an CCXXIV, Jonathan Dowland a écrit :
> > FWIW, la
On Saturday 25 June 2005 20:53, nuno romano wrote:
> I got the following warning trying to create a
> crypto file system in hda10 partition of my
> hard disk: I did ->
>
> modprobe cryptoloop
> modprobe aes
>
> losetup -e aes-256 /dev/loop0 /dev/hda10
> Password:
> ioctl: LOOP_SET_STATUS:
On Wed, 2003-01-01 at 00:42, Jack O'Quin wrote:
> I did it the Debian Way, which works very well. :-)
>
> But, that *does* involve running make-kpkg, the Debian Way to compile
> kernel images. Charlie, if you haven't tried this script, it's a
> really clean way to make kernels and kernel module
Stefan Radomski <[EMAIL PROTECTED]> writes:
> It seems to me that Jack managed to get cryptoloop working without
> recompiling the kernel, he did it 'the debian way', as reported here:
>
> http://lists.debian.org/debian-user/2002/debian-user-200212/msg05110.html
I did it the Debian Way, which wo
On Tue, 2002-12-31 at 21:25, Charlie Reiman wrote:
> Thanks. You mean:
>
> http://lists.debian.org/debian-user/2002/debian-user-200212/msg04708.html
>
> It looks like I have to rebuild the kernel to get this working. As I
> mentioned, I really can't do that. Is it possible to get the patched
> c
> -Original Message-
> From: Stefan Radomski [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, December 31, 2002 12:02 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Crypto issues
>
>
> Hi Charlie,
> please search the archive, exactly this issue was solved a week ago..
Hi Charlie,
please search the archive, exactly this issue was solved a week ago..
--
"boredom is not a burden anyone should bear"
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Personally, I rarely use the debianized kernel source... to impatient
to wait for new releases to be packaged! :-) For whatever it's worth,
I'm having good results with the crypto patches and upstream source.
The one thing to watch out for is loopback filesystems (whether
encrypted or not)... the
[EMAIL PROTECTED] wrote:
>
> Hi,
> I want to compile the 2.4 kernel + crypto patch.
> apt-getting the kernel-source is no problem, but the international
> kernel patch isn't yet debianized.
>
> What's the best option?
> -Patching the debianized kernel source.
> -Patching the non-debianized kernel
On Fri, Apr 21, 2000 at 08:27:52PM -0800, Ethan Benson wrote:
>
> > and if you want to compile them there's always 'apt-get --compile source
> > packagename'. if you haven't used it before here's how it works :)
>
> with the annoying side affect of apt insisting on replacing the
> locally compile
On Fri, Apr 21, 2000 at 12:29:30PM -0800, Adam Shand wrote:
> > If you're really hard core about security and encryption (and I'm going
> > to be heretical here, but hey, I have to plug my home), try OpenBSD.
> > Since it's main repository is in Canada, US crypto laws don't apply. I
> > played w
On Sat, Oct 14, 2000 at 07:35:52PM -0600, Ray Percival ([EMAIL PROTECTED])
wrote:
> I'm looking for a good command line tool to encrypt /home with I need
> something that can handle large (4096 bit) keys. Any suggestions?
> Thanks very much.
Please set your linewrap to 72 characters.
apt-ge
Title: RE: crypto patch
hesitant to put it in by default. Who knows, maybe some other
distirbution does? Bastille Linux?
[Andrew Weiss]
So would you run this OS on a headless server? :-)
Epitaph for Bill Gates: "This man performed an illegal operation and was shut down"
Ethan Benson <[EMAIL PROTECTED]> writes:
> --revision just sets an epoch, which is rather evil since it will
> think your package is newwer then ANY upgraded package unless the
> upgraded package has an epoch > yours.
The --revision flag in kernel-package only makes an epoch if you
explicitl
On Fri, 21 Apr 2000, Ethan Benson wrote:
> > I guess ultimately, what would be best, would be to keep track of the
> > sources that you have installed, so that you know when the sources
> > have been updated. Or have apt recompile for you.
>
> well i just don't understand why apt thinks it shou
On Sat, Apr 22, 2000 at 01:25:15AM -0500, Brad wrote:
> On Fri, Apr 21, 2000 at 08:27:52PM -0800, Ethan Benson wrote:
> >
> > > and if you want to compile them there's always 'apt-get --compile source
> > > packagename'. if you haven't used it before here's how it works :)
> >
> > with the annoyi
On Fri, Apr 21, 2000 at 08:27:52PM -0800, Ethan Benson wrote:
>
> > and if you want to compile them there's always 'apt-get --compile source
> > packagename'. if you haven't used it before here's how it works :)
>
> with the annoying side affect of apt insisting on replacing the
> locally compile
On Sat, Apr 22, 2000 at 02:02:35AM -0400, Marshal Kar-Cheung Wong wrote:
> > "Ethan" == Ethan Benson <[EMAIL PROTECTED]> writes:
>
> >> and if you want to compile them there's always 'apt-get
> >> --compile source packagename'. if you haven't used it before
> >> here's how it work
> "Ethan" == Ethan Benson <[EMAIL PROTECTED]> writes:
>> and if you want to compile them there's always 'apt-get
>> --compile source packagename'. if you haven't used it before
>> here's how it works :)
> with the annoying side affect of apt insisting on replacing the
> l
On Fri, Apr 21, 2000 at 12:29:30PM -0800, Adam Shand wrote:
> > If you're really hard core about security and encryption (and I'm going
> > to be heretical here, but hey, I have to plug my home), try OpenBSD.
> > Since it's main repository is in Canada, US crypto laws don't apply. I
> > played w
> "Adam" == Adam Shand <[EMAIL PROTECTED]> writes:
>> Probably not. Beside the crypto laws, there is also the DSFG
>> that debian adheres to, and many of the encryption schemes have
>> patents on them, thus makeing them non-free, and not in debian
>> by default.
> oh yeah
> Probably not. Beside the crypto laws, there is also the DSFG that
> debian adheres to, and many of the encryption schemes have patents on
> them, thus makeing them non-free, and not in debian by default.
oh yeah, i forgot about that ... still there are some that are patent
unencumbered aren't
On Thu, Apr 20, 2000 at 10:49:10PM -0400, Marshal Kar-Cheung Wong wrote:
> > "Adam" == Adam Shand <[EMAIL PROTECTED]> writes:
>
> > with the new mellowing of usa crypto laws, is there any chance
> > that the international kernel patch could be included in the
> > default debian ker
> "Adam" == Adam Shand <[EMAIL PROTECTED]> writes:
>> you have to get the international kernal patch from either
>> www.kerneli.org, or in the non-US section. Then you have to
>> patch the kernel and recompile.
> with the new mellowing of usa crypto laws, is there any chance
> you have to get the international kernal patch from either
> www.kerneli.org, or in the non-US section. Then you have to patch the
> kernel and recompile.
with the new mellowing of usa crypto laws, is there any chance that the
international kernel patch could be included in the default debian
> "Michael" == Michael O'Brien <[EMAIL PROTECTED]> writes:
> Hola~ Rookie question here. I'm trying to setup an encrypted
> filesystem as per:
>
> http://www.linuxdoc.org/HOWTO/Loopback-Encrypted-Filesystem-HOWTO-3.html
> The first step is installing the latest crypto pat
"Michael O'Brien" <[EMAIL PROTECTED]> writes:
> Rookie question here. I'm trying to setup an encrypted filesystem as per:
>
> http://www.linuxdoc.org/HOWTO/Loopback-Encrypted-Filesystem-HOWTO-3.html
>
> The first step is installing the latest crypto patch. How do I install the
> "latest crypt
28 matches
Mail list logo
