for AppxPackage Signing from within Craft.
some certificates might be secured by password. This patch extends Craft to support password-protected certificates
| vonreth |
for AppxPackage Signing from within Craft.
some certificates might be secured by password. This patch extends Craft to support password-protected certificates
| No Linters Available |
| No Unit Test Coverage |
| Buildable 20897 | |
| Build 20915: arc lint + arc unit |
I won't accept this change.
Saving a password in config file offers some risk.
Also if its a self signed cert for testing, just create one without pw.
| bin/utils.py | ||
|---|---|---|
| 887 | Maybe you could create a general implementation for promts like this in https://github.com/KDE/craft/blob/master/bin/Utils/CraftChoicePrompt.py (be sure to directly fail and not block in ci mode. ci mode would need another implementation) It sould probably also create a notification to make aware of the promt. | |
Protected = True
in the CraftSettings.ini's Signing section to ask for password prompt if your signing certificate is password-protected.
Other than this, CraftChoicePrompt/py has now support for promptForPassword so password inputs can be done anywhere within Craft.
as you can see here ^, password is visible in the next logged command. How do we get rid of the password from that?
| bin/Utils/CraftChoicePrompt.py | ||
|---|---|---|
| 98 | Well I'm not sure.. I hate the idea of managing it. | |
| 102 | In a debug log probably. | |
| bin/utils.py | ||
| 888 | You can pass kwargs["logCommand"] = False to the system call. then it will only show in verbose mode. | |
| bin/Utils/CraftChoicePrompt.py | ||
|---|---|---|
| 98 | actually, I meant to ask how to 'fail' here. Could you help me with a short code snippet or something? | |
| bin/utils.py | ||
|---|---|---|
| 889 | I tried doing kwargs["logCommand"] = False here but it didn't work. I saw a similar thing in Craft.py, where you initialized an empty dict first and then started filling it, so I followed. | |
| bin/utils.py | ||
|---|---|---|
| 889 | no issue, just something i noticed. | |
pushed the commit directly.
https://commits.kde.org/craft/e1f690e1fbfe83ebb62c834611f618ed57ac51df