You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2020/03/08 15:27:52 UTC

[GitHub] [openwhisk] rabbah commented on issue #4756: Create AES128 and AES256 encryption for parameters

rabbah commented on issue #4756: Create AES128 and AES256 encryption for parameters
URL: https://github.com/apache/openwhisk/pull/4756#issuecomment-596217518
 
 
   @mcdan I'm going through this PR again - sorry for the delay. I've resolved the conflict locally and will push that to your branch when I'm done. I have a few other code suggestions I'll make as I go through the code.
   
   I want to confirm some of my understanding:
   1. when parameter encryption is turned on, the parameters on action update and package update are encrypted using the current scheme.
   2. when an action or package is retrieved, the parameters are not decoded
   
   Is that correct? If so, did you omit triggers on purpose?
   

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services