similar to: Fwd: PAM_RHOST set to "UNKNOWN" when running in inetd mode without IP socket

This is actually something I had on my mind to write about in the past few -stable and alpha releases, but did not get to and instead always patched myself. Now having updated to the latest snapshot (which may be released as beta1), I stumbled on it again: In src/auth/passdb-pam.c, where the client host is passed to PAM, the code looks like this: #ifdef PAM_RHOST const char *host =

Hi and here's an feature request from a user/developer, wher I would like to hear your comments again. Thanks > The PAM_RHOST item, which tells PAM which remote host it is conversing > with, is currently set by OpenSSH _after_ authentication is made. This > is not a good thing for me, as a have written a module which needs the > IP of the peer as a part of authentication. >

On Thu, 2014-01-30 at 11:25 -0500, Dan Swartzendruber wrote: > Hopefully I'm not out to lunch here. I ported tftp-hpa to our proprietary > OS, VOS (at stratus.com). We've always runs the old legacy tftpd from > inetd, so I wanted to continue doing so with tftp-hpa. It seems to work > okay, but I noticed that the code in tftpd.c has a 'while (1)' loop that > has

> Correct. Like most UDP-based inetd services, tftpd is intended to be run in 'wait' mode. When the first request arrives, inetd starts the service but does not read the incoming packet (it can't, because it has no way to pass it along to the server). After that, inetd ignores that socket until the server exits. This isn't critical for tftp, but it does help to keep down the

On 01/30/2014 10:25 AM, Jeffrey Hutzelman wrote: > > Correct. Like most UDP-based inetd services, tftpd is intended to be > run in 'wait' mode. When the first request arrives, inetd starts the > service but does not read the incoming packet (it can't, because it has > no way to pass it along to the server). After that, inetd ignores that > socket until the server

Hopefully I'm not out to lunch here. I ported tftp-hpa to our proprietary OS, VOS (at stratus.com). We've always runs the old legacy tftpd from inetd, so I wanted to continue doing so with tftp-hpa. It seems to work okay, but I noticed that the code in tftpd.c has a 'while (1)' loop that has this at the end: /* * Now that we have read the request packet from

A little problem, which is bugging me: when using PAM authentication, Dovecot (0.99.5) does not set the PAM_RHOST item, so the PAM modules cannot know who the client is. We need this for some PAM module doing access control. Changing passdb-pam.c to pam_set_item it seems trivial, but I'm bugged as to how to get the client name from there. It seems not to be available in the auth_request

Hey.. I'm finding that I can force dovecot (setup in inetd mode) into a wedged state by spamming it with carrage returns. As I've not had enough time to familiarize myself with the code.. I thought I'd ping the list before 1.0 is christened. -Phil.

Hi. Inetd mode is broken as of cvs-20051111 After logging in on POP3 port imap binary is started. Seems like somehow master process receives wrong protocol id and thus starts wrong binary. -- ./lxnt

Environment: Solaris 2.5.1 Samba 1.9.18p3 We run samba from inetd (no special reason - just how its been done in the past). Then on one server we got masses of Samba daemons running (up to 40 as a time trying to run - load average 40+!), giving following complaints: Sep 28 14:39:06 zeus.brunel.ac.uk smbd[10728]: standard input is not a socket, a ssuming -D option Sep 28 14:39:06

I'm trying to start SAMBA from the inetd. I have added the port numbers to /etc/services: netbios-ns 137/udp netbios-ssn 139/tcp To my inetd.conf I have added: netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd After this I killed any samba-prosecces, and refreshed the inetd with:

It would seem I didn't test this thoroughly enough before I sent my email. I can reproduce the problem (same openssh version) on both Solaris 8 and Solaris 6. (I had thought it was only on Solaris 8.) I haven't checked to see if it exists on other versions of Solaris, but the problem does not exist however on RedHat 6.2 running the same openssh version. I hope that helps. Adam Benjamin

> ?????? wrote: > > Hello Sir/Madam! > > my name is dae su kim! > i have a problem diffcult! > The problem is samba process smbd and nmbd no responsing! > This log is my problem! > help me! please help me! > > problem : SAMBA_2.0.7 > > 7 03:13:48 cad1 inetd[179]: netbios-ns/udp server > failing > 7 03:27:03 cad1

Hello, My apologies if this is a known "feature" and I'm simply reporting something already known. The situation is this: - the sshd in openssh-2.3.0p1 (and also previously in openssh-2.1.1p4) fail when invoked via inetd on Solaris 8 - the sshd is invoked with: 1) an entry in /etc/services: sshback 10000/tcp sshdback # SSH Back Door 2) an entry

Hello, we would like to use rsync (2.6.2 manualy patched and recompiled) in daemon mode spawned by inetd (Solaris 5.8 Environment). /etc/services: rsync 1234/tcp #RSYNC daemon /etc/inet/inetd.conf: rsync stream tcp nowait publish /usr/bin/rsync rsyncd --daemon --port 1234 . Alas, this does not seem to work, there is the following error message in the log file:

Hi samba friends, I'm upgrading our Samba 2.2.8a server to 3.6.15 on a Solaris 9 box, we need to do this as all our latest Mac OS X 10.8 clients cannot map to the 2.2.8a network share, and need the newer Samba (well known issue for mountain lion). I've compiled 3.6.15 and this seemed to go ok, no obvious errors were shown during .configure make and make install, and smbd -V gives

Hello. I know that it is recommended to run smbd as a standalone daemon and to avoid inetd. Can you please tell me why inetd is discouraged and what problems it imposes? Also, I have one user who is having problems accessing her personal files on a MacOSX 10.3.2 via smb. Any ideas what may be causing it? Judy Lin NACS-DCS

Is there any option for dovecot to exit when is unneded? I mostly use dovecot via shell process (ie. something like /usr/sbin/dovecot --exec-mail imap) But sometimes I want to use it remotely via tcp and I run dovecot via inetd. --8<---------------cut here---------------start------------->8--- localhost:imap stream tcp nowait root /usr/sbin/tcpd

I was searching for help on Mandrake's site and got nowhere other than seeing this really weird help-page loop where it showed the pages you could go to, BUT would not show any information from the page.... Just use the search from www.mandrake.com to see this strangeness.... No helpful... Anyway.. trying to run drakconf and startup services to start either inetd or xinetd seems to be

Have a system admin who would like to stop running inetd on his Solaris 9 system. Currently the only thing left in his /etc/inet/inetd.conf file is: 100134/1 tli rpc/ticotsord wait root /usr/lib/krb5/ktkt_warnd ktkt_warnd Does anyone know if they can remove this without causing any problems?