search for: logverbose

..."Connection closed" message that is present > in the debug log you sent is not making to to your syslog. If I change LogLevel in /etc/ssh/sshd_config from default INFO to VERBOSE then I see 'Connection closed' message but also others which I don't want. I also tried 'LogVerbose packet.c:sshpkt_vfatal():*' and even 'LogVerbose *:sshpkt_vfatal():*' (both with 'LogLevel INFO') but none worked. Regards, Opty

...age that is present > > in the debug log you sent is not making to to your syslog. > > If I change LogLevel in /etc/ssh/sshd_config from default INFO to > VERBOSE then I see 'Connection closed' message but also others which I > don't want. > > I also tried 'LogVerbose packet.c:sshpkt_vfatal():*' and even > 'LogVerbose *:sshpkt_vfatal():*' (both with 'LogLevel INFO') but none > worked. What version OpenSSH are you using? Are you building from source or are you using a vendor/distribution packaging? It's possible that someone else ha...

...; in the debug log you sent is not making to to your syslog. > > > > If I change LogLevel in /etc/ssh/sshd_config from default INFO to > > VERBOSE then I see 'Connection closed' message but also others which I > > don't want. > > > > I also tried 'LogVerbose packet.c:sshpkt_vfatal():*' and even > > 'LogVerbose *:sshpkt_vfatal():*' (both with 'LogLevel INFO') but none > > worked. > > What version OpenSSH are you using? Are you building from source or are > you using a vendor/distribution packaging? It's possi...

...they can be easily associated. >> >> The FQDN might be too long, though -- perhaps just the PID >> with an additional line associating it with the host would be >> a better fit? > > it's a bit of a hack, but you can get PID in debug messages right now > using LogVerbose=*, though you'll probably need to set it in ssh_config > if you're using ProxyJump as options from the command-line are mostly > not passed to the subordinate ssh processes. Thanks for the idea -- but that means having write access to sshd_config and (potentially) disturbing all othe...

