Mailing List Archive: conserver: users

Password not passing through

Index | Next | Previous | View Threaded

skoinm at bcm

Jan 18, 2008, 12:25 PM

Post #1 of 3 (1271 views)
Permalink

Password not passing through

Hey folks, I have a new conserver installation that I'm doing and I'm
having a weird issue. What appears to be happening is that the
correct password isn't being passed on through.

Here's the conserver.cf stripped down to show what I'm doing.

### set up global access
default full { rw *; }

### set the defaults for all the consoles
# these get applied before anything else
default * {
# The '&' character is substituted with the console name
logfile /var/conserver/consoles/&;
# timestamps every hour with activity and break logging
timestamp 1hab;
# include the 'full' default
include full;
# master server is localhost
master localhost;
}

default conssh {
type exec;
exec /usr/local/bin/conssh P H;
execsubst P=pd,H=hs;
}

console swift {
port 44;
include conssh;
host cons-2;
}

#########
The /usr/local/bin/conssh script looks like:

#!/bin/sh
PORT=${1}
TERMSRV=${2}
ssh -2 -q -x -t root:ttyS${PORT}@${TERMSRV}

If I run the conssh script with the parameters (/usr/local/bin/conssh
44 cons-2) and put in the password it drops me right in. If I do a
'console swift' it should be doing the same thing. But it asks for
the password and rejects it. I've even tried changing passwords so
that it is using one that doesn't have special characters in it but
that doesn't seem to be it.

Ideas?

Steve
_______________________________________________
users mailing list
users[at]conserver.com
https://www.conserver.com/mailman/listinfo/users

bryan at conserver

Jan 18, 2008, 12:46 PM

Post #2 of 3 (1176 views)
Permalink

Re: Password not passing through [In reply to]

On Fri, Jan 18, 2008 at 02:25:49PM -0600, Steve Koinm wrote:
> If I run the conssh script with the parameters (/usr/local/bin/conssh
> 44 cons-2) and put in the password it drops me right in. If I do a
> 'console swift' it should be doing the same thing. But it asks for
> the password and rejects it. I've even tried changing passwords so
> that it is using one that doesn't have special characters in it but
> that doesn't seem to be it.

things certaily appear ok on the surface. my gut reaction is that there
might be some issue with the pseudo-tty that gets created and mapping of
cr/lf characters. i'd probably add an 'stty -a' to the script so you
can see how things are set in your normal shell (when you run it) as
well as within the pseudo-tty of conserver. if you see anything
"interesting" as far as differences, you could then add those
adjustments to the script. since you tried simple characters, the only
other thing that pops into my mind is the cr/lf mapping features of
ttys.

if anything else hits me, i'll email more...

Bryan
_______________________________________________
users mailing list
users[at]conserver.com
https://www.conserver.com/mailman/listinfo/users

skoinm at bcm

Jan 18, 2008, 2:43 PM

Post #3 of 3 (1182 views)
Permalink

Re: Password not passing through [In reply to]

I'm not seeing anything that I would consider "interesting" between
these two. I did go in and do a stty echok which is the closest thing
to interesting I could find in between the two.

Here is the stty -a from my interactive shell:

Speed 38400 baud; rows 73; columns 129; line = 0; intr = ^C; quit = ^
\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>; eol2 = <undef>;
swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase
= ^W; lnext = ^V; flush = ^O; min = 1; time = 0; -parenb -parodd cs8 -
hupcl -cstopb cread -clocal -crtscts -ignbrk -brkint -ignpar -parmrk -
inpck -istrip -inlcr -igncr icrnl ixon -ixoff -iuclc -ixany -imaxbel -
iutf8 opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0
tab0 bs0 vt0 ff0 isig icanon iexten echo echoe echok -echonl -noflsh -
xcase -tostop -echoprt echoctl echoke

And here is the stty -a from the conssh script:

Speed 38400 baud; rows 0; columns 0; line = 0; intr = ^C; quit = ^\;
erase = ^H; kill = @; eof = ^D; eol = <undef>; eol2 = <undef>; swtch =
<undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W;
lnext = ^V; flush = ^O; min = 1; time = 0; -parenb -parodd cs8 -hupcl -
cstopb cread -clocal -crtscts -ignbrk -brkint -ignpar -parmrk -inpck -
istrip -inlcr -igncr icrnl ixon -ixoff -iuclc -ixany -imaxbel -iutf8
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0
bs0 vt0 ff0 isig icanon iexten echo echoe -echok -echonl -noflsh -
xcase -tostop -echoprt echoctl echoke

Other ideas?

Steve
On Jan 18, 2008, at 2:46 PM, Bryan Stansell wrote:

> On Fri, Jan 18, 2008 at 02:25:49PM -0600, Steve Koinm wrote:
>> If I run the conssh script with the parameters (/usr/local/bin/conssh
>> 44 cons-2) and put in the password it drops me right in. If I do a
>> 'console swift' it should be doing the same thing. But it asks for
>> the password and rejects it. I've even tried changing passwords so
>> that it is using one that doesn't have special characters in it but
>> that doesn't seem to be it.
>
> things certaily appear ok on the surface. my gut reaction is that
> there
> might be some issue with the pseudo-tty that gets created and
> mapping of
> cr/lf characters. i'd probably add an 'stty -a' to the script so you
> can see how things are set in your normal shell (when you run it) as
> well as within the pseudo-tty of conserver. if you see anything
> "interesting" as far as differences, you could then add those
> adjustments to the script. since you tried simple characters, the
> only
> other thing that pops into my mind is the cr/lf mapping features of
> ttys.
>
> if anything else hits me, i'll email more...
>
> Bryan
> _______________________________________________
> users mailing list
> users[at]conserver.com
> https://www.conserver.com/mailman/listinfo/users
>

_______________________________________________
users mailing list
users[at]conserver.com
https://www.conserver.com/mailman/listinfo/users

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com