Talk:EJBCA

This article was nominated for deletion on 14 April 2021. The result of the discussion was speedy keep.

This article was nominated for deletion on 17 April 2021. The result of the discussion was speedy keep.

Java Stub‑class Low‑importance

	This article is within the scope of WikiProject Java, a collaborative effort to improve the coverage of Java on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.JavaWikipedia:WikiProject JavaTemplate:WikiProject JavaJava articles
Stub	This article has been rated as Stub-class on Wikipedia's content assessment scale.
Low	This article has been rated as Low-importance on the project's importance scale.

Computing Stub‑class Low‑importance

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Stub	This article has been rated as Stub-class on Wikipedia's content assessment scale.
Low	This article has been rated as Low-importance on the project's importance scale.

The following Wikipedia contributor has declared a personal or professional connection to the subject of this article. Relevant policies and guidelines may include conflict of interest, autobiography, and neutral point of view.

Primetomas (talk · contribs) This user has contributed to the article. This user has declared a connection. (declared here)

Untitled

Just announced to the community that it exists.. it would be nice to have a day or two to provide some more info..—Preceding unsigned comment added by ZeiZai6Y (talk • contribs) 09:44, 29 April 2008 (UTC)[reply]

Do you have any sources other than the project's website? Any articles, news releases, etc? UltraExactZZ ^Claims~ Evidence 12:45, 29 April 2008 (UTC)[reply]

A good start but this article needs improvement

I like the fact that you put EJBCA in. But it currently rather reads like a catalog sheet than like a Wikipedia article.

You should make sure that every information has a notable source. Currently your article looks like original research
The whole overall context is missing: the history of EJBCA, the context where it is relevant.
Also critical reflections are needed. What are the weak points? Why are commercial systems still relevant? And sources, discussing it would make sense.
Are there notable examples, perhaps open source portals or big Cloud applications which use EJBCA

Thx for making it better

ScienceGuard (talk) 18:32, 16 October 2016 (UTC)[reply]

Remove dead or redundant links

1. The link to: A workflow based architecture for Public Key Infrastructure; Johan Eklund; TRITA-CSC-E 2010:047 Is dead, and KTH does not seem to keep an archive of these anymore. I suggest removing it. 2. In External links, only the first one should be kept imo (reverting my edit that added them). The others are linked from there, or already present in the article (github). I suggest removing the three links below the "official site".

COI: I am the founder of this opensource project Primetomas (talk) 05:51, 18 April 2021 (UTC)[reply]

Edit request - See also

It is requested that an edit be made to the semi-protected article at A. (edit · history · last · links · protection log)

This template must be followed by a complete and specific description of the request, that is, specify what text should be removed and a verbatim copy of the text that should replace it. "Please change X" is not acceptable and will be rejected; the request must be of the form "please change X to Y".

The edit may be made by any autoconfirmed user. Remember to change the |answered=no parameter to "yes" when the request has been accepted, rejected or on hold awaiting user input. This is so that inactive or completed requests don't needlessly fill up the edit requests category. You may also wish to use the {{ESp}} template in the response. To request that a page be protected or unprotected, make a protection request.

Please replace the contents of "See also" with:

Public Key Infrastructure Open Source Implementations

Primetomas (talk) 08:45, 19 April 2021 (UTC)[reply]

Go ahead: I have reviewed these proposed changes and suggest that you go ahead and make the proposed changes to the page. EpicPupper 18:38, 19 April 2021 (UTC)[reply]

@EpicPupper: Implemented. Primetomas (talk) 06:16, 20 April 2021 (UTC)[reply]

Edit request - External links

It is requested that an edit be made to the semi-protected article at A. (edit · history · last · links · protection log)

This template must be followed by a complete and specific description of the request, that is, specify what text should be removed and a verbatim copy of the text that should replace it. "Please change X" is not acceptable and will be rejected; the request must be of the form "please change X to Y".

The edit may be made by any autoconfirmed user. Remember to change the |answered=no parameter to "yes" when the request has been accepted, rejected or on hold awaiting user input. This is so that inactive or completed requests don't needlessly fill up the edit requests category. You may also wish to use the {{ESp}} template in the response. To request that a page be protected or unprotected, make a protection request.

Remove redundant links from the External links section, leaving it with only one link:

Replace:

No URL found. Please specify a URL here or add one to Wikidata.
EJBCA at SourceForge
EJBCA at Docker Hub
EJBCA source at GitHub

with:

No URL found. Please specify a URL here or add one to Wikidata.

Primetomas (talk) 08:52, 19 April 2021 (UTC)[reply]

Done Anton.bersh (talk) 06:29, 20 April 2021 (UTC)[reply]

Edit request - remove dead links and documentation references

