366:"Only 4500 hits" means there is usage of "P11". It's not like there are many more than 4500 developers using the PKCS #11 standard. It's not about significant percentage or overwhelming usage. It's about colloquial or slang usage among developers. Contrary to your assertions, all of these links do in fact show colloquial usage of "P11" as short for "PKCS #11". In fact, all of those links have usage of the shortened "P11" in code, in descriptions, in labels, in parameter names, etc. In these cases "P11" is short for "PKCS #11". A non-technical person trying to understand what "P11" means has a hard time finding out the answer. Listing the short colloquial usage is important to help non-technical users identify the technology referred to behind the slang. Eliminating such text from the Wiki entry based on personal experience as opposed to evidence of usage in the development community is short sighted and not helpful.
175:
157:
129:
73:
49:
22:
333:
317:
I'm not convinced of that - the above link only gives some 4500 hits - and a lot of those aren't actually developers referring to it as "P11"; they're things hits where "p11" is of a longer string (e.g. libpam-p11), or as (for example) variables and such called "p11" - neither backs up your comment,
297:
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
395:
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
410:
Java's PKCS#11 provider is a PKCS11 consumer. PKCS11 implementations can be of the type where they consume PKCS11, or where they provide PKCS11 services. Both are indeed implementations. Both types implementations were demonstrated at the 2015 Oasis interoperability booth at RSA
399:
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.
276:
PKCS is a series of cryptography standards promoted by RSA Security (now a part of EMC). The majority are data format and interchange standards for cryptographic algorithms and their use, but #11 is in fact an interface standard. See
396:
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).
119:
448:
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:
509:
499:
113:
339:, where PKCS#11 is also present in order to get come kind of context.) This gives a better view of how widespread "P11" is as a developer term - only some 46 hits(!)
323:
The URL posted actually backs up my view - if you look through all the google hits it shows, the overwhelming majority have "PKCS#11"/"PKCS11" in the subject, and
529:
514:
412:
223:
504:
229:
519:
467:
Thanks for bringing this to attention. These kinds of lists, particularly lists of external links are generally discouraged, so I have split that out as
89:
494:
138:
59:
199:
524:
80:
54:
373:
299:
182:
162:
403:
Would it be better to say something like "Sun's Java includes a PKCS #11 JCE provider, allowing access to any PKCS #11 library".
327:"P11". If it was commonly referred to as "P11", you could expect a significant proportion returned to have "P11" in the subject.
534:
413:
https://www.oasis-open.org/news/pr/twelve-companies-demonstrate-interoperability-for-oasis-kmip-and-pkcs-11-encryption-and-cryp
29:
468:
267:
452:. I am the maintainer of that project so don't want to update the link myself as I could have a vested interest.
35:
377:
369:
255:
457:
195:
434:
307:
198:
on
Knowledge (XXG). If you would like to participate, please visit the project page, where you can join
88:
on
Knowledge (XXG). If you would like to participate, please visit the project page, where you can join
283:
419:
302:
quickly demonstrates interchangeability of the forms in API documentation and in discussion forums. -
430:
303:
415:
353:
453:
449:
263:
476:
251:
This description of PCKS11 is wrong. PKCS is a certificate file format. It is not an API.
488:
349:
85:
259:
174:
156:
472:
278:
191:
128:
187:
72:
48:
293:
In
Colloquial usage developers often refer to the API simply as "P11"
479:
461:
438:
423:
381:
357:
318:
that developers use "P11" when talking to each other about it.
311:
286:
15:
127:
450:
https://github.com/t-d-k/doxbox/tree/master/SDeanComponents
28:
This article has not yet been rated on
Knowledge (XXG)'s
298:
negate the usage of the short form in colloquial usage.
348:
experience, though that doesn't mean it's widespread
186:, a collaborative effort to improve the coverage of
84:, a collaborative effort to improve the coverage of
228:This article has not yet received a rating on the
118:This article has not yet received a rating on the
8:
510:Unknown-importance Computer science articles
151:
43:
21:
19:
332:On this basis, a better search would be:
500:Unknown-importance Cryptography articles
98:Knowledge (XXG):WikiProject Cryptography
153:
45:
530:Unknown-importance Computing articles
515:WikiProject Computer science articles
208:Knowledge (XXG):WikiProject Computing
7:
505:Unassessed Computer science articles
180:This article is within the scope of
78:This article is within the scope of
335:(searching groups for "P11" in the
34:It is of interest to the following
469:List of applications using PKCS 11
14:
520:WikiProject Cryptography articles
471:and unlinked all the entries. --
101:Template:WikiProject Cryptography
495:Unassessed Cryptography articles
300:A search for "P11" and "PKCS#11"
173:
155:
71:
47:
20:
211:Template:WikiProject Computing
1:
525:Unassessed Computing articles
480:17:44, 11 November 2014 (UTC)
462:21:33, 9 September 2014 (UTC)
358:07:18, 5 September 2009 (UTC)
312:06:04, 5 September 2009 (UTC)
202:and see a list of open tasks.
136:This article is supported by
92:and see a list of open tasks.
382:14:11, 14 October 2011 (UTC)
139:WikiProject Computer science
439:07:24, 9 October 2016 (UTC)
406:But than again, who cares.
551:
287:19:02, 18 April 2007 (UTC)
230:project's importance scale
344:It may well be common in
227:
168:
135:
117:
66:
42:
424:23:08, 13 May 2015 (UTC)
270:) 16:23, 19 January 2007
81:WikiProject Cryptography
535:All Computing articles
196:information technology
132:
183:WikiProject Computing
131:
104:Cryptography articles
391:Java Implementation?
247:Description wrong?
214:Computing articles
133:
30:content assessment
478:
372:comment added by
272:
258:comment added by
244:
243:
240:
239:
236:
235:
150:
149:
146:
145:
542:
475:
384:
271:
252:
216:
215:
212:
209:
206:
177:
170:
169:
159:
152:
120:importance scale
106:
105:
102:
99:
96:
75:
68:
67:
62:
60:Computer science
51:
44:
25:
24:
23:
16:
550:
549:
545:
544:
543:
541:
540:
539:
485:
484:
446:
393:
367:
295:
253:
249:
213:
210:
207:
204:
203:
103:
100:
97:
94:
93:
57:
12:
11:
5:
548:
546:
538:
537:
532:
527:
522:
517:
512:
507:
502:
497:
487:
486:
483:
482:
445:
442:
427:
426:
392:
389:
388:
387:
386:
385:
361:
360:
341:
340:
329:
328:
320:
319:
294:
291:
290:
289:
281:
248:
245:
242:
241:
238:
237:
234:
233:
226:
220:
219:
217:
200:the discussion
178:
166:
165:
160:
148:
147:
144:
143:
134:
124:
123:
116:
110:
109:
107:
90:the discussion
76:
64:
63:
52:
40:
39:
33:
26:
13:
10:
9:
6:
4:
3:
2:
547:
536:
533:
531:
528:
526:
523:
521:
518:
516:
513:
511:
508:
506:
503:
501:
498:
496:
493:
492:
490:
481:
477:
474:
470:
466:
465:
464:
463:
459:
455:
451:
443:
441:
440:
436:
432:
425:
421:
417:
414:
409:
408:
407:
404:
401:
397:
390:
383:
379:
375:
374:24.205.251.60
371:
365:
364:
363:
362:
359:
355:
351:
347:
343:
342:
338:
334:
331:
330:
326:
322:
321:
316:
315:
314:
313:
309:
305:
301:
292:
288:
285:
282:
279:
275:
274:
273:
269:
265:
261:
257:
246:
231:
225:
222:
221:
218:
201:
197:
193:
189:
185:
184:
179:
176:
172:
171:
167:
164:
161:
158:
154:
141:
140:
130:
126:
125:
121:
115:
112:
111:
108:
91:
87:
83:
82:
77:
74:
70:
69:
65:
61:
56:
53:
50:
46:
41:
37:
31:
27:
18:
17:
454:Tdk at squte
447:
428:
405:
402:
398:
394:
368:— Preceding
345:
336:
324:
296:
284:71.107.96.47
280:for details.
250:
181:
137:
95:Cryptography
86:Cryptography
79:
55:Cryptography
36:WikiProjects
444:borken link
254:—Preceding
489:Categories
205:Computing
192:computing
188:computers
163:Computing
431:Pooseant
429:PKCS#12
370:unsigned
350:Nuwewsco
304:Joachimv
268:contribs
256:unsigned
337:subject
416:Bubbva
260:Mcr314
194:, and
32:scale.
473:intgr
458:talk
435:talk
420:talk
378:talk
354:talk
346:your
308:talk
264:talk
325:not
224:???
114:???
491::
460:)
437:)
422:)
380:)
356:)
310:)
266:•
190:,
58::
456:(
433:(
418:(
376:(
352:(
306:(
262:(
232:.
142:.
122:.
38::
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
