similar to: openssh and DOS

this patch adds a LogFile option to sshd_config. it just logs messages directly to a file instead of stderr or syslog. the largest change is an additional argument to log_init() in log.c for the log file name (and then changes to the rest of the tools to add a NULL arg). galt -------------- next part -------------- diff -urN openssh-3.5p1-orig/log.c openssh-3.5p1/log.c ---

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

I added a few features to openssh for my local use that I think would be more broadly useful. I basically added access control lists to control who would be allowed public key authentication. I added four config file entries for the server: PubkeyAllowUsers PubkeyDenyUsers PubkeyAllowGroups PubkeyDenyGroups These follow the same sematics as the already existing entries for

Hi, I ran across a case in which my server maintenance was simplified by using SSHD configuration options like this in sshd_config: AllowGroups admin at 192.168.0.* sshuser in much the same fashion as (Allow|Deny)Users. In this case, the goal is to provide access to administrators only from the local network, while allowing SSH users to login from anywhere. This (IMHO) simplifies access

The following patch allows OpenSSH 2.2.0-p1 to be started (and managed) from /etc/inittab (by "init") on systems which support that. This is useful when you *really* want SSHD to always run since it will be automatically restarted by "init" if it dies (and if "init" dies the the systems dies :-). I use a line (in /etc/inittab) like this on Solaris systems:

The primary purpose of the attached patches is for portable OpenSSH to support changing expired passwords as specified in shadow password files. To support that, I did a couple enhancements to the base OpenBSD OpenSSH code. They are: 1. Consolidated the handling of "forced_command" into a do_exec() function in session.c. These were being handled inconsistently and allocated

Hi What if you have sysv signals (i.e. signal is restored when handler is called) and child process exits here? Zombie will be left, because SIGCHLD is ignored at that point. Shouldn't signal be before waitpid? Mikulas static void main_sigchld_handler(int sig) { int save_errno = errno; pid_t pid; int status; while ((pid = waitpid(-1, &status, WNOHANG))

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

A short while ago, I looked at using the AllowUsers configuration option in openssh (v3.8p1 , but I believe this to be unchanged in 3.9p1) to restrict access such that only specific remote machines could access specific local accounts. I swiftly discovered that a) specifying wildcarded IP numbers to try to allow a useful IP range was pointless: if I specified AllowUsers joe at

> We also spotted these sql connections getting aborted, upon upgrading MySQL from 5.6 to 5.7. (Going back to 5.6 we don't see them!) I have a mailserver running MySQL 5.6.44 which is not very busy that logs these warnings. Another busy one running MySQL 5.6.45 does not log any warnings. MySQL interactive-/wait_timeout is 28800 (8 hours), which is more than enough time to wait for a

I will top post here ... got a similar issue with mariadb a while ago after upgrading from 10.1 to 10.2 lots of warnings about aborted connections in the logs. after digging into this issue the culprit was a new default setting value in the newer maridb server. during the update the log_warnings changed from 1 to 2 therefore showing lots of aborted connection notices in the logs changing

Hello. I noticed that OpenSSH 2.1.1p3 does not check whether it is being called as rlogin or slogin, like it's siblings do. This can get ugly if you have rlogin and rsh symlinked to ssh, and old r* commands are moved off in another place, as I do. Since Solaris rsh is hardcoded to call /usr/bin/rlogin, it will get stuck in an infinite loop. Below is a quick patch I hacked up, based on

I have a few patches for AIX. The patchfile is attached below. The patch has been tested on AIX4.2 and AIX4.3. The patch is on openssh-1.2.1pre25, with openssl-0.94, using RSAref. 1) authenticate support - this function allows the system to determine authentification. Whatever the system allows for login, authenticate will too. It doesn't matter whether it is AFS, DFS, SecureID, local.

Dear all, I have made patch for samba-2.0.7/source/smbd/conn.c This will, instead of using by-directional link, use array for managing connections. # The patch does seems to work on my RHL6.1Ja(fixed) version of # Linux machine. I don't know about other OS/Architecture. This should work better then original because: 1) The original code used bitmap.c for looking empty area. But using

I've attached a patch for openssh-SNAP-20001028 which fixes the following two problems: 1) I fixed fixpaths to complain instead of failing silently if it can't write the output file. 2) I changed log-server.c to use av0 as the first argument to openlog(). I also made sure it called openlog() before the TCP wrapper stuff, because libwrap calls syslog() and winds up using the

If one is using the pidfile as an indicator of sshd's status, it is possible to kill sshd before the sigterm handler gets installed, since the pidfile is written out before the signal handlers are setup. The solution is to simply write the pidfile after the signal handlers are setup. Here's the patch. Rob --- sshd.c.orig Fri Jun 22 11:16:41 2001 +++ sshd.c Fri Jun 22 11:18:32 2001 @@

Hi, If sshd is started with 'sshd', restarting with kill -HUP will fail. I've included the most obvious patch, but making sure that the full pathname is in saved_argv[0] just might be more secure. Cheers, Han Holl --- sshd.c.orig Mon Feb 19 10:55:54 2001 +++ sshd.c Mon Feb 19 10:56:15 2001 @@ -208,7 +208,7 @@ { log("Received SIGHUP; restarting.");

Dear R list, Please, could someone help me with SSQ decomposition and contrasts. Below my data, graphic, ANOVAs and my doubt: # Data a = paste('a', gl(3, 8), sep='') b = paste('b', gl(2, 4, 24), sep='') tra = sort(paste('t', rep(1:6, 4), sep='')) y = c(26.2, 26.0, 25.0, 25.4, 24.8, 24.6, 26.7, 25.2, 25.7, 26.3, 25.1, 26.4, 19.6,

# Dear R list, # # A have a doubt about SSQ decomposition and contrasts with ANOVAs. # So, I would like a tip from more advanced R users. # Below my data, the basic script and my doubts: # Data r = paste('r', gl(3, 8), sep='') e = paste('e', rep(gl(2, 4), 3), sep='') tra = sort(paste('t', rep(1:6, 4), sep='')) y = c(26.2, 26.0, 25.0, 25.4,

Nguyen Cao Dat asked about this: ERROR! Out of file structures - perhaps increase MAX_OPEN_FILES? As it happens I have started getting them too - on a PC Application server - the cause seems to be lots of files needed to be open to run applications - Lotus apps seems to be a particular culprit, but experiments indicate that even opening help on Microsoft Word opens 13 files! MAX_OPEN_FILES