javac/cvs
Submitted by hagar on Fri, 05/21/2004 - 23:02.
As Levente got as far as he did, I guess we at the network team have a job ahead that we can manage very fast, if we lay ourselv in chaines. CVS access in ssh mode. I refound the http://www.bouncycastle.org/ it's for the javax.crypto package, and using it with the jsch (http://www.jcraft.com/jsch/) package we could get ssh combined with http://javacvs.netbeans.org/index.html, I guess we could make cvs via ssh possible for development direct in jnode better/possible to sourceforge. Is there any voliters? I'll my self be one of them.
Regards,
Martin
- Login to post comments
Crypto API
Martin,
For javax.crypto, there is GNU Crypto (http://www.gnu.org/software/gnu-crypto/), an external projet of GNU Classpath. Perhaps can we check this project first.
Fabien.
The javax.crypto in the GNU C
The javax.crypto in the GNU Crypto is based on the Bouncy Castle Crypto APIs, but I guess we should take the GNU packages and add them to the core. The rest, as I see it, should be added to the net. I'll start with adding the gnu crypto.
Regards,
Licenses
Hi Martin,
Make sure to check the licenses of the stuff you want to include. It is very easy to overlook that and have an unwanted "lock-in".
Ewout
I just checked: JavaCVS:
I just checked:
JavaCVS:
License: NetBeans source code is available under a variant of the Mozilla Public License (MPL). The license, called the Sun Public License (SPL), is the equivalent to the MPL with only trivial changes such as mentioning Sun Microsystems rather than Netscape. It is compliant with the Open Source Definition. You will find the the hacker's diff, and the lawyer's diff. As well as the full text of the SPL and a link to License FAQs.
JSCH:
JSch 0.0.* was released under the GNU LGPL license. Later, we have switched over to a BSD-style license.
Bouncy Castle Crypto APIs:
Copyright (c) 2000 The Legion Of The Bouncy Castle (http://www.bouncycastle.org)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
I guess, we shall have a place where we put the licenses of other projects, but else it should ok to use these apis in JNode.
Regards,
Martin