search for: 20205

hi, mutt -f imap://max at test.local@127.0.0.1 Could not connect to 127.0.0.1 (Connection refused). lsof -i dovecot 20200 root 5u IPv4 233361 TCP localhost:imap2 (LISTEN) imap-logi 20204 dovecot 0u IPv4 233361 TCP localhost:imap2 (LISTEN) imap-logi 20205 dovecot 0u IPv4 233361 TCP localhost:imap2 (LISTEN) imap-logi 20206 dovecot 0u IPv4 233361 TCP localhost:imap2 (LISTEN) dovecot --version 1.0.15 dovecot -n # 1.0.15: /etc/dovecot/dovecot.conf log_path: /var/log/dovecot/error.log info_log_path: /var/log/dovecot/info.log log_...

...and secure transport for unattended file transfer and ingestion by applications, at least on Linux. It will have to be replaced by TLS or the Splunk Universal Agent. Pity, that. Mike McManus Principal - Technology Security GTO Security Governance Team - Unix P: He/Him/His AT&T Services, Inc. 20205 North Creek Pkwy, Bothell, WA 98011 michael.mcmanus at att.com -----Original Message----- From: openssh-unix-dev <openssh-unix-dev-bounces+mm1072=att.com at mindrot.org> On Behalf Of MCMANUS, MICHAEL P Sent: Thursday, June 29, 2023 3:06 PM To: openssh-unix-dev at mindrot.org Subject: Subsy...

...segment. start.x.co.ordinate start.y.co.ordinate end.x.co.ordinate end.y.co.ordinate line.colour.value 300 300 2289 20289 2 300 300 2692 20467 1 300 300 3010 20608 2 300 300 2727 19828 1 300 300 2606 20056 2 300 300 16244 21416 1 300 300 16154 21899 2 300 300 16941 21434 1 300 300 17356 20205 2 300 300 16928 21245 1 300 300 16011 21024 2 300 300 17323 20053 1 300 300 17312 20435 2 300 300 17175 21259 1 300 300 16851 21268 2 [[alternative HTML version deleted]]

On 05.07.23 02:50, Damien Miller wrote: > Some possibilities: > 1. the receive.ksh script is faulty in some way that causes it to invoke > sftp-server How would the script even *know* that the client requested the SFTP subsystem? Is a subsystem's executable/path, supposedly internally overwritten with the forced command at that point, exposed through $SSH_ORIGINAL_COMMAND ?

