Just want to let you know that I can confirm this bug too. WindowsXP
client with Xfce4.8 as desktop on the server.
--
Free Software Download: Index, Search & Analyze Logs and other IT data in
Real-Time with Splunk. Coll
Dear list,
I am testing the 1.1 pre-beta (2/21/11) 64 bit Linux binary on an Ubuntu
Natty machine. According to previous posts, I start the VNC server as:
./Xvnc :4 -SecurityTypes=VeNCrypt,Plain -PlainUsers=sebastiaan
pam_service=vnc
which works fine when connecting with:
./vncviewer :4
differently.
Anyway, is there any way to make a construction to authenticate against
a module with root-only readable configuration file as a normal user?
(different than inetd/xdm, which does not have the features I need for
this group of users).
Sincerely,
Sebastiaan
tip, authentication is working great now!
Sincerely,
Sebastiaan
--
Free Software Download: Index, Search & Analyze Logs and other IT data in
Real-Time with Splunk. Collect, index and harness all the fast moving IT
Hi,
On 02/25/2011 11:16 PM, Martin Koegler wrote:
> On Fri, Feb 25, 2011 at 09:52:48AM +0100, Sebastiaan Breedveld wrote:
>> Unfortunately, the radius configuration file contains a sectret
>> string to authenticate against the Radius server, so it should not
>> be world
ecks wether VeNCrypt type or none is specified. (That is, I am in
the assumption that the VeNCrypt type does not use the vnc password.)
Greetings,
Sebastiaan
--- /usr/bin/vncserver2011-01-24 00:23:33.0 +0100
+++ vncserver2011-03-01 10:34:01.0 +0100
@@ -121,7 +121,7 @@
# C
tive) "VncAuth". If either of those
> conditions is true, then and only then should vncserver check for the
> existence of the VNC password.
>
Are you sure about that? If I run:
vncserver
and then connect, vncviewer still tries to authenticate with VncAuth.
I am using the Linux
dds --rfbauth automatically,
so a more structural change is necessary:
- if no options are given, force VeNCrypt, and do not use --rfbauth anymore
- force VeNCrypt by specifying SecurityTypes, and do not use --rfbauth
in that case
O
ensitive) "VncAuth". If either of those
> conditions is true, then and only then should vncserver check for the
> existence of the VNC password.
>
Then how does it work? If I start:
Xvnc :10
then I read on the server:
client requests security type VeNCrypt
but the client tries to
present by default. It is also not trivial to make one since each
distribution has its own way of configuring pam. I would suggest to
default to /etc/pam.d/vnc if present, otherwise use /etc/pam.d/login
(which is present on all systems).
Sebastiaan
Robert
On 03/01/2011 08:10 AM, Sebastiaan
This patch needs another line modified, to display the option when run
with vncserver -h.
The second patch is for the man-page (I have not updated the date of the
page, I will leave that to you).
Index: unix/vncserver
===
--- unix/
) In addition to the above:
4. do not create .vnc/passwd if -Password, -PasswordFile or -rfbauth is
already given.
Thinking about -Password: is there any sane environment where this is
still used?
Greetings,
Sebastiaan
.
Therefor I like to specify a display range that inetd can use. The
following patch allows an optional argument for inetd:
Xvnc -inetd 20-100; % uses displays 20-100
Xvnc -inetd; % uses the default 1-99
Greetings,
Sebastiaan
Ps: while testing incorrect input, I noticed that incorrect input is
ignored
> I opened
> https://sourceforge.net/tracker/?func=detail&aid=3198439&group_id=254363&atid=1126848
> to track this issue because I don't have time for it right now.
>
> Regards, Adam
>
Greetings,
Sebastiaan
---
/home/sebastiaan/tigerbuild/tigervnc-1.0.90/unix/xse
Will the new beta also include this patch? I am not able to build for
windows systems to test the patch, but I have users which can test the
windows viewer binary.
Greetings,
Sebastiaan
--
Free Software Download
How can one use quotation marks in inetd? When called from inetd, the
quotation marks are ignored.
Greetings,
Sebastiaan
--- ../../../../unix/xserver/hw/vnc/xvnc.cc2011-02-21
16:05:15.0 +0100
+++ xvnc.cc2011-03-03 21:23:51.128076509 +0100
@@ -78,6 +78,11 @@
#include "input
On 03/03/2011 09:34 PM, Sebastiaan Breedveld wrote:
Hi,
Here is another patch. It adds a -resolutions argument with a list of
resolutions to add to the default list:
Xvnc -resolutions "1264x900 1400x1500"
Of course this is a more flexible approach than specifying only 1 with
the
On 03/03/2011 01:18 PM, Adam Tkac wrote:
> On Thu, Mar 03, 2011 at 01:11:22PM +0100, Sebastiaan Breedveld wrote:
>> > 2) When using the VeNCrypt security type, the ~/.vnc/passwd is not
>>>> necessary, yet the user is asked to create one. Same when using the
>>&g
anyway. This issue holds me up from letting more of my users
work with TigerVNC and test it.
Robert
+1 for some fix in the 1.1 release. The client is pretty useless now
when using TLS. I do not think that a beta release should be released
with known bugs.
Sebastiaan
On 03/09/2011 05:13
does not increase the loop counter, and leaves it up to the
if-statements below if the added argument makes sense.
Now the patch, as attachment ;) Last time I have been on a mailing list,
attachments were rejected (yes, it has been a long time since).
Sebastiaan
--- vncserver 2011-03-10 08:41
$0 -kill :$displayNumber)
>> " . "edString($desktopLog) . " 2>&1 &");
+}
Seems like a wrongly patched file, as both strings now contain a
kill. The attached patch should fix it.
The new behaviour should only be invoked when add
ix this in the beta. But attention should be payed later.
Greetings,
Sebastiaan
--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organi
On 03/15/2011 08:29 PM, DRC wrote:
> On 3/15/11 4:48 AM, Sebastiaan Breedveld wrote:
>> 1) The new vncserver script does something weird with -fg. When I use
>> this switch, xfce4 refuses to start with:
>>
>> "Unable to contact settings server. Failed to connect t
On 03/16/2011 09:59 PM, Eric Stadtherr wrote:
On Wed, 16 Mar 2011 15:50:53 -0500, DRC wrote:
http://www.virtualgl.org/DeveloperInfo/TigerVNCPreReleases
-- Reverts default behavior of vncserver but adds a 'vncserver
-autokill' option that will automatically kill Xvnc whenever xstartup exits.
On 03/16/2011 09:50 PM, DRC wrote:
> http://www.virtualgl.org/DeveloperInfo/TigerVNCPreReleases
>
> -- Reverts default behavior of vncserver but adds a 'vncserver
> -autokill' option that will automatically kill Xvnc whenever xstartup exits.
>
Builds fine, runs fine (Linux 64). No comments from me
On 05/19/2011 11:46 AM, Pierre Ossman wrote:
> On Fri, 04 Mar 2011 10:07:09 +0100
> Sebastiaan Breedveld wrote:
>
>> On 03/03/2011 09:34 PM, Sebastiaan Breedveld wrote:
>>> Hi,
>>>
>>> Here is another patch. It adds a -resolutions argument with a list of
client again?
So, when you are at work, you have the high-speed setting, but at home
(if you have the session at work still running), you can deceide to not
send (high-speed network) updates to the other client.
Greetings,
Sebastiaan
---
27 matches
Mail list logo
