Revision history [back]
 | 1 | initial version | posted 2013-12-30 18:27:37 +0200  |
harbour app rpms to be signed by a dedicated key
As talked about here, it appears that the signing of harbour app rpms is left to the app provider.
Better would be that when the QA/QC/test team acknowledges it, that the rpm is automatically signed by a special harbour-app only key.
Possibly a warning could be shown if rpm installs are attempted without key or with a bad key.
| | 2 | No.2 Revision |
harbour Harbour app rpms to be signed by a dedicated key
As talked about here, it appears that the signing of harbour app rpms is left to the app provider.
Better would be that when the QA/QC/test team acknowledges it, that the rpm is automatically signed by a special harbour-app only key.
Possibly a warning could be shown if rpm installs are attempted without key or with a bad key.
| | 3 | No.3 Revision |
Harbour app rpms to be signed by a dedicated key
As talked about here, it appears that the signing of harbour app rpms is left to the app provider.
Better would be that when the QA/QC/test team acknowledges it, that the rpm is automatically signed by a special harbour-app only key.
Possibly a warning could be shown if rpm installs are attempted without key or with a bad key.
Edit: Since there's an "untrusted software" option, it should just force to fail installing rpm if the signature is missing.