...----- Original Message -------- Subject: Re: [R] Memory leak in R v1.5.1? Date: Wed, 07 Aug 2002 01:12:09 -0400 From: Jan Meyer <janm at mit.edu> To: Peter Dalgaard BSA <p.dalgaard at biostat.ku.dk> References: <Pine.LNX.4.31.0208061713050.2645-100000 at gannet.stats> <3D4FFC7E.20205 at mit.edu> <x2znw0x6wg.fsf at biostat.ku.dk> Hi Peter, right on the point. I had an attach() statement in my function that I was calling frequently. Now after removing all attach() statements in frequently called functions, the problem is completely gone (except for an almost unnoticabl...

...nssh/sftp-server I would almost expect this sort of behavior with the internal-sftp subsystem, but not with an external executable. Can anyone shed some light on this situation? Mike McManus Principal - Technology Security GTO Security Governance Team - Unix P: He/Him/His AT&T Services, Inc. 20205 North Creek Pkwy, Bothell, WA 98011 michael.mcmanus at att.com

...ing mode. Connection from ::1 port 49356 debug1: Client protocol version 2.0; client software version OpenSSH_3.7.1p1 debug1: match: OpenSSH_3.7.1p1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_3.7.1p1 debug2: Network child is on pid 20205 debug3: preauth child monitor started debug3: mm_request_receive entering debug3: privsep user:group 75:75 debug1: permanently_set_uid: 75/75 setuid 75: Operation not permitted debug1: Calling cleanup 0x25008(0x0) For comparision, this is what 3.6.1p1 says (truncated): root# sshd -d -d -d debug2:...

On 05.07.23 18:01, MCMANUS, MICHAEL P wrote: > It appears the forced command either does not run or runs to completion > and exits immediately, as there is no process named "receive.ksh" in > the process tree. FWIW, two cents of mine: -- The script *exiting* should *not* prompt sshd to execute the requested subsystem "as a second thought", or else it'd happen

On 06.07.23 23:37, MCMANUS, MICHAEL P wrote:> So changing the forced command as stated will break the application. I > would need to create a test bed to simulate the listener rather than > use the server as is, where is. That may produce false or misleading > results. Since the forced command is tied to the specific keypair in the authorized_keys, you could -- test with a different

I'm running Samba 3.4.7 on Ubuntu 10.04. This is a recent upgrade and we've starting experience a sporadic problem after this upgrade. When users are browsing through Windows Explorer they sometimes run across folders that appear as unassociated files. This requires the user to click the 'Refresh' button in Windows Explorer to properly see the folders. The files and folders are

Can you send me the config.log? Jean-Marc Le vendredi 13 mai 2005 ? 00:16 +0200, Pierre a ?crit : > Jean-Marc Valin wrote: > > What platform (OS, compiler/version) > > GNU/Linux > kernel 2.6.11.8 > gcc 3.4.3 > > > Also, does it work with no options. > > No, I just tried with just "./configure" and I have the same error. > > -- Jean-Marc

...052: test -s conftest configure:20055: $? = 0 configure:20067: result: yes configure:20169: checking for main in -lwinmm configure:20193: gcc -o conftest -s -O3 -march=i686 conftest.c -lwinmm -lm >&5 configure:20199: $? = 0 configure:20202: test -z || test ! -s conftest.err configure:20205: $? = 0 configure:20208: test -s conftest configure:20211: $? = 0 configure:20224: result: yes configure:20385: checking for short configure:20409: gcc -c -s -O3 -march=i686 conftest.c >&5 configure:20415: $? = 0 configure:20418: test -z || test ! -s conftest.err configure:20421: $? = 0...

...e:20055: $? = 0 > configure:20067: result: yes > configure:20169: checking for main in -lwinmm > configure:20193: gcc -o conftest -s -O3 -march=i686 conftest.c -lwinmm -lm >&5 > configure:20199: $? = 0 > configure:20202: test -z || test ! -s conftest.err > configure:20205: $? = 0 > configure:20208: test -s conftest > configure:20211: $? = 0 > configure:20224: result: yes > configure:20385: checking for short > configure:20409: gcc -c -s -O3 -march=i686 conftest.c >&5 > configure:20415: $? = 0 > configure:20418: test -z || test ! -s c...

...052: test -s conftest configure:20055: $? = 0 configure:20067: result: yes configure:20169: checking for main in -lwinmm configure:20193: gcc -o conftest -s -O3 -march=i686 conftest.c -lwinmm -lm >&5 configure:20199: $? = 0 configure:20202: test -z || test ! -s conftest.err configure:20205: $? = 0 configure:20208: test -s conftest configure:20211: $? = 0 configure:20224: result: yes configure:20385: checking for short configure:20409: gcc -c -s -O3 -march=i686 -O3 -msse conftest.c >&5 configure:20415: $? = 0 configure:20418: test -z || test ! -s conftest.err configure:204...

...22:00~-196.954~80-2~3 20199~Well_80-2~7/7/2000 23:00~-195.938~80-2~3 20200~Well_80-2~7/8/2000 0:00~-195.938~80-2~3 20201~Well_80-2~7/8/2000 1:00~-195.938~80-2~3 20202~Well_80-2~7/8/2000 2:00~-195.938~80-2~3 20203~Well_80-2~7/8/2000 3:00~-195.938~80-2~3 20204~Well_80-2~7/8/2000 4:00~-195.176~80-2~3 20205~Well_80-2~7/8/2000 5:00~-195.176~80-2~3 20206~Well_80-2~7/8/2000 6:00~-195.176~80-2~3 20207~Well_80-2~7/8/2000 7:00~-195.176~80-2~3 20208~Well_80-2~7/8/2000 8:00~-194.160~80-2~3 20209~Well_80-2~7/8/2000 9:00~-194.160~80-2~3 20210~Well_80-2~7/8/2000 10:00~-194.160~80-2~3 20211~Well_80-2~7/8/2000 11:...

On 30/06/2023 09:56, Damien Miller wrote: > It's very hard to figure out what is happening here without a debug log. > > You can get one by stopping the listening sshd and running it manually > in debug mode, e.g. "/usr/sbin/sshd -ddd" Or starting one in debug mode on a different port, e.g. "-p99 -ddd"