Index | Thread | Search

From:
Avon Robertson <avon.r@xtra.co.nz>
Subject:
Re: rpki-client: allow UTF8String for BGPsec router cert subjects
To:
Job Snijders <job@openbsd.org>
Cc:
tech@openbsd.org
Date:
Wed, 19 Nov 2025 12:46:42 +1300

Download raw body.

Thread
  • Job Snijders:

    rpki-client: allow UTF8String for BGPsec router cert subjects

    • Avon Robertson:

      rpki-client: allow UTF8String for BGPsec router cert subjects

  • On Tue, Nov 18, 2025 at 01:37:11PM +0000, Job Snijders wrote:
    > OK job@
    > 
    > but,
    > 
    > On Tue, Nov 18, 2025 at 01:53:37PM +0100, Theo Buehler wrote:
    > >  			 * XXX - For some reason RFC 8209, section 3.1.1 decided
    > > -			 * to allow UTF8String for BGPsec Router Certificates.
    > > +			 * to allow UTF8String for the subject of BGPsec Router
    > > +			 * Certificates, although RECOMMENDED contents fit in
    > > +			 * a PrintableString.
    > 
    > Is the above comment really needed? Perhaps:
    > 
    > 	/*
    > 	 * RFC 8209, section 3.1.1 suggests UTF8String is permissible
    > 	 * for the subject of BGPsec Router Certificates, but this
    > 	 * implementation consciescly only supports PrintableString.
    
    Replace above line with next line?
    
    	 * concise implementation only supports PrintableString.
    > 	 */
    
    > 
    > Kind regards,
    > 
    > Job
    > 
    
    -- 
    aer
    
    
  • Job Snijders:

    rpki-client: allow UTF8String for BGPsec router cert subjects