...e seen so far. > It's not a configuration we test, so you're mostly on your own to debug it. It's entirely possible there's a bug there; if so, I'd expect it to be something like a fd being closed while devcrypto is still depending on it. > > I'd suggest turning on LogVerbose=* so you can see which process (represented by it's PID) is doing what, though that probably won't be represented in the devcrypto debug messages unless you hack something similar in. Too bad, I was hoping it was a tested/supported configuration. Since that doesn't seem to be the case,...

...f the originating host, so that they can be easily associated. > > The FQDN might be too long, though -- perhaps just the PID > with an additional line associating it with the host would be > a better fit? it's a bit of a hack, but you can get PID in debug messages right now using LogVerbose=*, though you'll probably need to set it in ssh_config if you're using ProxyJump as options from the command-line are mostly not passed to the subordinate ssh processes. -d

...ated. >>> >>> The FQDN might be too long, though -- perhaps just the PID >>> with an additional line associating it with the host would be >>> a better fit? >> >> it's a bit of a hack, but you can get PID in debug messages right now >> using LogVerbose=*, though you'll probably need to set it in ssh_config >> if you're using ProxyJump as options from the command-line are mostly >> not passed to the subordinate ssh processes. > > Thanks for the idea -- but that means having write access to sshd_config > and (potential...

On Sun, 26 May 2024, Opty wrote: > On Wed, May 22, 2024 at 6:29?AM Damien Miller <djm at mindrot.org> wrote: > > On Tue, 21 May 2024, Opty wrote: > > > Hello, > > > > > > can anyone confirm that OpenSSH server doesn't log client disconnect > > > without SSH_MSG_DISCONNECT? > > > > OpenSSH logs the disconnection regardless of

...not making to to your syslog. > > > > > > If I change LogLevel in /etc/ssh/sshd_config from default INFO to > > > VERBOSE then I see 'Connection closed' message but also others which I > > > don't want. > > > > > > I also tried 'LogVerbose packet.c:sshpkt_vfatal():*' and even > > > 'LogVerbose *:sshpkt_vfatal():*' (both with 'LogLevel INFO') but none > > > worked. > > > > What version OpenSSH are you using? Are you building from source or are > > you using a vendor/distribution...

...mination was. > > E.g. why shouldn't we log connections that drop because the peer > > process got SIGINT or the TCP connection dropped before sending a > > SSH2_MSG_DISCONNECT? > > I will wait for the final verdict then. Thanks for letting me know. I will also try 'LogVerbose serverloop.c:process_input():*' soon which might do here. Regards, Opty

...2024 at 6:03?AM Damien Miller <djm at mindrot.org> wrote: > > > We need to decide whether to promote these log messages to INFO. > > > > > > [...] > > > > I will wait for the final verdict then. Thanks for letting me know. > > I will also try 'LogVerbose serverloop.c:process_input():*' soon which > might do here. A bit chatty but works: 2024-06-14T20:01:54.084176+02:00 qeporkak sshd 10012 - - Accepted keyboard-interactive/pam for opty from 127.0.0.1 port 60547 ssh2 2024-06-14T20:01:54.090845+02:00 qeporkak elogind-daemon 1116 - - New sessi...

...djm at mindrot.org> wrote: > > > > We need to decide whether to promote these log messages to INFO. > > > > > > > > [...] > > > > > > I will wait for the final verdict then. Thanks for letting me know. > > > > I will also try 'LogVerbose serverloop.c:process_input():*' soon which > > might do here. > > A bit chatty but works: > > 2024-06-14T20:01:54.084176+02:00 qeporkak sshd 10012 - - Accepted > keyboard-interactive/pam for opty from 127.0.0.1 port 60547 ssh2 > 2024-06-14T20:01:54.090845+02:00 qeporka...

http://bugs.freedesktop.org/show_bug.cgi?id=18336 Summary: nv10 : doesn't detect connected dvi monitor Product: xorg Version: 7.3 Platform: Other OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

...have the same problem as described by Dmitry a day ago in a topic similar. I am able to use x11 with base driver "nv" but when I load "nvidia" driver, startx simply crash my machine and reboot after 5 seconds. I have a similar log file as reported by Dmitry even using startx+logverbose option. XF86Config file is similar,except it is not the same nvidia video card. I use a Geforce 256. X was working well before using nvidia driver with 4.8 stable. I even run this driver on freebsd-current for almost a year. Normally, I can set this driver easily, even on freebsd current releas...

...44 --- a/readconf.c +++ b/readconf.c @@ -156,7 +156,7 @@ typedef enum { oGlobalKnownHostsFile, oUserKnownHostsFile, oConnectionAttempts, oBatchMode, oCheckHostIP, oStrictHostKeyChecking, oCompression, oTCPKeepAlive, oNumberOfPasswordPrompts, - oLogFacility, oLogLevel, oLogVerbose, oCiphers, oMacs, + oLogFacility, oLogLevel, oLogPath, oLogVerbose, oCiphers, oMacs, oPubkeyAuthentication, oKbdInteractiveAuthentication, oKbdInteractiveDevices, oHostKeyAlias, oDynamicForward, oPreferredAuthentications, oHostbasedAuthentication, @@ -271,6 +271,7 @@ s...

...E-0050048383C9}" fixme:msi:MsiEnableLogA 00001596 "C:\\windows\\temp\\Office XP Professional Setup(0013)_Task(0001).txt" 00000000 fixme:msi:MsiInstallProductW L"Z:\\media\\cdrecorder\\FILES\\OSP\\1033\\OSP.MSI" L"LAUNCHEDFROMSETUP=1 SETUPEXEPATH=Z:\\media\\cdrecorder\\ LOGVERBOSE=1 DWSETUPLOGFILE=C:\\windows\\temp\\Office XP Professional Setup(0013).txt DWMSILOGFILE=C:\\windows\\temp\\Office XP Professional Setup(0013)_Task(0001).txt REBOOT=ReallySuppress" fixme:msi:HANDLE_CustomType1 DATABASE NOT THREADSAFE... not starting fixme:msi:HANDLE_CustomType1 DATABASE NOT THR...

http://bugs.freedesktop.org/show_bug.cgi?id=26577 Summary: [regression] Black screen with X on NV11 and NV31 Product: xorg Version: git Platform: All OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

...or handling is confusing it. It's not a configuration we test, so you're mostly on your own to debug it. It's entirely possible there's a bug there; if so, I'd expect it to be something like a fd being closed while devcrypto is still depending on it. I'd suggest turning on LogVerbose=* so you can see which process (represented by it's PID) is doing what, though that probably won't be represented in the devcrypto debug messages unless you hack something similar in. On Tue, 8 Oct 2024, Peter Rashleigh wrote: > Hi All, > > I'm having an issue where SSH sess...

I've got a usecase right now where I've got to use a few intermediate ProxyJump hosts, and it would help debugging via -v tremendously if the debug lines would have a prefix of the originating host, so that they can be easily associated. The FQDN might be too long, though -- perhaps just the PID with an additional line associating it with the host would be a better fit? Thanks!

On Wed, Jun 5, 2024 at 6:03?AM Damien Miller <djm at mindrot.org> wrote: > On Sat, 1 Jun 2024, Opty wrote: > > Indeed I am. > > > > What now? > > We need to decide whether to promote these log messages to INFO. > > > Should PuTTY change its 'perfectly OK to unceremoniously > > slam the connection shut when you're done' attitude? > >