From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: cygwin@cygwin.com
Subject: Re: zip with encryption
Date: Sat, 21 Feb 2004 06:23:00 -0000 [thread overview]
Message-ID: <4036E874.9030708@cwilson.fastmail.fm> (raw)
In-Reply-To: <200402202134.i1KLYBcC022320@kafka.net.nih.gov>
bbuchbinder wrote:
> I was wondering if it might be possible to have zip 2.3 re-compiled
> with encryption and re-released. Chuck Wilson stated in
> http://www.cygwin.com/ml/cygwin-announce/2001/msg00005.html
> and
> http://www.cygwin.com/ml/cygwin-announce/2002-05/msg00018.html
> that it can be done but that first Red Hat needs to inform the U.S.
> government that binaries with encryption will be exported. I know
> that there are other ways to get encrypted zip files but it would
> be convenient if the official Cygwin zip would be encryption-enabled.
Also, I'm not sure what the implications are for our mirroring hosts.
Does the law require them to also notify the US govt, simply because
they mirror what sourceware's server provides? Surely the kernel
mirrors have dealt with this issue; perhaps only the "primary source"
needs to make the notification.
I don't know. I'm not a lawyer so I don't even WANT to know. But it's
Yet Another Thing RH's lawyers would have to look into, just for little
old me to include encryption code in cygwin's port of the zip package.
Not likely to happen -- especially with Red Hat's current legal issues
taking up all the lawyering time. SCO, XFree86 licensing GPL
incompatibilities, etc etc etc
--
Chuck
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2004-02-21 5:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-20 22:15 bbuchbinder
2004-02-20 22:20 ` Christopher Faylor
2004-02-21 6:23 ` Charles Wilson [this message]
2004-02-23 16:43 Buchbinder, Barry (NIH/NIAID)
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=4036E874.9030708@cwilson.fastmail.fm \
--to=cygwin@cwilson.fastmail.fm \
--cc=cygwin@cygwin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).