Re: [noVNC] snap package & arm64 (raspberrypi 4b)

[Pierre Ossman]

On 08/12/2024 13:14, Martine & Philippe vont à la mer Martineke wrote:
> hello
>
> i wanted to install novnc via snap, but unfortunately it tells me that
> there is no package for arm64.
> how can we get around this?
>

The snap is unfortunately only built for x86. So either do a normal,
non-snap, install, or try to build the snap yourself on your Raspberry Pi.

Regards,
--
Pierre Ossman Software Development
Cendio AB https://cendio.com
Teknikringen 8 https://twitter.com/ThinLinc
583 30 Linköping https://facebook.com/ThinLinc
Phone: +46-13-214600

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

[Martine & Philippe vont à la mer Martineke]

Hi

so I did an installation from github and it works fine and it's very stable.
but to respect the advice to switch to https, I generated my certificates and I therefore launch via the following order:

/etc/novnc/noVNC-master/utils/novnc_proxy --vnc localhost:5900 --cert /home/martineke/certif/mtk.crt --key /home/martineke/certif/mtk.key --listen 6081

This seems to work since I get:

WebSocket server settings:
  - Listen on: 6081
  - Webserver. Web root: /etc/novnc/noVNC-master
  - SSL/TLS support
  - proxying from :6081 to localhost:5900

and if I come to https, the client waits for me to type the passphrase used to generate the certificate on the server. (enter PEM passphrase)

is this because I'm not using a snap command for this launch?(ARM64)

or that my certificates are imperfect? for example domain-certificate instead of certificate for a server?

greetings

[Pierre Ossman]

On 15/01/2025 18:10, Martine & Philippe vont à la mer Martineke wrote:
>
> and if I come to https, the client waits for me to type the passphrase used
> to generate the certificate on the server. (enter PEM passphrase)
>
> is this because I'm not using a snap command for this launch?(ARM64)
>
> or that my certificates are imperfect? for example domain-certificate
> instead of certificate for a server?
>

That is because your certificate (techincally, the key for it) was
configured with a password to protect it. Normally you generate server
certificates without any protecting key, for the reasons you've discovered.

You should be able to remove the password using your certificate tools.

Regards,
--
Pierre Ossman Software Development

Cendio AB http://cendio.com
Teknikringen 8 http://twitter.com/ThinLinc
583 30 Linköping http://facebook.com/ThinLinc

[Martine & Philippe vont à la mer Martineke]

Thanks.

now it works fine.

other question :

### Additional websockify features
* Daemonizing: When the `-D` option is specified, websockify runs
  in the background as a daemon process.

this option is unknow in noVNC. 

is it systematically sent by noVNC to websockify?

greetings

[Pierre Ossman]

On 16/01/2025 16:16, Martine & Philippe vont à la mer Martineke wrote:
> Thanks.
> now it works fine.
>
> other question :
>
> ### Additional websockify features
> * Daemonizing: When the `-D` option is specified, websockify runs
> in the background as a daemon process.
>
> this option is unknow in noVNC.
> is it systematically sent by noVNC to websockify?
>

No, the novnc_proxy always runs websockify in the foreground and waits
for it to exit.

Regards,
--
Pierre Ossman Software Development

Cendio AB https://cendio.com
Teknikringen 8 https://twitter.com/ThinLinc

583 30 Linköping https://facebook.com/ThinLinc