1. Forum
  2. USENET
  3. comp.security.ssh

  • Putty 0.81 logging appears broken

    From Chris Townley@news@cct-net.co.uk to comp.security.ssh on Thu May 2 17:32:22 2024
    From Newsgroup: comp.security.ssh

    With Putty 0.81 no Windows 11, when I select to log to a file, then open
    the session, no log file is created.

    The file I chose is in a directory that my Windows user has full access to.

    Any ideas?
    --
    Chris
    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From Simon Tatham@anakin@pobox.com to comp.security.ssh on Fri May 3 10:24:00 2024
    From Newsgroup: comp.security.ssh

    Chris Townley <news@cct-net.co.uk> writes:

    With Putty 0.81 no Windows 11, when I select to log to a file, then
    open the session, no log file is created.

    What do you see in the terminal window, or the PuTTY Event Log?

    If I tell PuTTY to log to a file in a directory it _can't_ access, then
    in the terminal window I see a message such as

    Error writing session log (raw mode) to file: z:\putty.log

    and the same error message appears at the bottom of the Event Log.

    On the other hand, when you _do_ successfully enable logging, nothing
    appears in the terminal window, but the Event Log contains a message
    indicating successful opening of the log file:

    2024-05-03 10:22:47 Writing new session log (raw mode) to file: z:\putty.log

    So, which of those do you see? That will tell us whether PuTTY _knows_
    it failed to write the file, or whether the Windows API claimed
    everything worked fine.
    --
    import hashlib; print((lambda p,q,g,y,r,s,m: (lambda w:(pow(g,int(hashlib.sha1( m.encode('ascii')).hexdigest(),16)*w%q,p)*pow(y,r*w%q,p)%p)%q)(pow(s,q-2,q))==r and s%q!=0 and m)(12342649995480866419, 2278082317364501, 1670428356600652640, 5398151833726432125, 645223105888478, 1916678356240619, "<anakin@pobox.com>")) --- Synchronet 3.21b-Linux NewsLink 1.2
  • From Chris Townley@news@cct-net.co.uk to comp.security.ssh on Fri May 3 10:50:26 2024
    From Newsgroup: comp.security.ssh

    On 03/05/2024 10:24, Simon Tatham wrote:
    Chris Townley <news@cct-net.co.uk> writes:

    With Putty 0.81 no Windows 11, when I select to log to a file, then
    open the session, no log file is created.

    What do you see in the terminal window, or the PuTTY Event Log?

    If I tell PuTTY to log to a file in a directory it _can't_ access, then
    in the terminal window I see a message such as

    Error writing session log (raw mode) to file: z:\putty.log

    and the same error message appears at the bottom of the Event Log.

    On the other hand, when you _do_ successfully enable logging, nothing
    appears in the terminal window, but the Event Log contains a message indicating successful opening of the log file:

    2024-05-03 10:22:47 Writing new session log (raw mode) to file: z:\putty.log

    So, which of those do you see? That will tell us whether PuTTY _knows_
    it failed to write the file, or whether the Windows API claimed
    everything worked fine.

    Initially I got no message, then changing what I logged from SSH packets
    and raw data to just SSH packets it then reported Error writing session log.
    I then created a file (to be overwritten) and checked the security on
    it, and the whole tree. Same result.

    I have just tried again, but using My Windows Documents folder. It
    created the file, and logged fine. SO in future I will do this

    I was initially using a .ssh directory in c:\Users\Chris\ which has
    always worked for me before.

    Strange.

    Thanks for the reply
    --
    Chris

    --- Synchronet 3.21b-Linux NewsLink 1.2