Re: crypto patch (OT: ports tree)

2000-11-14 Thread H.C.Hsiang
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

Re: crypto patch (OT: ports tree)

2000-11-14 Thread H.C.Hsiang
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

RE: crypto patch

2000-04-23 Thread Andrew Weiss
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"

Re: Apt wishlist WAS: Re: crypto patch (OT: ports tree)

2000-04-22 Thread Robert D. Hilliard
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

Re: Apt wishlist WAS: Re: crypto patch (OT: ports tree)

2000-04-22 Thread Jason Gunthorpe
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

Re: crypto patch (OT: ports tree)

2000-04-22 Thread Ethan Benson
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

Re: crypto patch (OT: ports tree)

2000-04-22 Thread Brad
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

Re: Apt wishlist WAS: Re: crypto patch (OT: ports tree)

2000-04-22 Thread Ethan Benson
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

Apt wishlist WAS: Re: crypto patch (OT: ports tree)

2000-04-22 Thread Marshal Kar-Cheung Wong
> "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

Re: crypto patch (OT: ports tree)

2000-04-22 Thread Ethan Benson
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

Re: crypto patch

2000-04-21 Thread Marshal Kar-Cheung Wong
> "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

Re: crypto patch

2000-04-21 Thread Adam Shand
> 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

Re: crypto patch

2000-04-21 Thread Brad
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

Re: crypto patch

2000-04-21 Thread Marshal Kar-Cheung Wong
> "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

Re: crypto patch

2000-04-21 Thread Adam Shand
> 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

Re: crypto patch

2000-04-20 Thread Marshal Kar-Cheung Wong
> "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

Re: crypto patch

2000-04-20 Thread Gary Hennigan
"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