71
edits
(→Project Ideas (non-definitive): Added ZAP suggestions) |
Franziskus (talk | contribs) (new NSS ideas) |
||
| Line 62: | Line 62: | ||
ZAP has extensive support for supporting application authentication, but configuring this is a manual process which can be tricky to get right. | ZAP has extensive support for supporting application authentication, but configuring this is a manual process which can be tricky to get right. | ||
The enhancement would allow ZAP to detect as many forms of authentication as possible and automatically configure them using the existing ZAP functionality. | The enhancement would allow ZAP to detect as many forms of authentication as possible and automatically configure them using the existing ZAP functionality. | ||
=== NSS Demos === | |||
Proposed by: franziskus | |||
Using the [https://nss-crypto.org/ NSS] library in your own project isn't the easiest job to do. | |||
In this project a suite of NSS demos should be compiled (ideally web executable using something like [https://runnable.io Runnable]) as reference for developers that want to use the library. | |||
=== The NSS TLS Server === | |||
Proposed by: franziskus | |||
The TLS stack in [https://nss-crypto.org/ NSS] provides basic support for TLS servers such as [https://fedorahosted.org/mod_nss/]. | |||
With this code being rarely used and tested it contains significant shortcomings. | |||
This project should identify those problems, fix them, and provide integration for all major HTTP server. | |||
=== SHA-3 Implementation in NSS === | |||
Proposed by: franziskus | |||
[https://en.wikipedia.org/wiki/SHA-3 SHA-3] is a new cryptographic hash functions. | |||
This project should provide basic SHA-3 support for [https://nss-crypto.org/ NSS]. | |||
=== New Idea Template === | === New Idea Template === | ||
edits