Your message dated Sat, 07 Aug 2021 13:27:04 +0200
with message-id <[email protected]>
and subject line Bug#337900: fixed in tightvnc 1:1.3.9-9 or before
has caused the Debian Bug report #337900,
regarding About tightvnc passwords
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
337900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=337900
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: tightvnc
Severity: wishlist
Hi
On Sun, Nov 06, 2005 at 08:04:11PM -0500, Andy Teijelo Pérez wrote:
> El Domingo, 6 de Noviembre de 2005 4:01, Ola Lundqvist escribió:
> > Hello
> >
> > I do not know anything about such a function.
>
> I found a man page here http://www.tightvnc.com/vncpasswd.1.html
>
> > Yes it is in the vnc-common package as they are identical (or at least
> > extremely similar).
> >
>
> Following the links in the tightvnc website I downloaded their source code
> from
> http://kent.dl.sourceforge.net/sourceforge/vnc-tight/tightvnc-1.2.9_unixsrc.tar.bz2
>
> after building it vncpasswd indeed asks for both passwords. After setting
> them, the tightvncserver package I had installed worked as expected. The
> first password it asks gives complete control of the Xvnc server and the
> second one only lets you view the server.
> After that, to be sure I was using the same source of my installed packages I
> downloaded the source from
> ftp://ftp.de.debian.org/debian/pool/main/t/tightvnc/tightvnc_1.2.9.orig.tar.gz
>
> and everything worked the same way.
Very interesting. I was not aware that there were any difference. Thanks a lot
for the information.
> >
> > This has been the case for several years and I have not changed it
> > lately. So you may have used something else than Debian in this case, or?
> >
> Well, if you say so, then I was, for sure, not using Debian.
>
> Since this doesn't seem to be a licensing problem or some conscious decision,
> is there a possibility that the vncpasswd utility from tightvnc could be
> included? Its behavior is not exactly the same as the one in vnc-common.
> Without it, tightvncserver is lacking a very useful feature. Maybe it could
> be added as a new package or as part of the tightvncserver package, using the
> alternatives mechanism or something similar.
>
> Maybe this is not the right place for this kind of requests, but I think it's
> worth asking.
I fully agree. I'll see if I can add this feature as well.
Adding this as a wishlist bug against the package.
Regards,
// Ola
> Cheers,
> Andy.
> > Regards,
> >
> > // Ola
> >
> > > Regards,
> > > Andy.
>
--
--- Ola Lundqvist systemkonsult --- M Sc in IT Engineering ----
/ [email protected] Annebergsslingan 37 \
| [email protected] 654 65 KARLSTAD |
| http://www.opal.dhs.org Mobile: +46 (0)70-332 1551 |
\ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 /
---------------------------------------------------------------
--- End Message ---
--- Begin Message ---
Source: tightvnc
Source-Version: 1:1.3.9-9
On Mon, 7 Nov 2005 06:28:38 +0100 Ola Lundqvist <[email protected]>
wrote:
> Package: tightvnc
> Severity: wishlist
>
> Hi
>
> On Sun, Nov 06, 2005 at 08:04:11PM -0500, Andy Teijelo Pérez wrote:
[...]
> > after building it vncpasswd indeed asks for both passwords. After
> > setting them, the tightvncserver package I had installed worked as
> > expected. The first password it asks gives complete control of the
> > Xvnc server and the second one only lets you view the server.
> > After that, to be sure I was using the same source of my installed
> > packages I downloaded the source from
> >
ftp://ftp.de.debian.org/debian/pool/main/t/tightvnc/tightvnc_1.2.9.orig.tar.gz
> > and everything worked the same way.
[...]
"The first password it asks gives complete control of the Xvnc server
and the second one only lets you view the server."
This functionality exists in vncpasswd packaged with tightvncserver at
least since version 1:1.3.9-9, most probably in considerably older
versions. I am closing this bug as fixed therefore.
Sven
--
GPG Fingerprint
3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585
signature.asc
Description: This is a digitally signed message part
--- End Message ---
