feat(vncscreen component): added missing handling for serververificat…

[blackcow1987]

…ion event

Looking at the example code of novnc, it was developed to handle the serververification event when using RA2ne authentication, but react-vnc lacks the corresponding code, so it was added.

        UI.rfb.addEventListener("serververification", UI.serverVerify);

https://github.com/novnc/noVNC/blob/master/app/ui.js#L1085

    async serverVerify(e) {
        const type = e.detail.type;
        if (type === 'RSA') {
            const publickey = e.detail.publickey;
            let fingerprint = await window.crypto.subtle.digest("SHA-1", publickey);
            // The same fingerprint format as RealVNC
            fingerprint = Array.from(new Uint8Array(fingerprint).slice(0, 8)).map(
                x => x.toString(16).padStart(2, '0')).join('-');
            document.getElementById('noVNC_verify_server_dlg').classList.add('noVNC_open');
            document.getElementById('noVNC_fingerprint').innerHTML = fingerprint;
        }
    },

https://github.com/novnc/noVNC/blob/master/app/ui.js#L1214

Description

Describe your PR here.

Resolved issues

Closes #1

Before submitting the PR, please take the following into consideration

• It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. If you don't have an issue, please create one.
• Prefix your PR title with feat: , fix: , chore: , docs:, or refactor:.
• The description should clearly illustrate what problems it solves.
• Ensure that the commit messages follow our guidelines.
• Resolve merge conflicts (if any).
• Make sure that the current branch is upto date with the main branch.

[roerohan]

Current PR looks good, but an additional feature was requested. Not sure if that is needed though, please let me know accordingly.

[roerohan]

Currently the fingerprint is only logged, it would be better if we could expose the fingerprint (if present) by forwarding the ref to the parent component, so that the fingerprint can be programmatically verified if needed.

The easiest way to do it in my opinion is to assign it to the RFB object (if it has a rfb.fingerprint field?) or just on the VNCScreenHandle object.

P.S. I'm not sure the fingerprint needs to be used by a client in any scenario, but I assume that's the purpose of it - to make sure the fingerprint is in accordance with the VNC server

[roerohan]

I added support for react 19, which has caused some conflicts in the PR. Sorry for the inconvenience, it would be great if you could resolve the merge conflicts.

[blackcow1987]

I have found that RSA type connections fail if this event is not handled. I found this issue while testing with RealVNC. I will solve the conflicts :)