Dear List,
Having recently resurrected my info file using the kernel parameter info=file:///info I get prompted (by linuxrc?) to enter a VNC password. The info file on the initrd has this:
install: ... autoyast: ... loghost: .... vnc: 1 vncpassword: thepassword
And in addition the kernel command line includes:
append initrd=initrd splash=silent showopts install=... autoyast= ... vnc=1 vncpassword=thepassword info=file:///info
(without the line-breaks of course.)
Can anyone see what I am doing wrong?
Ian Grant wrote:
Dear List,
Having recently resurrected my info file using the kernel parameter info=file:///info I get prompted (by linuxrc?) to enter a VNC password. The info file on the initrd has this:
install: ... autoyast: ... loghost: .... vnc: 1 vncpassword: thepassword
And in addition the kernel command line includes:
append initrd=initrd splash=silent showopts install=... autoyast= ... vnc=1 vncpassword=thepassword info=file:///info
(without the line-breaks of course.)
Can anyone see what I am doing wrong?
Hi Ian,
I guess it's a new rule with 10.2. I can reproduce this, but only if the VNC password I chose is less than 8 characters. I don't recall this password checking before.
HTH,
Lee
On Tue, 30 Jan 2007, Lee Mayes wrote:
Ian Grant wrote:
Dear List,
Having recently resurrected my info file using the kernel parameter info=file:///info I get prompted (by linuxrc?) to enter a VNC password. The info file on the initrd has this:
install: ... autoyast: ... loghost: .... vnc: 1 vncpassword: thepassword
And in addition the kernel command line includes:
append initrd=initrd splash=silent showopts install=... autoyast= ... vnc=1 vncpassword=thepassword info=file:///info
(without the line-breaks of course.)
Can anyone see what I am doing wrong?
Hi Ian,
I guess it's a new rule with 10.2. I can reproduce this, but only if the VNC password I chose is less than 8 characters. I don't recall this password checking before.
Yes, there was a bug about this. I was asked to change the check from > 5 to 8 chars. Meanwhile I doubt that's justified and it will be likely > 6 (which seems to be the correct limit) in 10.3.
Steffen
On Tue, 30 Jan 2007 14:24:39 -0500 Lee Mayes autoinst@mayeses.com wrote:
Ian Grant wrote:
Dear List,
Having recently resurrected my info file using the kernel parameter info=file:///info I get prompted (by linuxrc?) to enter a VNC password. [...]
I guess it's a new rule with 10.2. I can reproduce this, but only if
the VNC password I chose is less than 8 characters. I don't recall this password checking before.
Thanks, that's interesting. The password I am using is 10 characters and it passes cracklib-check. ... I should have said that this password is OK if it's only in the options on the kernel command line. So if you are right then the checking is only being done for passwords specified in the info file, not ones on the kernel command line, which is a bit weird ...
On Thu, 1 Feb 2007, Ian Grant wrote:
On Tue, 30 Jan 2007 14:24:39 -0500 Lee Mayes autoinst@mayeses.com wrote:
Ian Grant wrote:
Dear List,
Having recently resurrected my info file using the kernel parameter info=file:///info I get prompted (by linuxrc?) to enter a VNC password. [...]
I guess it's a new rule with 10.2. I can reproduce this, but only if
the VNC password I chose is less than 8 characters. I don't recall this password checking before.
Thanks, that's interesting. The password I am using is 10 characters and it passes cracklib-check. ... I should have said that this password is OK if it's only in the options on the kernel command line. So if you are right then the checking is only being done for passwords specified in the info file, not ones on the kernel command line, which is a bit weird
That's not true. And there's no max length check either.
You get the prompt either if the password is too short or there is none set at all. Maybe your info file is not read? Press ^C, then 'i' in linuxrc to see current config and look for 'vncpassword'.
Steffen
On Thu, 1 Feb 2007 11:56:11 +0100 (CET) Steffen Winterfeldt snwint@suse.de wrote:
You get the prompt either if the password is too short or there is none set at all. Maybe your info file is not read?
Thanks. It seems the problem was having both vnc=1 vncpassword=... on the kernel command line as well as the vnc: 1 and VNCPassword: ... in the info file. Taking everything except info=file:///info off the kernel command line and putting everything in the info file fixed it. (The reason I had both command line parameters and entries in the info file is that I started running out of blank CDs when I was setting this up for the first time a few years ago, so I put everything everywhere!)
Press ^C, then 'i' in linuxrc to see current config and look for 'vncpassword'.
Ooh, magic! I'll try this next time I have a problem.
Cheers Ian
autoinstall@lists.opensuse.org
-
Ian Grant -
Lee Mayes -
Steffen Winterfeldt