It is requested that an edit be made to the semi-protected article at A. (edit · history · last · links · protection log)

This template must be followed by a complete and specific description of the request, that is, specify what text should be removed and a verbatim copy of the text that should replace it. "Please change X" is not acceptable and will be rejected; the request must be of the form "please change X to Y".

The edit may be made by any autoconfirmed user. Remember to change the |answered=no parameter to "yes" when the request has been accepted, rejected or on hold awaiting user input. This is so that inactive or completed requests don't needlessly fill up the edit requests category. You may also wish to use the {{ESp}} template in the response. To request that a page be protected or unprotected, make a protection request.

In "Further reading" remove the list item that is not available on-line anymore, "A workflow based architecture for Public Key Infrastructure"

In "Design", completely remove the documentation reference that moved and is incorrect: ^[1]

In Design completely remove the documentation reference that is just a link to product documentation: ^[2]

Primetomas (talk) 08:58, 19 April 2021 (UTC)[reply]

I carried out these edits. Anton.bersh (talk) 09:47, 19 April 2021 (UTC)[reply]

Done EpicPupper 18:36, 19 April 2021 (UTC)[reply]

Edit request - Notable features edit #1

It is requested that an edit be made to the semi-protected article at A. (edit · history · last · links · protection log)

This template must be followed by a complete and specific description of the request, that is, specify what text should be removed and a verbatim copy of the text that should replace it. "Please change X" is not acceptable and will be rejected; the request must be of the form "please change X to Y".

The edit may be made by any autoconfirmed user. Remember to change the |answered=no parameter to "yes" when the request has been accepted, rejected or on hold awaiting user input. This is so that inactive or completed requests don't needlessly fill up the edit requests category. You may also wish to use the {{ESp}} template in the response. To request that a page be protected or unprotected, make a protection request.

Please change:

Online Certificate Status Protocol: For certificate validation you have the choice of using X.509 CRLs and OCSP (RFC6960).

to

Online Certificate Status Protocol: certificate validation options include X.509 CRLs and OCSP (RFC6960).

Please change:

Multiple algorithms: You can use all common, and some uncommon algorithms in your PKI. RSA, ECDSA, EdDSA, and DSA, SHA-1, SHA-2, and SHA-3. Compliant with NSA Suite B Cryptography.

to

Multiple algorithms: Common algorithms for usage in PKI includes: RSA, ECDSA, EdDSA, and DSA, SHA-1, SHA-2, and SHA-3. Compliant with NSA Suite B Cryptography.

Please change:

PKCS#11 HSMs: Using the standard PKCS 11 API you can use most PKCS#11 compliant HSMs to protect the CAs’ and OCSP responders’ private keys.

to

PKCS#11 HSMs: Standard PKCS 11 compliant hardware security modules are used to protect the CAs’ and OCSP responders’ private keys.

Please change:

High performance and capacity: You can build a PKI with capacity of issuing billions of certificates at a rate of several hundreds per second.

to

High capacity: Using a standard RDBMS the system have a capacity to store large amounts of issued certificates.

Primetomas (talk) 09:30, 19 April 2021 (UTC)[reply]

Go ahead: I have reviewed these proposed changes and suggest that you go ahead and make the proposed changes to the page. EpicPupper 18:37, 19 April 2021 (UTC)[reply]

@EpicPupper: Implemented. Do you think this resolves the Grammatical person issue? Primetomas (talk) 06:21, 20 April 2021 (UTC)[reply]

@Primetomas: I will take a look at the article today and see if the issue is resolved. EpicPupper 16:14, 22 April 2021 (UTC)[reply]

History section discussion

For discussion:

ScienceGuard suggests above to provide some history "The whole overall context is missing: the history of EJBCA, the context where it is relevant".

Would a section similar to the History section in Let's_Encrypt be good and appropriate? Something like (meta code):

---

History and Usage

The EJBCA project was started in 2001 (ref to v1.0 release post) by Tomas Gustavsson. PrimeKey, the company maintaining the project today, was incorporated in May 2002.

It has since been used to issue digital certificates for different use cases including Academia (citation), Grid Computing (citation), Energy (citation) and (other use cases with citation).

Subsection: Notable Issues

The EJBCA software has been used during some publicly noted certificate related incidents (citation to Arstechnica and The register articles)

---

I think this will answer some questions about usage and history, as well giving some critical reflection. What do people think?

Primetomas (talk) 16:37, 22 April 2021 (UTC) (note COI)[reply]

[1] "Automated and large scale operations".

[2] "PKI Architectures".

[1]

[2]

Untitled

A good start but this article needs improvement

Remove dead or redundant links

See also link to similar software?

Edit request - See also

Edit request - External links

Edit request - remove dead links and documentation references

Edit request - Notable features edit #1

History section discussion