Mark,
On 8/26/21 06:08, Mark Thomas wrote:
On 25/08/2021 18:04, Christopher Schultz wrote:
Mark,
On 8/25/21 10:28, Mark Thomas wrote:
On 25/08/2021 15:10, Christopher Schultz wrote:
All,
I'm trying to do this without looking at the code which is in Tomcat
because I'd like to release it separately and not have to worry
about figuring out hos to get permission, etc.
It is ALv2 so the requirements are pretty minimal. You just need to
include a copy of the ALv2, note you based it on Apache Tomcat and
don;t use any ASF trademarks in your product name.
Hmm. I seem to recall asking someone if I could contribute your
PEMFile stuff to the PostgreSQL JDBC driver project (they only support
non-encrypted DER files directly) and the reply I got was something
along the lines of "horrific copyright violation/IP theft/good luck
finding all the original authors and getting their permission/etc."
(paraphrasing).
Hmm. Odd. I wonder why they said that. Do you have a public reference to
that conversation. Obviously, any potential IP issues are a concern.
I'll look for it.
Looking at the code, I'm struggling to see where the concern would come
from.
The original contribution was from Emmanuel. Given his work on JSign I
have no reason to think the contribution wasn't original.
The ASN.1 parser was written from scratch by me. There are comment
references to various specifications but whatever copyright/license they
are under has no bearing on the copyright/licensing of the
implementation. (And most, if not all, are RFCs.)
One of the first things I did was write my own ASN.1 parser. It looks
like you went for the barest of bones, while I went a step or so farther.
The other commits are essentially cosmetic / refactoring.
If they wanted to relicense the code rather than use it under the ALv2
then I can see how they might view that as potentially difficult
although in this instance given all the people involved are Tomcat
committers it would likely be fairly simple (assuming all the
contributors were happy).
PostgreSQL has their own license[1]. It's pretty bare-bones, in the MIT
style.
I found a PRIVATE KEY[2] that my code cannot open without some
additional work. I'm going to try it with Tomcat to see if we have the
same issue.
There is code and references in one of the SO answers that enabled me to
adapt my code to with with that type of encrypted key.
Thanks,
-chris
[1] https://www.postgresql.org/about/licence/
[2]
https://stackoverflow.com/questions/63832456/parsing-encrypted-pkcs8-encoded-pem-file-programatically
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
