Agree, we should take the same approach.
It should not be part of lib and more "startup" bundles (as we have
eventadmin and others).
I will create a Jira about that.
Regards
JB
On 02/02/2020 17:43, Romain Manni-Bucau wrote:
> This is a one way choice so then bouncycastle becomes a jre
This is a one way choice so then bouncycastle becomes a jre provided lib
(as jaxb was) for consumers and bundles are no more working or use other
actual instances making it potentially corrupted if bundles and part of the
boot - potentially not just karaf jars -must share bc. Also note it would
Hi together,
how going on with this topic. Actually bouncastle is the defacto
standard security library for karaf and bundled by default. So taking
the approach explained by Robert sounds reasonable to upstream to Karaf
itself and moving libs to from system to boot and maybe even register
On 15/01/2020 16:25, Benjamin Graf wrote:
> Hi,
>
> I'm actually playing around with the latest 4.3.0-SNAPSHOT. I recognize
> that the ssh bundle is using bouncycastle for reading pem files right
> now (KARAF-6383). The "issue" I'm facing is that if I like to set
> bouncycastle as the security
+1 a temp classloader using local resolution or plain reimpl of pem read
does not sound terrible to me
Le mer. 15 janv. 2020 à 16:25, Benjamin Graf a
écrit :
> Hi,
>
> I'm actually playing around with the latest 4.3.0-SNAPSHOT. I recognize
> that the ssh bundle is using bouncycastle for reading
Hi,
I'm actually playing around with the latest 4.3.0-SNAPSHOT. I recognize
that the ssh bundle is using bouncycastle for reading pem files right
now (KARAF-6383). The "issue" I'm facing is that if I like to set
bouncycastle as the security provider via
"org.apache.karaf.security.providers =
