Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.java.security > #18

Re: X500Principal and UTF-16 encoded certificates

From Roedy Green <see_website@mindprod.com.invalid>
Newsgroups comp.lang.java.security
Subject Re: X500Principal and UTF-16 encoded certificates
Date 2011-04-22 12:38 -0700
Organization Canadian Mind Products
Message-ID <osl3r696edh6fp07t1d5219j5fb1jnpd1g@4ax.com> (permalink)
References <f3317f71-49c9-448d-9baa-8cb439a19b4b@l36g2000vbp.googlegroups.com> <ed8d8950-6fb4-4082-800f-1609258ceb96@hd10g2000vbb.googlegroups.com>

Show all headers | View raw


On Thu, 21 Apr 2011 08:27:02 -0700 (PDT), Yosi Izaq
<izaqyos@gmail.com> wrote, quoted or indirectly quoted someone who
said :

>Is there any specific reason why
>X500Principal:getName(X500Principal.RFC2253) may be preferable to
>X500Principal:getName(X500Principal.RFC1779)?

I think RFC1779 only applies to ASCII.  Even 16-bit Unicode was a new
fangled idea when it was released. C with its 8-bit chars was still
king.

RFC-2253 formally obsoletes RFC-1779.  

RFC-2253 explicitly states in its title it is for UTF-8 only.

RFC-2253 in turn was obsoleted by RFC-4510, RFC-4514 and was updated
by RFC 3373.

You can discover this by chasing the links at
http://mindprod.com/jgloss/rfc.html

I wish RFCs would in the header report the obsoletes/obsoleted-by
information.  It is so easy to use out of date information. Perhaps
someone might even edit them to create a unified document set with all
obsolete information removed, or at least partially grayed out.

-- 
Roedy Green Canadian Mind Products
http://mindprod.com
Politicians complain that Kindles and iBooks are killing jobs by 
destroying the paper book industry.  I see it that they have create a way 
to produce books for less than a third the cost without destroying forests 
and emitting greenhouse gases in the process.  They have created wealth.  
They are encouraging literacy and cutting the costs of education.  

Back to comp.lang.java.security | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

X500Principal and UTF-16 encoded certificates Yosi Izaq <izaqyos@gmail.com> - 2011-04-21 06:22 -0700
  Re: X500Principal and UTF-16 encoded certificates Yosi Izaq <izaqyos@gmail.com> - 2011-04-21 08:27 -0700
    Re: X500Principal and UTF-16 encoded certificates Daniele Futtorovic <da.futt.news@laposte-dot-net.invalid> - 2011-04-22 17:35 +0200
      Re: X500Principal and UTF-16 encoded certificates Yosi Izaq <izaqyos@gmail.com> - 2011-04-24 02:21 -0700
    Re: X500Principal and UTF-16 encoded certificates Roedy Green <see_website@mindprod.com.invalid> - 2011-04-22 12:38 -0700
      Re: X500Principal and UTF-16 encoded certificates Stanimir Stamenkov <s7an10@netscape.net> - 2011-04-23 01:09 +0300
        Re: X500Principal and UTF-16 encoded certificates Roedy Green <see_website@mindprod.com.invalid> - 2011-04-24 11:54 -0700
          Re: X500Principal and UTF-16 encoded certificates Daniele Futtorovic <da.futt.news@laposte-dot-net.invalid> - 2011-04-24 21:32 +0200
            Re: X500Principal and UTF-16 encoded certificates Roedy Green <see_website@mindprod.com.invalid> - 2011-04-25 17:23 -0700
      Re: X500Principal and UTF-16 encoded certificates Yosi Izaq <izaqyos@gmail.com> - 2011-04-24 02:32 -0700

csiph-web