pov, Michael (LDA IT PLM):
Hi folks,
we have recently noticed the following with Java's kinit (tested with
Zulu 8 and 13, code is identical in 18 as well):
C:\Users\osipovmi>kinit osipo...@ad001.siemens.net
I have intentionally written the realm in lowercase to rely on
canonicalizatio
Am 2021-10-21 um 21:38 schrieb Wei-Jun Wang:
KrbKdcReq throws the exception on line 55, so it is the previous check
if (isAsReq && !req.reqBody.cname.equals(rep.cname) &&
((!req.reqBody.kdcOptions.get(KDCOptions.CANONICALIZE) &&
req.reqBody.cname.get
Hi folks,
we have recently noticed the following with Java's kinit (tested with
Zulu 8 and 13, code is identical in 18 as well):
C:\Users\osipovmi>kinit osipo...@ad001.siemens.net
I have intentionally written the realm in lowercase to rely on
canonicalization of the AD KDC. krb5.conf conta
nown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=JZcwDAqmzCbNmMSAaZiagdUpMNCCZxH59bs4a4avERo%3D&reserved=0
On Jul 30, 2021, at 11:26 AM, Osipov, Michael (LDA IT PLM)
wrote:
Am 2021-07-29 um 16:05 schrieb Sean Mullan:
Are you calling the PKCS12Attribute(String, String) cons
.,L=Ankara,C=TR
was smart enough to stick with US-ASCII only in the CN, but still
single-byte != two-byte UCS-2
On 6/14/21 3:21 PM, Osipov, Michael (LDA IT PLM) wrote:
Folks,
can someone confirm the following bug or tell me I am too stupid to read
the RFCs:
I have recently created a PKCS12-ba
Folks,
can someone confirm the following bug or tell me I am too stupid to read
the RFCs:
I have recently created a PKCS12-based trust store and had one CA from
Hungary with non-ASCII chars in the subject's CN RDN.
RFC 7292 for friendlyName refers to RFC 2985, section 5.5.1:
friendlyNa
Hi Max,
thank you for fixing my bug. I have finally verified it to properly work
just as specified in the RFC with AdoptOpenJDK 16 on Windows.
Do you see any chance to have this small change to be backported to 8
and 11? If this is the wrong list should this go to jdk8u-dev@?
Regards,
Mich
