![]() | This article has not yet been rated on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||
|
This description of PCKS11 is wrong. PKCS is a certificate file format. It is not an API. —Preceding unsigned comment added by Mcr314 ( talk • contribs) 16:23, 19 January 2007
Substituting "P" for "PKCS#" in all the PKCS standards is common in the developer community using PKCS#11 but confusing for the novice and thus worthwhile to note concisely in this article for reader clarity. Yes, usage in forums and articles is is greater for "PKCS#11" than "P11", but this does not negate the usage of the short form in colloquial usage. A search for "P11" and "PKCS#11" quickly demonstrates interchangeability of the forms in API documentation and in discussion forums. - Joachimv ( talk) 06:04, 5 September 2009 (UTC)
The section on "Other Implementations" mentions that "Sun's Java has included a native (written in Java) implementation of PKCS #11". The link on the word "JCE" in fact points to the "Sun PKCS #11 Provider", which is in fact not an implementation of PKCS #11, but more an adapter, using a native interface to call the functions of a PKCS #11 library. It implements a Java JCE Provider interface, using the functions of a PKCS#11 library to provide its services (crypto functionality and/or access to key and other objects).
Also the wording "native (written in Java)" seems pointless - it is either native (not Java), or Java (not native). After, the JNI are not used to interface Java to Java, but Java to native code. And it is not really practical to implement a "C Api" in Java.
Would it be better to say something like "Sun's Java includes a PKCS #11 JCE provider, allowing access to any PKCS #11 library".
But than again, who cares.
PKCS#12 Pooseant ( talk) 07:24, 9 October 2016 (UTC)
The link to sdeancomponents is now dead and points to a domain squatter. Unfortunately this page is not in any web archive that I can find. These components are a part of a project on github: https://github.com/t-d-k/doxbox/tree/master/SDeanComponents. I am the maintainer of that project so don't want to update the link myself as I could have a vested interest. Tdk at squte ( talk) 21:33, 9 September 2014 (UTC)
![]() | This article has not yet been rated on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||
|
This description of PCKS11 is wrong. PKCS is a certificate file format. It is not an API. —Preceding unsigned comment added by Mcr314 ( talk • contribs) 16:23, 19 January 2007
Substituting "P" for "PKCS#" in all the PKCS standards is common in the developer community using PKCS#11 but confusing for the novice and thus worthwhile to note concisely in this article for reader clarity. Yes, usage in forums and articles is is greater for "PKCS#11" than "P11", but this does not negate the usage of the short form in colloquial usage. A search for "P11" and "PKCS#11" quickly demonstrates interchangeability of the forms in API documentation and in discussion forums. - Joachimv ( talk) 06:04, 5 September 2009 (UTC)
The section on "Other Implementations" mentions that "Sun's Java has included a native (written in Java) implementation of PKCS #11". The link on the word "JCE" in fact points to the "Sun PKCS #11 Provider", which is in fact not an implementation of PKCS #11, but more an adapter, using a native interface to call the functions of a PKCS #11 library. It implements a Java JCE Provider interface, using the functions of a PKCS#11 library to provide its services (crypto functionality and/or access to key and other objects).
Also the wording "native (written in Java)" seems pointless - it is either native (not Java), or Java (not native). After, the JNI are not used to interface Java to Java, but Java to native code. And it is not really practical to implement a "C Api" in Java.
Would it be better to say something like "Sun's Java includes a PKCS #11 JCE provider, allowing access to any PKCS #11 library".
But than again, who cares.
PKCS#12 Pooseant ( talk) 07:24, 9 October 2016 (UTC)
The link to sdeancomponents is now dead and points to a domain squatter. Unfortunately this page is not in any web archive that I can find. These components are a part of a project on github: https://github.com/t-d-k/doxbox/tree/master/SDeanComponents. I am the maintainer of that project so don't want to update the link myself as I could have a vested interest. Tdk at squte ( talk) 21:33, 9 September 2014 (UTC)