You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@jakarta.apache.org by Jason van Zyl <jv...@zenplex.com> on 2001/10/23 19:40:53 UTC
Distributing the JSSE
Hi,
I want to distribute the JSSE jars with the Turbine Development Kit but I'm
not entirely sure if it's legal. On the JSSE website it says that "the
binary implementation may be used royalty-free as part of commercial
applications", but in the license it says for internal use only?
Here's the lic:
http://java.sun.com/products/jsse/LICENSE.txt
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Distributing the JSSE
Posted by Kasper Nielsen <ne...@kav.dk>.
----- Original Message -----
From: "Jason van Zyl" <jv...@zenplex.com>
To: <ge...@jakarta.apache.org>
Sent: Tuesday, October 23, 2001 11:55 PM
Subject: Re: Distributing the JSSE
> On 10/23/01 2:38 PM, "Jon Stevens" <jo...@latchkey.com> wrote:
>
> > on 10/23/01 10:40 AM, "Jason van Zyl" <jv...@zenplex.com> wrote:
> >
> >> I want to distribute the JSSE jars with the Turbine Development Kit but
I'm
> >> not entirely sure if it's legal. On the JSSE website it says that "the
> >> binary implementation may be used royalty-free as part of commercial
> >> applications", but in the license it says for internal use only?
> >
> > It is not legal.
>
> If that is indeed the case does anyone know of any JSSE implementations
that
> can be distributed?
>
I seriously doubt anybody would waste time on creating another
implementation of JSSE, when the reference implementation is freely
available (with source code) and is included in future versions of java.
- Kasper
- Kasper
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
RE: Distributing the JSSE
Posted by Kief Morris <km...@bitbull.com>.
Ylan Segal typed the following on 09:47 AM 10/26/2001 -0600
>>
>> so this is an US export law issue and not a Sun License issue?
>>
>I was under the impression that the US had lifted some of the export issues
>in regards to crypto. For example, in the past, browsers (like IE or
>Netscape) downloaded from outside the US (I live in Mexico) had only 40bit
>encryption. I could not access 128bit sites in the US with my browsers.
>About a year ago (if I am not mistaken) that changed and now I can use
>128bit sites jus fine.
>
>Just my $0.02
AFAIK (IANAL) they still require a lot of paperwork to get approval to
export serious encryption. Netscape and Microsoft can afford to have
lawyers sort all that out for them. Also, it wouldn't be too surprising if
our fine representatives in Congress decided they could get some attention
by increasing restrictions on encryption, so that law abiding terrorists
won't use it.
So, anybody living in a country with liberal crypto-laws want to write
a JSSE clone?
Kief
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Distributing the JSSE
Posted by Peter Donald <do...@apache.org>.
On Sat, 3 Nov 2001 01:30, Guillaume Rousse wrote:
> Sofar no one answered this mail... Does US crytopgraphy export restrictions
> apply to both version of JSSE, or only to domestic version ? And do these
> restictions apply everywhere, or only for US-based download location ?
the restrictions apply if the distributor is US based or site is in US. In
your case I assume sourceforge is US based so unless you have all the proper
paperwork I doubt they will be able to distribute - even on non-US mirrors.
--
Cheers,
Pete
-------------------------------------------------
We should take care not to make the intellect our
god; it has, of course, powerful muscles, but no
personality.
-------------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Distributing the JSSE
Posted by Berin Loritsch <bl...@apache.org>.
Guillaume Rousse wrote:
>
> Ainsi parlait Kasper Nielsen :
> > > > so this is an US export law issue and not a Sun License issue?
> > >
> > > I think so. It would be possible to distribute it but it would take a lot
> >
> > of
> >
> > > work to get all paper work done and I think there was other conditions
> > > (ie must be us citizen, must get the connections from embargoed countries
> >
> > blocked
> >
> > > etc)
> >
> > thats strange on http://java.sun.com/products/jsse/index-102.html they have
> > a link to
> >
> > Download JSSE 1.0.2 global software and documentation with support for
> > strong encryption.
> >
> > and a Download JSSE 1.0.2 domestic (US/Canada) software and documentation
> > with support for strong encryption
> >
> > Don't know what the difference is, but I would imagine its legal to
> > distribute something that is allready allowed to be globally distributed?
> Sofar no one answered this mail... Does US crytopgraphy export restrictions
> apply to both version of JSSE, or only to domestic version ? And do these
> restictions apply everywhere, or only for US-based download location ?
The latest version of JSSE complies with US restrictions for most countries.
However, US export law forbids ANY type of encryption to certain countries
(mostly known for supporting or allowing terrorist activity).
> Said otherwise, can jpackage project (jpackage.sourceforge.net) provide JSSE
> global version packages, as any other Sun java API packages, eventually only
> on non-US mirrors, or is it a special case ?
It is a special case, as certain countries are not allowed to get ANY type
of US encryption technologies.
> --
> Guillaume Rousse <ro...@ccr.jussieu.fr>
> GPG key http://lis.snv.jussieu.fr/~rousse/gpgkey.html
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
"Those who would trade liberty for
temporary security deserve neither"
- Benjamin Franklin
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Distributing the JSSE
Posted by "Craig R. McClanahan" <cr...@apache.org>.
On Fri, 2 Nov 2001, Guillaume Rousse wrote:
> Date: Fri, 2 Nov 2001 15:30:56 +0100
> From: Guillaume Rousse <ro...@ccr.jussieu.fr>
> Reply-To: Jakarta General List <ge...@jakarta.apache.org>
> To: general@jakarta.apache.org
> Cc: jpackage-devel@lists.sourceforge.net
> Subject: Re: Distributing the JSSE
>
> Ainsi parlait Kasper Nielsen :
> > > > so this is an US export law issue and not a Sun License issue?
> > >
> > > I think so. It would be possible to distribute it but it would take a lot
> >
> > of
> >
> > > work to get all paper work done and I think there was other conditions
> > > (ie must be us citizen, must get the connections from embargoed countries
> >
> > blocked
> >
> > > etc)
> >
> > thats strange on http://java.sun.com/products/jsse/index-102.html they have
> > a link to
> >
> > Download JSSE 1.0.2 global software and documentation with support for
> > strong encryption.
> >
> > and a Download JSSE 1.0.2 domestic (US/Canada) software and documentation
> > with support for strong encryption
> >
> > Don't know what the difference is, but I would imagine its legal to
> > distribute something that is allready allowed to be globally distributed?
> Sofar no one answered this mail... Does US crytopgraphy export restrictions
> apply to both version of JSSE, or only to domestic version ? And do these
> restictions apply everywhere, or only for US-based download location ?
>
> Said otherwise, can jpackage project (jpackage.sourceforge.net) provide JSSE
> global version packages, as any other Sun java API packages, eventually only
> on non-US mirrors, or is it a special case ?
Crypto is different because of US export laws. The Sun redistribution
licenses for JSSE have the same basic terms as the redistribution licenses
for the other Java APIs (see the license you had to click through to
download it for details.)
> --
> Guillaume Rousse <ro...@ccr.jussieu.fr>
> GPG key http://lis.snv.jussieu.fr/~rousse/gpgkey.html
>
Craig
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Distributing the JSSE
Posted by Guillaume Rousse <ro...@ccr.jussieu.fr>.
Ainsi parlait Kasper Nielsen :
> > > so this is an US export law issue and not a Sun License issue?
> >
> > I think so. It would be possible to distribute it but it would take a lot
>
> of
>
> > work to get all paper work done and I think there was other conditions
> > (ie must be us citizen, must get the connections from embargoed countries
>
> blocked
>
> > etc)
>
> thats strange on http://java.sun.com/products/jsse/index-102.html they have
> a link to
>
> Download JSSE 1.0.2 global software and documentation with support for
> strong encryption.
>
> and a Download JSSE 1.0.2 domestic (US/Canada) software and documentation
> with support for strong encryption
>
> Don't know what the difference is, but I would imagine its legal to
> distribute something that is allready allowed to be globally distributed?
Sofar no one answered this mail... Does US crytopgraphy export restrictions
apply to both version of JSSE, or only to domestic version ? And do these
restictions apply everywhere, or only for US-based download location ?
Said otherwise, can jpackage project (jpackage.sourceforge.net) provide JSSE
global version packages, as any other Sun java API packages, eventually only
on non-US mirrors, or is it a special case ?
--
Guillaume Rousse <ro...@ccr.jussieu.fr>
GPG key http://lis.snv.jussieu.fr/~rousse/gpgkey.html
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Distributing the JSSE
Posted by Kasper Nielsen <ne...@kav.dk>.
----- Original Message -----
From: "Peter Donald" <do...@apache.org>
To: <ge...@jakarta.apache.org>
Sent: Friday, October 26, 2001 8:21 AM
Subject: Re: Distributing the JSSE
> >
> > so this is an US export law issue and not a Sun License issue?
>
> I think so. It would be possible to distribute it but it would take a lot
of
> work to get all paper work done and I think there was other conditions (ie
> must be us citizen, must get the connections from embargoed countries
blocked
> etc)
>
thats strange on http://java.sun.com/products/jsse/index-102.html they have
a link to
Download JSSE 1.0.2 global software and documentation with support for
strong encryption.
and a Download JSSE 1.0.2 domestic (US/Canada) software and documentation
with support for strong encryption
Don't know what the difference is, but I would imagine its legal to
distribute something that is allready allowed to be globally distributed?
- Kasper
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Distributing the JSSE
Posted by "Craig R. McClanahan" <cr...@apache.org>.
On Fri, 26 Oct 2001, Peter Donald wrote:
> Date: Fri, 26 Oct 2001 16:21:46 +1000
> From: Peter Donald <do...@apache.org>
> Reply-To: general@jakarta.apache.org
> To: general@jakarta.apache.org
> Subject: Re: Distributing the JSSE
>
> On Fri, 26 Oct 2001 02:16, Kasper Nielsen wrote:
> > > Because the amount of paperwork needed to legally distribute it is
> > > huuuuuuuuge. The US export laws do allow non-profits and indviduals to
> > > distribute crypto things but they have to jump through a few hoops and
> >
> > make
> >
> > > sure they fill out oodles of stuff.
> > >
> > > Avalon was going to distribute it until Craig dropped a note on commons
> > > or ant list regarding this and gave a link. I followed it and it was much
> > > too much work to get it done legally so we dropped it. Craig do you still
> > > have that link ?
> >
I cannot find the original link that I forwarded, but got it off the JSSE
web site. It had to do with the still-existing registration requirements
for people who want to export crypto software.
> > so this is an US export law issue and not a Sun License issue?
>
> I think so. It would be possible to distribute it but it would take a lot of
> work to get all paper work done and I think there was other conditions (ie
> must be us citizen, must get the connections from embargoed countries blocked
> etc)
>
Yep.
> --
> Cheers,
>
> Pete
>
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Distributing the JSSE
Posted by Peter Donald <do...@apache.org>.
On Fri, 26 Oct 2001 02:16, Kasper Nielsen wrote:
> > Because the amount of paperwork needed to legally distribute it is
> > huuuuuuuuge. The US export laws do allow non-profits and indviduals to
> > distribute crypto things but they have to jump through a few hoops and
>
> make
>
> > sure they fill out oodles of stuff.
> >
> > Avalon was going to distribute it until Craig dropped a note on commons
> > or ant list regarding this and gave a link. I followed it and it was much
> > too much work to get it done legally so we dropped it. Craig do you still
> > have that link ?
>
> so this is an US export law issue and not a Sun License issue?
I think so. It would be possible to distribute it but it would take a lot of
work to get all paper work done and I think there was other conditions (ie
must be us citizen, must get the connections from embargoed countries blocked
etc)
--
Cheers,
Pete
---------------------------------------------------
"Therefore it can be said that victorious warriors
win first, and then go to battle, while defeated
warriors go to battle first, and then seek to win."
- Sun Tzu, the Art Of War
---------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Distributing the JSSE
Posted by Pier Fumagalli <pi...@betaversion.org>.
Kasper Nielsen at news@kav.dk wrote:
>
> so this is an US export law issue and not a Sun License issue?
AFAIK (in theory, but I'm not a lawyer), it is...
Pier
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Site update
Posted by Peter Donald <do...@apache.org>.
On Mon, 29 Oct 2001 13:30, martin.cooper@tumbleweed.com wrote:
> One reason I can think of is that you then run the risk of someone editing
> the HTML pages directly, and checking in those changes. The next time
> someone else comes along and makes changes the proper way, by editing the
> XML and not the HTML, they will blow away the previous changes to the HTML
> when the generated files are checked in. If only the XML files are checked
> in, then there is no danger that someone will check in changes to the
> generated files.
>
> In my opinion, anything that is automatically generated should not be
> checked in. However, this seems to be one of those issues where people have
> to agree to differ, because neither "side" will ever convince the other
> that their way is better. ;-)
Well currently I am on the side of check generated stuff in. I would like to
be on the other side and would quite happily swap if someone was to put an
automated system together to do it (say gump?).
Fundamentally I am lazy and checking things into CVS is easier and less time
consuming. You want to fix it - go ahead - I will welcome that as long as it
doesn't make me do any more work ;)
--
Cheers,
Pete
-------------------------------------------------------------
| Egoism is the drug that soothes the pain of stupidity. |
-------------------------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Site update
Posted by ma...@tumbleweed.com.
One reason I can think of is that you then run the risk of someone editing
the HTML pages directly, and checking in those changes. The next time
someone else comes along and makes changes the proper way, by editing the
XML and not the HTML, they will blow away the previous changes to the HTML
when the generated files are checked in. If only the XML files are checked
in, then there is no danger that someone will check in changes to the
generated files.
In my opinion, anything that is automatically generated should not be
checked in. However, this seems to be one of those issues where people have
to agree to differ, because neither "side" will ever convince the other that
their way is better. ;-)
--
Martin Cooper
----- Original Message -----
From: "Matt Egyhazy" <mw...@virginia.edu>
To: "Jakarta General List" <ge...@jakarta.apache.org>
Sent: Sunday, October 28, 2001 6:03 PM
Subject: Re: Site update
> i cant think of a good reason why html pages should not be in cvs (in
> general).
>
> matt
> ----- Original Message -----
> From: "Jon Stevens" <jo...@latchkey.com>
> To: <ge...@jakarta.apache.org>
> Sent: Sunday, October 28, 2001 4:26 PM
> Subject: Re: Site update
>
>
> > on 10/27/01 12:27 PM, "Remy Maucherat" <rm...@home.com> wrote:
> >
> > > Hi,
> > >
> > > When doing site updates, please don't forget to update before starting
> > > editing. For example, Berin reverted many changes to the news and
binary
> > > pages.
> > >
> > > Remy
> >
> > Even though it was partially the fault of CVS that f*cked up in this
case,
> I
> > do argue that this is a perfect example of why I push for keeping the
> .html
> > pages in CVS.
> >
> > -jon
> >
> >
> > --
> > To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> > For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Site update
Posted by Matt Egyhazy <mw...@virginia.edu>.
i cant think of a good reason why html pages should not be in cvs (in
general).
matt
----- Original Message -----
From: "Jon Stevens" <jo...@latchkey.com>
To: <ge...@jakarta.apache.org>
Sent: Sunday, October 28, 2001 4:26 PM
Subject: Re: Site update
> on 10/27/01 12:27 PM, "Remy Maucherat" <rm...@home.com> wrote:
>
> > Hi,
> >
> > When doing site updates, please don't forget to update before starting
> > editing. For example, Berin reverted many changes to the news and binary
> > pages.
> >
> > Remy
>
> Even though it was partially the fault of CVS that f*cked up in this case,
I
> do argue that this is a perfect example of why I push for keeping the
.html
> pages in CVS.
>
> -jon
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Site update
Posted by Remy Maucherat <rm...@home.com>.
> on 10/27/01 12:27 PM, "Remy Maucherat" <rm...@home.com> wrote:
>
> > Hi,
> >
> > When doing site updates, please don't forget to update before starting
> > editing. For example, Berin reverted many changes to the news and binary
> > pages.
> >
> > Remy
>
> Even though it was partially the fault of CVS that f*cked up in this case,
I
> do argue that this is a perfect example of why I push for keeping the
.html
> pages in CVS.
In that case, both the generated HTMLs and XMLs sources were reverted to
prior revisions, so it wouldn't have helped in any way.
Remy
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Site update
Posted by Jon Stevens <jo...@latchkey.com>.
on 10/27/01 12:27 PM, "Remy Maucherat" <rm...@home.com> wrote:
> Hi,
>
> When doing site updates, please don't forget to update before starting
> editing. For example, Berin reverted many changes to the news and binary
> pages.
>
> Remy
Even though it was partially the fault of CVS that f*cked up in this case, I
do argue that this is a perfect example of why I push for keeping the .html
pages in CVS.
-jon
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Site update
Posted by Remy Maucherat <rm...@home.com>.
> On 10/27/01 4:27 PM, "Remy Maucherat" <rm...@home.com> wrote:
>
> > Hi,
> >
> > When doing site updates, please don't forget to update before starting
> > editing. For example, Berin reverted many changes to the news and binary
> > pages.
> >
>
> Shouldn't the cvs commit caught that on the merge?
Somehow, it didn't.
You can see the diff between 1.93 and 1.94 of the binary index page:
RCS file: /home/cvs/jakarta-site2/xdocs/site/binindex.xml,v
retrieving revision 1.93
retrieving revision 1.94
diff -r1.93 -r1.94
73,75c73,76
< <li><a
href="http://www.apache.org/dist/jakarta/jakarta-ant/release/v1.4.1/bin/">An
t 1.4.1</a></li>
< <li><a
href="http://www.apache.org/dist/jakarta/jakarta-avalon/release/framework/v4
.0">Avalon Framework 4.0</a></li>
< <li><a
href="http://www.apache.org/dist/jakarta/jakarta-avalon/release/excalibur/v4
.0">Avalon Excalibur 4.0</a></li>
---
> <li><a
href="http://www.apache.org/dist/jakarta/jakarta-ant/release/v1.4/bin/">Ant
1.4</a></li>
> <li><a
href="http://www.apache.org/dist/jakarta/jakarta-avalon/release/framework/v4
.0/">Avalon Framework 4.0</a></li>
> <li><a
href="http://www.apache.org/dist/jakarta/jakarta-avalon/release/excalibur/v4
.0/">Avalon Excalibur 4.0</a></li>
> <li><a
href="http://www.apache.org/dist/jakarta/jakarta-avalon/release/logkit/v1.0/
">Avalon LogKit 1.0</a></li>
87,88c88
< <li><a
href="http://www.apache.org/dist/jakarta/jakarta-tomcat/release/v3.3/bin/">T
omcat 3.3</a></li>
< <li><a
href="http://www.apache.org/dist/jakarta/jakarta-tomcat-4.0/release/v4.0.1/"
>Tomcat 4.0.1</a></li>
---
> <li><a
href="http://www.apache.org/dist/jakarta/jakarta-tomcat-4.0/release/v4.0/">T
omcat 4.0</a></li>
98c98
< <li><a
href="http://www.apache.org/dist/jakarta/jakarta-avalon/release/logkit/lates
t/">Avalon LogKit 1.0 beta 5</a></li>
---
> <li><a
href="http://www.apache.org/dist/jakarta/jakarta-ant/release/v1.4.1b1/">Ant
1.4.1 beta 1</a></li>
100,101c100,102
< <li><a
href="http://www.apache.org/dist/jakarta/jakarta-lucene/release/v1.2-rc2/">L
ucene 1.2 Release Candidate 2</a></li>
< <li><a
href="http://www.apache.org/dist/jakarta/jakarta-slide/release/1.0/">Slide
1.0.15 Beta</a></li>
---
> <li><a
href="http://www.apache.org/dist/jakarta/jakarta-lucene/release/v1.2-rc1/">L
ucene 1.2 Release Candidate 1</a></li>
> <li><a
href="http://www.apache.org/dist/jakarta/jakarta-tomcat/release/v3.3-rc1/bin
/">Tomcat 3.3
> Release Candidate 1</a></li>
118d118
< <li><a
href="http://www.apache.org/dist/jakarta/jakarta-slide/nightly/">Slide</a></
li>
So the affected links include Tomcat, Ant, Slide, Lucene.
Same happened to the news page.
Remy
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Site update
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On 10/27/01 4:27 PM, "Remy Maucherat" <rm...@home.com> wrote:
> Hi,
>
> When doing site updates, please don't forget to update before starting
> editing. For example, Berin reverted many changes to the news and binary
> pages.
>
Shouldn't the cvs commit caught that on the merge?
--
Geir Magnusson Jr. geirm@optonline.net
System and Software Consulting
"Whoever would overthrow the liberty of a nation must begin by subduing the
freeness of speech." - Benjamin Franklin
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Site update
Posted by Remy Maucherat <rm...@home.com>.
Hi,
When doing site updates, please don't forget to update before starting
editing. For example, Berin reverted many changes to the news and binary
pages.
Remy
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
nntp server for jakarta newsgroups
Posted by Jakarta <ja...@dyxn.net>.
hi all,
"fools rush in where angels fear to tread"
but,
"we believe in eating our own dogfood"
i set up james to serve newsgroups for jakarta.
try it if you like. i'm open to any and all recommendations for changes.
my personal email is my first name at this domain.
the server will be available from now onwards.
news.dyxn.net or 208.191.61.107
thanks,
rhys dixon
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
RE: Distributing the JSSE
Posted by Ylan Segal <yl...@digiworks.tv>.
>
> so this is an US export law issue and not a Sun License issue?
>
I was under the impression that the US had lifted some of the export issues
in regards to crypto. For example, in the past, browsers (like IE or
Netscape) downloaded from outside the US (I live in Mexico) had only 40bit
encryption. I could not access 128bit sites in the US with my browsers.
About a year ago (if I am not mistaken) that changed and now I can use
128bit sites jus fine.
Just my $0.02
Ylan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Distributing the JSSE
Posted by Kasper Nielsen <ne...@kav.dk>.
----- Original Message -----
From: "Peter Donald" <do...@apache.org>
To: <ge...@jakarta.apache.org>
Sent: Thursday, October 25, 2001 2:48 AM
Subject: Re: Distributing the JSSE
> On Thu, 25 Oct 2001 01:45, Jon Stevens wrote:
> > Catalina does not distribute the JSSE (from the catalina/build.xml):
> >
> > <target name="copy-jsse.jar" if="copy.jsse.jar">
> > <!-- Cannot redistribute JSSE
> > <copy todir="${catalina.build}/common/lib" file="${jcert.jar}"/>
> > <copy todir="${catalina.build}/common/lib" file="${jnet.jar}"/>
> > <copy todir="${catalina.build}/common/lib" file="${jsse.jar}"/>
> > -->
> > </target>
> >
> > I would like to know why they don't redistribute it.
>
> Because the amount of paperwork needed to legally distribute it is
> huuuuuuuuge. The US export laws do allow non-profits and indviduals to
> distribute crypto things but they have to jump through a few hoops and
make
> sure they fill out oodles of stuff.
>
> Avalon was going to distribute it until Craig dropped a note on commons or
> ant list regarding this and gave a link. I followed it and it was much too
> much work to get it done legally so we dropped it. Craig do you still have
> that link ?
so this is an US export law issue and not a Sun License issue?
-.Kasper
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Distributing the JSSE
Posted by Peter Donald <do...@apache.org>.
On Thu, 25 Oct 2001 01:45, Jon Stevens wrote:
> Catalina does not distribute the JSSE (from the catalina/build.xml):
>
> <target name="copy-jsse.jar" if="copy.jsse.jar">
> <!-- Cannot redistribute JSSE
> <copy todir="${catalina.build}/common/lib" file="${jcert.jar}"/>
> <copy todir="${catalina.build}/common/lib" file="${jnet.jar}"/>
> <copy todir="${catalina.build}/common/lib" file="${jsse.jar}"/>
> -->
> </target>
>
> I would like to know why they don't redistribute it.
Because the amount of paperwork needed to legally distribute it is
huuuuuuuuge. The US export laws do allow non-profits and indviduals to
distribute crypto things but they have to jump through a few hoops and make
sure they fill out oodles of stuff.
Avalon was going to distribute it until Craig dropped a note on commons or
ant list regarding this and gave a link. I followed it and it was much too
much work to get it done legally so we dropped it. Craig do you still have
that link ?
> I think (ii) is funny because from what I'm hearing is that Jboss has
> modified it and is distributing it because there is a serious classloader
> problem in it.
And we all know how JBoss only does things that are legal .... right ?
--
Cheers,
Pete
--------------------------------------------------
The fact that nobody understands you doesn't
mean you're an artist.
--------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Distributing the JSSE
Posted by Pier Fumagalli <pi...@betaversion.org>.
Jon Stevens at jon@latchkey.com wrote:
> Catalina does not distribute the JSSE (from the catalina/build.xml):
>
> <target name="copy-jsse.jar" if="copy.jsse.jar">
> <!-- Cannot redistribute JSSE
> <copy todir="${catalina.build}/common/lib" file="${jcert.jar}"/>
> <copy todir="${catalina.build}/common/lib" file="${jnet.jar}"/>
> <copy todir="${catalina.build}/common/lib" file="${jsse.jar}"/>
> -->
> </target>
>
> I would like to know why they don't redistribute it.
Export regulation, I believe... When you add that to (iv), we should
definitely check the originating IP address, and make sure we're not
exporting crypto stuff in places where we shouldn't... I believe that
regarding cryptographic software there are still a lot of hurdles to clear.
(I believe we don't even redistribute OpenSSL together with Apache 2.0, even
though it's required to build the SSL module in it).
Pier
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Distributing the JSSE
Posted by Jon Stevens <jo...@latchkey.com>.
on 10/23/01 7:38 PM, "Geir Magnusson Jr." <ge...@optonline.net> wrote:
> On 10/23/01 5:55 PM, "Jason van Zyl" <jv...@zenplex.com> wrote:
>
>> On 10/23/01 2:38 PM, "Jon Stevens" <jo...@latchkey.com> wrote:
>>
>>> on 10/23/01 10:40 AM, "Jason van Zyl" <jv...@zenplex.com> wrote:
>>>
>>>> I want to distribute the JSSE jars with the Turbine Development Kit but I'm
>>>> not entirely sure if it's legal. On the JSSE website it says that "the
>>>> binary implementation may be used royalty-free as part of commercial
>>>> applications", but in the license it says for internal use only?
>>>
>>> It is not legal.
>>
>> If that is indeed the case does anyone know of any JSSE implementations that
>> can be distributed?
>>
>
>
> Why is it not legal? According to the license posted by jason, there is a
> supplemental section that reads :
>
> SUPPLEMENTAL LICENSE TERMS
>
> These supplemental license terms ("Supplement") add to or
> modify the terms of the Binary Code License Agreement
> (collectively, the "Agreement"). Capitalized terms not
> defined in this Supplement shall have the same meanings
> ascribed to them in the Agreement. These Supplement terms
> shall supersede any inconsistent or conflicting terms in
> the Agreement, or in any license contained within the
> Software.
>
> 1. License to Distribute. Sun grants you a non-exclusive,
> non-transferable, royalty-free, limited license to (a) use
> the binary form of the Software for the sole purpose of
> designing, developing and testing your JavaTM applets and
> applications intended to run on a compatible Java
> environment (the "Programs"), provided that the Programs
> add significant and primary functionality to the Software,
> and (b) reproduce and distribute the binary form of the
> Software through multiple tiers of distribution provided
> that you: (i) distribute the Software complete and
> unmodified; (ii) do not distribute additional software
> intended to supersede any component(s) of the Software;
> (iii) do not remove or alter any proprietary
> legends or notices contained in or on the Software; and
> (iv) only distribute the Software pursuant to a license
> agreement that protects Sun's interests consistent with the
> terms contained in this Agreement, and provides that Sun is
> a third party beneficiary to such license agreement. If you
> distribute the Software pursuant to this paragraph, you
> must include the following statement as part of product
> documentation (whether hard copy or electronic), as a
> part of a copyright page or proprietary rights notice
> page, in an "About" box or in any other form reasonably
> designed to make the statement visible to users of the
> Software: "This product includes code licensed from
> RSA Data Security".
>
> The only problem that I see is (iv). Is that it?
>
Catalina does not distribute the JSSE (from the catalina/build.xml):
<target name="copy-jsse.jar" if="copy.jsse.jar">
<!-- Cannot redistribute JSSE
<copy todir="${catalina.build}/common/lib" file="${jcert.jar}"/>
<copy todir="${catalina.build}/common/lib" file="${jnet.jar}"/>
<copy todir="${catalina.build}/common/lib" file="${jsse.jar}"/>
-->
</target>
I would like to know why they don't redistribute it.
I think (ii) is funny because from what I'm hearing is that Jboss has
modified it and is distributing it because there is a serious classloader
problem in it.
(iv) definitely doesn't make me feel real comfortable.
-jon
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Distributing the JSSE
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On 10/23/01 5:55 PM, "Jason van Zyl" <jv...@zenplex.com> wrote:
> On 10/23/01 2:38 PM, "Jon Stevens" <jo...@latchkey.com> wrote:
>
>> on 10/23/01 10:40 AM, "Jason van Zyl" <jv...@zenplex.com> wrote:
>>
>>> I want to distribute the JSSE jars with the Turbine Development Kit but I'm
>>> not entirely sure if it's legal. On the JSSE website it says that "the
>>> binary implementation may be used royalty-free as part of commercial
>>> applications", but in the license it says for internal use only?
>>
>> It is not legal.
>
> If that is indeed the case does anyone know of any JSSE implementations that
> can be distributed?
>
Why is it not legal? According to the license posted by jason, there is a
supplemental section that reads :
SUPPLEMENTAL LICENSE TERMS
These supplemental license terms ("Supplement") add to or
modify the terms of the Binary Code License Agreement
(collectively, the "Agreement"). Capitalized terms not
defined in this Supplement shall have the same meanings
ascribed to them in the Agreement. These Supplement terms
shall supersede any inconsistent or conflicting terms in
the Agreement, or in any license contained within the
Software.
1. License to Distribute. Sun grants you a non-exclusive,
non-transferable, royalty-free, limited license to (a) use
the binary form of the Software for the sole purpose of
designing, developing and testing your JavaTM applets and
applications intended to run on a compatible Java
environment (the "Programs"), provided that the Programs
add significant and primary functionality to the Software,
and (b) reproduce and distribute the binary form of the
Software through multiple tiers of distribution provided
that you: (i) distribute the Software complete and
unmodified; (ii) do not distribute additional software
intended to supersede any component(s) of the Software;
(iii) do not remove or alter any proprietary
legends or notices contained in or on the Software; and
(iv) only distribute the Software pursuant to a license
agreement that protects Sun's interests consistent with the
terms contained in this Agreement, and provides that Sun is
a third party beneficiary to such license agreement. If you
distribute the Software pursuant to this paragraph, you
must include the following statement as part of product
documentation (whether hard copy or electronic), as a
part of a copyright page or proprietary rights notice
page, in an "About" box or in any other form reasonably
designed to make the statement visible to users of the
Software: "This product includes code licensed from
RSA Data Security".
The only problem that I see is (iv). Is that it?
--
Geir Magnusson Jr. geirm@optonline.net
System and Software Consulting
"Whoever would overthrow the liberty of a nation must begin by subduing the
freeness of speech." - Benjamin Franklin
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Distributing the JSSE
Posted by Jason van Zyl <jv...@zenplex.com>.
On 10/23/01 2:38 PM, "Jon Stevens" <jo...@latchkey.com> wrote:
> on 10/23/01 10:40 AM, "Jason van Zyl" <jv...@zenplex.com> wrote:
>
>> I want to distribute the JSSE jars with the Turbine Development Kit but I'm
>> not entirely sure if it's legal. On the JSSE website it says that "the
>> binary implementation may be used royalty-free as part of commercial
>> applications", but in the license it says for internal use only?
>
> It is not legal.
If that is indeed the case does anyone know of any JSSE implementations that
can be distributed?
> -jon
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Mailing lists problem...
Posted by Pier Fumagalli <pi...@betaversion.org>.
Paulo Gaspar at paulo.gaspar@krankikom.de wrote:
> I am receiving no mail from any Apache mailling list for a couple of days.
> I am also getting no answer from the mailling list management robot.
>
> Do you know what is happening?
Daedalus is backlogged... We're moving *@jakarta.apache.org on a new
server... Should be solved shortly (right now tomcat-dev and tomcat0user are
already there)
Pier
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Mailing lists problem...
Posted by Paulo Gaspar <pa...@krankikom.de>.
I am receiving no mail from any Apache mailling list for a couple of days.
I am also getting no answer from the mailling list management robot.
Do you know what is happening?
Thanks,
Paulo Gaspar
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Distributing the JSSE
Posted by Jon Stevens <jo...@latchkey.com>.
on 10/23/01 10:40 AM, "Jason van Zyl" <jv...@zenplex.com> wrote:
> I want to distribute the JSSE jars with the Turbine Development Kit but I'm
> not entirely sure if it's legal. On the JSSE website it says that "the
> binary implementation may be used royalty-free as part of commercial
> applications", but in the license it says for internal use only?
It is not legal.
-jon
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org