m4sterchain opened a new pull request #190: Optimize RPC TLS config
URL: https://github.com/apache/incubator-teaclave/pull/190
 
 
   ## Description
   
   Related to #61. I optimized the TLS config cache related logic with the 
following changes.
   - Simplify `get_tls_config` logic, changed the hash_map cached structure.
   - Introduce `private_key_sha256` as an identify to CertKeyPair, making 
`get_ra_cert` return a simple CertKeyPair.
   - Decouple `ecc_handle`  from the params of `fn gen_ecc_cert`.
   - Split the contruction of cert_der and private_key_der in to two different 
functions.
   
   I am still working the optimization, and will finally fix #61 in a descent 
way. 
   
   Fixes # (issue)
   
   ## Type of change (select applied and DELETE the others)
   
   - [ ] Bug fix (non-breaking change which fixes an issue)
   - [ ] New feature (non-breaking change which adds functionality)
   - [ ] Breaking change (fix or feature that would cause existing 
functionality to not work as expected)
   - [ ] API change with a documentation update
   - [ ] Additional test coverage
   - [ ] Code cleanup or just sync with upstream third-party crates
   
   ## How Has This Been Tested?
   
   ## Checklist (check ALL before submitting PR, even not applicable)
   
   - [ ] Fork the repo and create your branch from `master`.
   - [ ] If you've added code that should be tested, add tests.
   - [ ] If you've changed APIs, update the documentation.
   - [ ] Ensure the tests pass (see CI results).
   - [ ] Make sure your code lints/format.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to