tigervnc server can't generate SSL certificate
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tigervnc (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Kubuntu 22.04, tigervnc-common 1.12.0+dfsg-4 amd64
What happens:
When I start tigervncserver with option -SecurityTypes X509Plain it reports the following error:
vncserver -geometry 1920x1080 -localhost no -autokill -SecurityTypes X509Plain
You will require a certificate to use X509None, X509Vnc, or X509Plain.
I will generate a self signed certificate for you in /home/mb/
-----
Cannot write random bytes:
4057E14E287F000
The openssl command /usr/bin/openssl req -newkey ec:/etc/
which seems plausible since it can't write to /dev/urandmon.
What should happen:
vncserver creates a self signed certifiate and starts.
Workaround (fix?) is to comment out the following line in /etc/tigervnc/
#RANDFILE = /dev/urandom
This bug was fixed in the package tigervnc - 1.12.0+dfsg-7
---------------
tigervnc (1.12.0+dfsg-7) unstable; urgency=medium
[ Joachim Falk ] <host>: <display# >.{log, pid} file location for :<display# >-<rfbport# >.{log, pid} or :<display# >-<rfbunixpath> .{log,pid} can also be used if multiple erver are running for the display (closes: #1025458). erver. on-obsolete- package libgl1-mesa-dev (>= 9.2) => libgl-dev on-obsolete- package libegl1-mesa-dev [linux-any kfreebsd-any] => libegl-dev
* Fixed autogeneration of SSL certificates for X509None, X509Vnc, and
X509Plain security types (LP: #1973292).
* Fixed /tmp copy lifetime of VNC password, certificate, and key files in
case of disabled autokill (LP: #1995869).
* Document ~/.vnc/config in man pages (closes: #1025459).
* Fixed bug concerning relative -rfbunixpath option values for
tigervncserver and x0tigervncserver.
* Consistent ~/.vnc/
tigervncserver. In case of x0tigervncserver,
<host>
<host>
x0tigervncs
* Document -rfbunixpath and -rfbunixmode options for tigervncserver and
x0tigervncs
* Fixed Lintian warnings
- build-depends-
- build-depends-
* Activated libunwind for armel, armhf, and arm64 after bug #923962 has
been fixed on those architectures.
-- Joachim Falk <email address hidden> Sat, 28 Dec 2022 17:26:29 +0100