use BouncyCastle as a library vs a JCE provider
Open
improvement
- Dominant language
- Java
- Stars
- 2.7k
- Forks
- 620
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 11
Description
in jclouds, we'd like to make tools that can be completely contained in a single jar. Ex.
http://skife.org/java/unix/2011/06/20/really_executable_jars.html
While sshj uses BouncyCastle as a JCE provider, this is not possible due to signed jar issues. It complicates things and many forget to put it separately or have to screw with their shade config, etc. In general, while a good idea, it introduces some accidental complexity.
Can we move sshj to just use BouncyCastle libraries? In doing so apps like jclouds don't need to dance around JCE issues, makine a much cleaner experience.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.