Displaying 20 results from an estimated 700 matches similar to: "compiler warnings about format strings"
2001 Sep 28
1
openssh-2.9.9p2 assumes pid_t, uid_t, etc. are not 'long'
openssh-2.9.9p2 assumes that pid_t, uid_t, gid_t, and mode_t are no
wider than int. GCC complains about this assumption on 32-bit Solaris
8 sparc, where these types are 'long', not 'int'. This isn't an
actual problem at runtime on this host, as long and int are the same
width, but it is a problem on other hosts where pid_t is wider than
int. E.g., I've heard that 64-bit
2000 Nov 08
1
internal error: we do not read, but chan_read_failed
Hello,
The error message in the subject line occurs with the new 2.3.0 openssh
version and appeared in the previous snapshots on our Solaris systems. As far
as I remember it was reported, but have not seen any more about this. I have
looked into it a little bit.
First, the file session.c (line 1849 onwards):
debug("session_exit_message: release channel %d", s->chanid);
2001 Jul 09
1
sshd problem on Solaris 7: Control-C hangs shell
I have a strange problem with sshd (from openssh-2.9p2) on Solaris 7. My shell is bash. When I open an ssh session , and type a Control-C to bash's prompt, the shell hangs. (But, if I for instance run "sleep 10" (during which time the pty is in cooked mode) and press Control-C, the sleep command is interrupted quite normally, and the bash prompt returns.)
Adding some debugging
2008 May 30
1
"ERR sshd: error: no more sessions" issue
Initially send this mail to user group. then realized this is more apt
place. Apologies for posting in both groups...
Hi all,
We're using openssh version 4.7p on our linux 2.6-22 kernel.
We have a Java based GUI that opens a secure shell connection to this linux box.
To do something over the connection, the GUI opens a session (some
times 3-4 simultaneous sessions) & once done, it will
2001 Jun 12
0
small patch to session.c
In the following code snippit from session.c:
void
session_close_by_pid(pid_t pid, int status)
{
Session *s = session_by_pid(pid);
if (s == NULL) {
debug("session_close_by_pid: no session for pid %d", s->pid);
return;
}
if (s->chanid != -1)
session_exit_message(s, status);
session_close(s);
}
2000 Nov 12
0
scp problems?
Hi. So I have been having problems using scp to copy
files between two of my machines, both of which are running OpenSSH
2.30p1 (though I've had the same problem with previous versions).
It is basically as simple as the file not being transferred after
authentication occurs. I can however use scp to copy files back and
forth from another machine using a SSH Communications version
2000 Oct 27
1
Typo in 2.2.0p1 ??
I don't already figure out what is the real impact of this but I think there is
a typo in function sigchld_handler() in serverloop.c (l 75).
It is written
if (WIFEXITED(child_wait_status) ||
WIFSIGNALED(child_wait_status))
child_terminated = 1;
child_has_selected = 0;
But I think one actually means:
if (WIFEXITED(child_wait_status) ||
WIFSIGNALED(child_wait_status)) {
2006 Apr 23
1
[Bug 1185] remote ssh command runs very slow on windows 2003
http://bugzilla.mindrot.org/show_bug.cgi?id=1185
Summary: remote ssh command runs very slow on windows 2003
Product: Portable OpenSSH
Version: 4.3p2
Platform: Other
OS/Version: Cygwin on NT/2k
Status: NEW
Severity: major
Priority: P2
Component: sshd
AssignedTo: bitbucket at mindrot.org
2002 May 09
0
functions : server_input_channel_req userauth_pubkey
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Greetings,
I am not sure if this is the correct place to ask these question,
if I am at the wrong place please advise.
I am currently working on some modifications to openssh
which record the users rsa/dsa identity comment file to
a log file when the user logs in (password authentication
is disabled).
The ssh1 portion of the modification works
2006 Apr 22
3
[Bug 1184] remote ssh command runs very slow on windows 2003
http://bugzilla.mindrot.org/show_bug.cgi?id=1184
Summary: remote ssh command runs very slow on windows 2003
Product: Portable OpenSSH
Version: 4.3p2
Platform: Other
OS/Version: Cygwin on NT/2k
Status: NEW
Severity: major
Priority: P2
Component: sshd
AssignedTo: bitbucket at mindrot.org
2006 Nov 22
10
[Bug 1264] Channel not close by sshd Server
http://bugzilla.mindrot.org/show_bug.cgi?id=1264
Summary: Channel not close by sshd Server
Product: Portable OpenSSH
Version: 4.3p2
Platform: Other
OS/Version: HP-UX
Status: NEW
Severity: critical
Priority: P2
Component: sshd
AssignedTo: bitbucket at mindrot.org
ReportedBy: ajain at hp.com
2002 Mar 29
1
Two patches for OpenSSH 3.1p1 (fwd)
Can I get people from other platforms to test the waitpid.patch to see
if it solves hang-on-exit on their platform?
I can confirm Solaris at this moment (but I've not done heavy testing at
this moment) that is works like a charm (Solaris 7). It handles 'sleep
90&' vs 'nohup sleep 90&' correctly (killed, vs left).
thanks.
- Ben
---------- Forwarded message
2001 Mar 25
2
Bug in bsd-waitpid.c and bsd-nextstep.c
Hi!
The handling of the "status" information in bsd-waitpid.c and bsd-nextstep.c
seems to be bit odd. Patch attached.
Best regards,
Lutz
--
Lutz Jaenicke Lutz.Jaenicke at aet.TU-Cottbus.DE
BTU Cottbus http://www.aet.TU-Cottbus.DE/personen/jaenicke/
Lehrstuhl Allgemeine Elektrotechnik Tel. +49 355 69-4129
Universitaetsplatz
2002 Mar 26
1
Two patches for OpenSSH 3.1p1
Please find enclosed two patches for OpenSSH 3.1p1.
The first patch solves a problem where sessions will be left "hanging"
when you normally exit from a ssh shell (for example by logging out from
the remote host via "exit" or "logout"). The problem seems to be that sshd
(and some other parts of OpenSSH) doesn't check the return code and errno
from waitpid() for
2000 Sep 28
1
[PATCH] Next cleanup part 4 or 5 by now.=)
Changes:
* Removed utimes() posix hack since scp.c moved to utimes()
* Fixed waitpid() to be more proper. It was driving me nuts.
* Made setsid() a #define in next-posix.h
* Removed WCOREDUMP() from next-posix.h since we really don't support
it and now #ifdef .. #else .. #endif around the single place it was
used.
* Fixed typecasting issue in sshd.c with sizeof() returning "long
2002 Apr 05
1
[Bug 100] serverloop.c modifications for correct UNICOS behavior
http://bugzilla.mindrot.org/show_bug.cgi?id=100
------- Additional Comments From mouring at eviladmin.org 2002-04-06 06:52 -------
The following code was committed to OpenSSH to catch some SysV issue. Does
this keep UNICOS happy?
while ((wait_pid = waitpid(-1, &wait_status, 0)) < 0)
if (errno != EINTR)
packet_disconnect("wait:
2002 Oct 11
2
Why openssh newer than 2.9.9 doesn't send SIGTERM and SIGHUP to child process?
Hi,
I search in archive list if there any reason why is removed in openssh
newer than 2.9.9 from function
'void session_close_by_channel(int id, void *arg)' sending of SIGTEMR and
SIGHUP signals to child as was in 2.9.9 version? See follow sniped code
from 2.9.9 sources:
---- openssh-2.9.9/session.c ----------------------------------------
void
session_close_by_channel(int id, void
2007 Oct 22
0
Intermittently stalling PAM authentication children
Hi,
we encounter a problem using PAM with privsep to manage OPIE
authentication : in some -- not really reproducible -- cases, the
child responsible of PAM authentication stalls and continues to run
even if its parent has been closed. The server is the standard RHEL 4
install, which is a 3.9p1 with backported security patches
As this children account for the 'MaxStartups' limit, new
2001 Oct 29
2
pam_open_session w/o tty on Solaris
Hello, all-
Apparently, under Solaris (I can personally confirm SunOS 5.7 and 5.8),
pam_open_session will generate a segfault if PAM_TTY is not set. The
obvious symptom of this is that OpenSSH 2.9.9p2 will segfault on any
operation that does not request a tty (do_exec_no_pty).
Based on a quick google search, this seems to have been encountered
by others, though the specific symptoms seem to
2001 Jan 29
1
Solaris wtmpx patch
Hi,
Solaris (tested with 2.6) needs a username in the logout record in the wtmpx
file. Currently openssh (version 2.3.0p1) leaves the username (utmpx.ut_user)
empty in logout records, which leads to conflicting results from the last
command. Example:
# last -5 siegert
siegert pts/186 stikine.ucs.sfu. Mon Jan 15 14:26 still logged in
siegert pts/105 stikine.ucs.sfu. Mon Jan 15