[SOLVED] Private key not found on dev machine
Published: March 12, 2018 - 10:33
Hello,
I am currently testing the new version 1.5 (RC1). The server is running Debian, and the development machine is running Windows 10, as is the management console PC.
On the development PC, I can't import packages or modify the machine's configuration (in fact, the "Check for updates" and "Start installations" buttons are grayed out). Each time, a window opens with the message:
"Private key does not exist."
I can't understand why it can't find the key, even though it's located in c:\private, as indicated in the documentation, and it's correctly entered in the files c:\Program Files (x86)\wapt\wapt-get.ini and appdata\local\waptconsole\waptconsole.ini. However,
in my appdata\roaming\waptconsole|waptconsole.ini, I only have settings related to the console's graphical interface, and in appdata\roaming\wapt, I only have a waptsession.sqlite file.
Note: I haven't enabled authentication. Kerberos, for now.
If someone could shed some light on this...
I know this version is brand new, and it's normal that the documentation isn't perfect yet, but I'd like to make a suggestion: it would be helpful to have a clear and precise description of the security system implemented in this new version (user authentication, machine authentication, with or without Kerberos...). It could be useful.
Thanks for your work
.
I am currently testing the new version 1.5 (RC1). The server is running Debian, and the development machine is running Windows 10, as is the management console PC.
On the development PC, I can't import packages or modify the machine's configuration (in fact, the "Check for updates" and "Start installations" buttons are grayed out). Each time, a window opens with the message:
"Private key does not exist."
I can't understand why it can't find the key, even though it's located in c:\private, as indicated in the documentation, and it's correctly entered in the files c:\Program Files (x86)\wapt\wapt-get.ini and appdata\local\waptconsole\waptconsole.ini. However,
in my appdata\roaming\waptconsole|waptconsole.ini, I only have settings related to the console's graphical interface, and in appdata\roaming\wapt, I only have a waptsession.sqlite file.
Note: I haven't enabled authentication. Kerberos, for now.
If someone could shed some light on this...
I know this version is brand new, and it's normal that the documentation isn't perfect yet, but I'd like to make a suggestion: it would be helpful to have a clear and precise description of the security system implemented in this new version (user authentication, machine authentication, with or without Kerberos...). It could be useful.
Thanks for your work
.