@julien-f Thank you very much I've updated to the latest commit and can confirm the behaviour has stopped, the prompt fix is much appreciated.

@Danp Sorry for the delay, in the end I waited for a nother commit to come out and update to it, once I'd done so the issue was fixed. Thanks for your help either way.

@Danp I just tried doing the web package but it's not made any difference it's not a big deal as I know the actual packages are getting updated but just something I noticed and wanted to share. Makes sense if no commits to the XO-WEB service have been made as you say.

Hi Everyone,

Just recently updated to the latest commit and noticed the commit number in XOA hasn't changed:
If I go to about I see the below:

I thought my script may have just failed so I reran it but I'm on the (as of writing) current commit:

Any ideas, is this just broken? I restarted the service manually just to be sure.

@julien-f Thank you very much I've updated to the latest commit and can confirm the behaviour has stopped, the prompt fix is much appreciated.

@peder Hi Peder,

Yes it returns 2048 and I also ran the reset XAPI command (the hosts have been physically rebooted since I did it as well).

The little error icon warning about having a short pubkey is also gone since I updated the certificates.

Hello,

I'm a long time user of Xen Orchestra and have made great use of these forums as a resource in the past currently using the from the sources version of orchestra on commit: 8f6c0 I've noticed the audit log plugin is now reporting thousands of API calls when a user is logged in for: host.isPubKeyTooShort

I noticed this was part of the work to get ready for XCP-NG 8.3 and I've already updated the pubkey on my hosts but this is still getting spammed in the logs and is drowning out any actual use they would have to effectively audit user activity which is frustrating as they used to work fine.

Any help in turning this off or looking at chaning how this is logged would be appreciated.