Displaying 20 results from an estimated 1000 matches similar to: "sshd does not exit after scp (hpux 11.00 / ssh 2.1.1p1)"
2001 Aug 03
1
Disconnecting: protocol error: rcvd type 98
When I SSH using protocol 1 from a Debian box running OpenSSH 2.9p2-4
to a sparc.sunos5 box running vanilla OpenSSH 2.9.1, after a little
while (of inactivity?) I get the following message on the client
terminal:
Disconnecting: protocol error: rcvd type 98
Looking further, this message is actually caused by the SSH daemon.
However, I'm at a loss to determine why sshd is doing this.
I attach
2001 Mar 30
4
linux tcsetattr failed
does anyone else see this on linux:
localhost sshd[14418]: Accepted password for stevesk from 15.126.45.158 port 49594
localhost sshd[14418]: Setting tty modes failed: Invalid argument
redhat with kernel 2.2.17.
ttymodes.c:
/* Set the new modes for the terminal. */
if (tcsetattr(fd, TCSANOW, &tio) < 0)
log("Setting tty modes failed: %.100s", strerror(errno));
return;
2001 Aug 27
1
scp1 issue
Hi.
I hope this is not entirely inappropriate, I have tried
comp.security.ssh but have not received any response, anyhow
I am wondering how scp1 really works, as far as I can tell it should be
quite straight forward, just send
version string
CMSG_SESSION_KEY
CMSG_USER
CMSG_AUTH_PASSWORD
CMSG_EXEC_CMD
And wait for SMSG_STDOUT_DATA until SMSG_EXITSTATUS.
I have read the scp.c code and and it more
2000 Dec 28
2
sshd doesn't log which RSA key was used
Hi guys,
and another feature request for sshd which I would classify as really
useful. And I think this behaviour is currently not available (If yes,
sorry, I must have missed it):
> I believe that the sshd should log which RSA key was used to connect to
> an account. When there are a number of keys in the authorized_keys file
> it is often useful to know which one was used for each
2001 Jan 10
1
SSH2/1 Failure when using bash shell, other shells work
Got a strange problem here. We have OpenSSH 2.3.0p1 running on a variety of
machines and on one particular Redhat 6.2 machine(all patches applied) we
run into a situation where it will not allow us to start a shell when using
bash or bash2. csh and others work fine.
One note...if I enable PermitRootLogin, the user root IS allowed to login
with bash. This is very strange. I'm guessing it
2000 May 26
4
openssh-2.1.0p2 ans Solaris 8
I have some troubles with subj and proper utmpx/wtmpx functionality.
After successfull ssh connect to Solaris 8 box, I run
#w
11:59am up 13:45, 1 user, load average: 0.00, 0.01, 0.02
User tty login@ idle JCPU PCPU what
root console 11:43am 9 bash
#
Record about my pts/1 login is absent. Next command I run from Solaris 8
console
2001 Oct 25
2
SIGCHLD race *trivial* patch
Yes, this is a patch against an older version of OpenSSH with other
stuff anyways, BUT, it's so TRIVIAL(*), that you can see how it would
apply to newer versions (which I've not tried).
Here's the gist: server_loop2() has a race condition with respect to
reception of SIGCHLD and checking/setting child_terminated. This patch
does two things: wait_until_can_do_something() adds a 1
2001 Aug 20
1
Idletimeout patch, third attempt
Here is my third attempt at the idletimeout patch. I tried to address
the points which Marcus Friedl brought up.
It is actually bigger than the previous patches, but not as intrusive.
It is big because it moves some stuff from serverloop.c to packet.c.
- I moved all the logic to packet.c. This means that I also had to move
the actual select() call, which used to be in serverloop.c to packet.c.
2000 Jun 28
4
openssh-2.1.1p1 on Debian slink and potato
Just today I compilied openssh-2.1.1p1 on Debian Slink and Potato both to come out with the same problem.
I am compiling them with openssl-0.9.5a.. The configure line I use for openssh is below:
./configure --sysconfdir=/etc/ssh --prefix=/usr --with-ssl-dir=../openssl-0.9.5a
So I compile, do a make install restart the sshd daemon and everything seems fine.
Then when I do a w at the prompt
2000 Nov 22
2
fds closed after SIGCHLD bug still in newest version (fwd)
can someone confirm this? it does not happen on openbsd.
-------------- next part --------------
An embedded message was scrubbed...
From: Florian Wunderlich <fwunderlich at devbrain.de>
Subject: Re: fds closed after SIGCHLD bug still in newest version
Date: Wed, 22 Nov 2000 14:44:17 +0100
Size: 3926
Url:
2004 Feb 09
1
nedit syntax highlighting patterns for R?
I tried to install the syntax pattern file, R-5.1.pats (obtained from
www.nedit.org)
in version 5.3 of nedit, but it gives the following errors. Does
anyone have a
more up-to-date copy?
euclid: ~/nedit % nedit -import R-5.1.pats
NEdit: language mode must be specified in highlight pattern:
<==
NEdit: style name required in style specification:
Note:darkRed:Italic
<==
NEdit: expecting
2000 Jul 03
1
Antwort: Re: sshd does not exit after scp (hpux 11.00 / ssh 2.1 .1p1)
Hi,
stevesk at sweden.hp.com wrote:
> Has any progress been made on this issue? I've included an older
> message that has a stack trace, which if I recall was still the same in
> 2.1.1p1. I can provide a newer trace or additional information if
> needed.
not really... On a non-trusted system with HP AnsiC it seems to work if
changing shutdown(fdin, SHUT_WR) to shutdown(fdin,
2002 Oct 10
1
NEdit Highligth patterns for R
Hi
I've just submitted to the NEdit development team a R highligth patterns
for NEdit (www.nedit.org).
NEdit is a text editor for LINUX which I use to write small R functions.
In my opinion is a very good tool for small scripts, maybe for huge
projects is not the best.
I'm attaching the R-5.1.pats file so you can try it.
As usual contributions and comments are welcome.
Regards
EJ
2014 Apr 01
1
BUG dovecot and nginx
we have setup a two level proxy configuration for our zimbra server:
[ dovecot 2.2.12 (imap proxy mode) ]
V
[ nginx (imap proxy mode) ]
V
[ zimbra imap server]
and it does not work ... after tying a login, the connection just
hangs and ends after 30 seconds with a timeout.
- if I try again rightaway in the same dovecot connection, the login
goes though without trouble.
2001 Apr 11
1
openssh 2.5.2p2/Solaris 5.8 problems
openssh 2.5.2p2 on Solaris 8 has PAM/cron problems. If I build it with PAM
then cron quits working giving "cron audit problem." errors. If I turn
PAM off then cron works but I get kicked out of any session where a password
is needed (i.e. no .rhosts/.shosts or not using ssh-agent) with the message
"Connection closed by IP#". I get through if I have a .rhosts/.shosts or use
2002 Jun 26
2
debug output when ssh'ing a remote host
Hi list,
I'm not sure whether this (see below) is a "bug" or a feature but as I cannot find any information on this neither in the INSTALL file nor via ./configure --help or somewhere else, I would like to ask you whether there is an answer to my question.
Thanx a lot & kind regards - have a nice day,
B. Courtin
Question:
---------
I lately updatet from OpenSSH 3.0.1p1 to
2001 Nov 26
2
Named pipe connections and stdout
All,
I am trying to use a named pipe to steer R from an external application.
Following the examples in RNEWS 1:1, I have created a simple listener:
zz <- fifo("TESTFIFO", "r")
repeat
{
a <- readLines(zz)
if(length(a) != 0)
{
e <- try(eval(parse(text = a)))
if (inherits(e,
2000 Jan 07
2
possible clue on tcp forwarding problems
When I encounter the problem with TCP port forwarding locking up, I'll
see this on the client window (if I haven't invoked ssh with -q):
chan_shutdown_read failed for #1/fd6: Transport endpoint is not connected
chan_shutdown_read failed for #1/fd6: Transport endpoint is not connected
This is with Blowfish encryption. I have to kill and restart the client
when this happens.
Phil
2000 Jul 11
0
persistant err message "tvp!=NULL"
=== not on the list, please cc ===
Greetings. I've STFW, and I've realy not seen any reference to this.
Recently I changed from loglevel info to loglevel debug. After I did that, I
started getting a PLETHERA of odd logs. I changed back to LogLevel INFO, but
I do stil get these messages, which kinda worry me:
Jul 11 10:10:13 cabal sshd[26003]: debug: tvp!=NULL kid 0 mili 10
Jul 11
2000 Dec 27
0
'debug1: tvp!=NULL kid 0 mili 10' messages
Since 2.4 is approaching, I'll raise a question that's been bugging me...
I prefer to run all my sshd's with LogLevel DEBUG. I'm just a paranoid
control freak ;) Anyway, for as long as I can remember openssh's sshd
spits out 'tvp!=NULL kid 0 mili 10' (or very minor variations) continuously
when LogLevel DEBUG is used. Looking at serverloop.c it looks like this