Re: USA crypto rules and libssl-dependent packages

2001-05-11 Thread Jimmy Kaplowitz
On Fri, May 11, 2001 at 09:53:04PM -0400, [EMAIL PROTECTED] wrote: > > I'm not sure that that matters. The BXA refers to "Open Cryptographic > Interfaces". My understanding was that any software which contained hooks > to call other software which actually performed encryption was regulated > as

Re: USA crypto rules and libssl-dependent packages

2001-05-11 Thread Jimmy Kaplowitz
On Fri, May 11, 2001 at 09:03:48PM -0400, Brian Ristuccia wrote: > > > > > > > > > > 2) Do the binary .debs go in non-US? > > > > > > Yes. Policy currently requires it. > > > > OK, I understand that this is a quirk of Debian policy, and not US law. > > > > It wouldn't make sense for .deb's t

Re: USA crypto rules and libssl-dependent packages

2001-05-11 Thread sharkey
> Really? I am not doing any static linking with libssl, only dynamic, so I > don't believe that I am including any crypto. I'm not sure that that matters. The BXA refers to "Open Cryptographic Interfaces". My understanding was that any software which contained hooks to call other software which

Re: USA crypto rules and libssl-dependent packages

2001-05-11 Thread Brian Ristuccia
On Fri, May 11, 2001 at 08:28:12PM -0400, Jimmy Kaplowitz wrote: > > > > > > > 2) Do the binary .debs go in non-US? > > > > Yes. Policy currently requires it. > > OK, I understand that this is a quirk of Debian policy, and not US law. > It wouldn't make sense for .deb's to go in a place diff

Re: USA crypto rules and libssl-dependent packages

2001-05-11 Thread Jimmy Kaplowitz
On Fri, May 11, 2001 at 01:51:54AM -0400, Brian Ristuccia wrote: > > > > 1) I live in the US. Therefore, do I have to send a BXA notification to the > > government (I believe license exception TSU is applicable - correct me if > > I'm > > wrong)? > > You may. Since it's easy, you probablys hould

Re: lame (again!)

2001-05-11 Thread James Troup
Brian Ristuccia <[EMAIL PROTECTED]> writes: > On Fri, May 11, 2001 at 10:14:22PM +0200, Marcelo E. Magallon wrote: > > >> Viral <[EMAIL PROTECTED]> writes: > > > > > I would like clarify the reason for lame not being included in the debian > > > archives, not even non-US. > > > > http://www.d

Re: lame (again!)

2001-05-11 Thread Brian Ristuccia
On Fri, May 11, 2001 at 10:14:22PM +0200, Marcelo E. Magallon wrote: > >> Viral <[EMAIL PROTECTED]> writes: > > > I would like clarify the reason for lame not being included in the debian > > archives, not even non-US. > > http://www.debian.org/devel/wnpp/unable-to-package > > IIRC your ques

Re: lame (again!)

2001-05-11 Thread Marcelo E. Magallon
>> Viral <[EMAIL PROTECTED]> writes: > I would like clarify the reason for lame not being included in the debian > archives, not even non-US. http://www.debian.org/devel/wnpp/unable-to-package IIRC your questions are addressed there. -- Marcelo | Mustrum Ridcully did a lot for

lame (again!)

2001-05-11 Thread Viral
Hi all, I would like clarify the reason for lame not being included in the debian archives, not even non-US. Firstly, the lame license is LGPL as of version 3.88. The psycho-acoustic model used in LAME is also GPLed (or LGPLed). I believe its not the same as the one patented by the Fraunhofer I

Re: USA crypto rules and libssl-dependent packages

2001-05-11 Thread Brian Ristuccia
On Thu, May 10, 2001 at 07:27:44PM -0400, Jimmy Kaplowitz wrote: > Hi. I am a novice Debian package maintainer, in the queue for becoming an > official developer. I am maintaining a package called althea, which is an > IMAP email client for GTK+. They have recently added support for SSL through > l