|
Bugzilla – Full Text Bug Listing |
| Summary: | VNC Remote Access via X11: spaces in password don't work but no hint given by YaST | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Forgotten User Drfk9mafMw <forgotten_Drfk9mafMw> |
| Component: | YaST2 | Assignee: | Marcus Schaefer <ms> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Minor | ||
| Priority: | P5 - None | CC: | max, security-team, snwint |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Forgotten User Drfk9mafMw
2006-09-19 12:34:06 UTC
Yes, AFAIK it is a restriction in Xvnc. So this needs to be detected in YaST2. IMHO this is a minor issue. I guess this doesn't only need to get fixed in YaST, but in linuxrc as well. Reassigned to maintainer of linuxrc Xvnc not supporting spaces in passwords sounds like grotesque nonsense to me. More likely I'd suspect a quoting issue in one of the shell scripts used to setup vnc. Hmm, I don't think so. The startup script does the following: $VNCPASS /root/.vnc/passwd "$VNCPassword" The variable $VNCPassword is an exported variable from the linuxrc environment and is never touched in the scripts. The contents are directly passed to the program $VNCPASS = /usr/bin/vncpasswd.arg So I assume a problem with the space handling in the vncpasswd.arg which is part of the tightvnc package. Assigning to maintainer of tightvnc By the way setting spaces in a password is a bad idea at all I think you guys are all running into the wrong direction. As I understand Daniel, the problem didn't happen on a VNC installation, but in an installed system, when during the X configuration he checked the box to export the local display via VNC. So linuxrc the installation system are certainly out of the loop here. I also tested vncpasswd.arg with passwords containing spaces, and didn't see any problems with it. So, my guess is, that the password gets truncated at the first space by YaST or SAX when it is queried from the user before it gets written to the disk. BTW, what's wrong with spaces in passwords? It's a regular character that shouldn't cause any problems. The only characters I would discourage people from using in passwords are umlauts, because they might be hit by encoding problems. @ c0mment #6: Yes, this is exactly what I mean... I was already looking up information about linuxrc and couldn't come up with a reason for why it should be related to the problem but blaimed my average Linux user skills for not understanding... And yes, I use spaces and other chars extensively in other (regular) passwords since I think it makes things much more secure :) aha, we are talking about the installed system ;) ok first of all the initial report is correct. A space in the password string confuses sax2 because the shell which is invocing the createVNC.sh script is called like this: /usr/share/sax/libsax/createVNC.sh 123 123 so only the first portion of the passowrd is used. Additionally this is a security problem because you can pass a shell quoted command as password which is executed. Both issues have been fixed |