From: jfcolom <jfcolom@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] x11vnc password is always in clear text, and clients are unable to connect with password
Date: Sun, 31 Dec 2023 09:15:11 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48007@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1331 bytes --]
New issue by jfcolom on void-packages repository
https://github.com/void-linux/void-packages/issues/48007
Description:
### Is this a new report?
Yes
### System Info
Void 6.6.8_1 x86_64 GenuineIntel uptodate rrFFFFF
### Package(s) Affected
x11vnc-0.9.16_6
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
It works ok in Debian bullseye
### Expected behaviour
`x11vnc` can generate a password file with the option `storepasswd` among others. The password should be stored obfuscated or encrypted. In addition, `vncviewer` should be able to connect to the server when the correct password is set.
### Actual behaviour
The password is always stored in clear text.
In addition, vncviewer always get "Authentication failure: password check failed!", even when the correct password is set.
### Steps to reproduce
1. Run x11vnc to generate a password:
`x11vnc -storepasswd`
2. Input and verify the password
3. See the generated file
`cat $HOME/.vnc/passwd`
The password should appear obfuscated or encrypted. In addition, `vncviewer` should be able to connect when the correct password is set. However, the password is in clear text and the client cannot connect, even when the password is properly set in the client (tested with client from tigervnc package)
next reply other threads:[~2023-12-31 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-31 8:15 jfcolom [this message]
2024-02-01 1:11 ` onlylunix
2024-02-20 6:11 ` dexgs
2024-02-20 6:26 ` dexgs
2024-02-20 15:32 ` dexgs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48007@inbox.vuxu.org \
--to=jfcolom@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).