> We have no plans to do this.
>> May be will put it into your plans ?
>>> Doubtful. We have lots of other work to do. Writing a full-strength
database-backed OCSP responder is outside of our interests.
I decided not wait for you and I have made OSSL Ocsp responder based at
index DB -
Congratulations, sounds like nice work!
Ø And a big wishing to you as dev. team is to check code and include to the
next nearest release version.
I doubt anyone on the team will review the code, and it almost certainly will
not become part of OpenSSL.
I hope that others are interested and
Ø Why this part of code will never become part of OSSL ?
It's not what we do.
OpenSSL is a crypto and TLS toolkit. It is not a general PKI solution.
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
> ... and it almost certainly will not become part of OpenSSL
It sound bad.
Why this part of code will never become part of OSSL ?
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
> We have no plans to do this.
May be will put it into your plans ?
> It would be nice to see something like this as a new open-source project.
I am for that by both hands. Burt unfortunatelly I am not a well skilled
programmer/developer and I will not do it.
I can give the task for that for
Ø > We have no plans to do this.
May be will put it into your plans ?
Doubtful. We have lots of other work to do. Writing a full-strength
database-backed OCSP responder is outside of our interests.
___
openssl-dev mailing list
To unsubscribe:
Ø Is it possible to include at nearest developing plans ability of running
OpenSSL at Ocsp responder mode as multithreading daemon (Linux) and service
(Windows) ?
We have no plans to do this.
It would be nice to see something like this as a new open-source project.
