> I got the Object ID and version straight out of the Certificate using
> Keystore Explorer. I'm not sure why there is a difference.
Keystore Explorer uses Bouncy Castle (https://www.bouncycastle.org/) as
provider for JCE.
If your JRE/JDK does not provide some algorithm you could use Bouncy
Java is 1.8.0_391
On Thu, Apr 4, 2024 at 1:35 PM Timothy Resh wrote:
> I got the Object ID and version straight out of the Certificate using
> Keystore Explorer. I'm not sure why there is a difference.
>
> The "\" is because I manually deleted the beginning part of the path.
> It's correct in
I got the Object ID and version straight out of the Certificate using
Keystore Explorer. I'm not sure why there is a difference.
The "\" is because I manually deleted the beginning part of the path. It's
correct in the actual file.
Java is 1.8.
On Wed, Apr 3, 2024 at 6:11 PM Konstantin
> Caused by: java.security.NoSuchAlgorithmException: The PKCS#8 encryption
> algorithm with DER encoded OID of [2a864886f70d010c0103] was not recognised
If I google for the above hex number, it finds the following:
'2A864886F70D010C0103' -- 1.2.840.113549.1.12.1.3
pbeWithSHAAnd3-KeyTripleDES-CBC
Sure, I can provide the entire setup for you. I'll work on that tonight .
On Sun, Mar 31, 2024 at 2:05 PM Mark Thomas wrote:
> On 25/03/2024 16:56, Timothy Resh wrote:
> > Sorry for the delay. Our certificate creation process was automated
> > several years ago and I had to go through the
On 25/03/2024 16:56, Timothy Resh wrote:
Sorry for the delay. Our certificate creation process was automated
several years ago and I had to go through the code to figure out the
commands being used for the certificates
First, we use the createcert.exe from the Sybase 17 installation to
I
Sorry for the delay. Our certificate creation process was automated
several years ago and I had to go through the code to figure out the
commands being used for the certificates
First, we use the createcert.exe from the Sybase 17 installation to
generate a DB cert for ODBC connectivity. Please
On 19/03/2024 18:18, Timothy Resh wrote:
where the . is the fqdn
This works fine *until* Tomcat 9.0.83 and now we get the following listed
below. I have read some of the
https://bz-he-de.apache.org/bugzilla/show_bug.cgi?id=67675 bugs and ask for
help.
The certificates are being created
Timothy,
On 3/19/24 14:18, Timothy Resh wrote:
where the . is the fqdn
This works fine *until* Tomcat 9.0.83 and now we get the following listed
below.
Is it possible for you to re-test with Tomcat 9.0.85 or later?
-chris
I have read some of the
where the . is the fqdn
This works fine *until* Tomcat 9.0.83 and now we get the following listed
below. I have read some of the
https://bz-he-de.apache.org/bugzilla/show_bug.cgi?id=67675 bugs and ask for
help.
The certificates are being created using openssl 3.013. Please note the
10 matches
Mail list logo
