Re: Putty 0.81 logging appears broken

Path	csiph.com!weretis.net!feeder8.news.weretis.net!newsfeed.xs3.de!nntp-feed.chiark.greenend.org.uk!ewrotcd!.POSTED.chiark.greenend.org.uk!not-for-mail
From	Simon Tatham <anakin@pobox.com>
Newsgroups	comp.security.ssh
Subject	Re: Putty 0.81 logging appears broken
Date	Fri, 03 May 2024 10:24:00 +0100
Message-ID	<81seyz2qq7.fsf@thyestes.tartarus.org> (permalink)
References	<v10f6o$3qpm0$1@dont-email.me>
Mime-Version	1.0
Content-Type	text/plain
Injection-Info	chiark.greenend.org.uk; posting-host="chiark.greenend.org.uk:93.93.131.173"; logging-data="29628"; mail-complaints-to="abuse@chiark.greenend.org.uk"
User-Agent	Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
Cancel-Lock	sha1:ppT8CdsUrniXl/gLe7iliJGc+xU=
Originator	simon@tunnel.thyestes.tartarus.org ([172.31.80.4])
Xref	csiph.com comp.security.ssh:15471

Show key headers only | View raw

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>"))

Back to comp.security.ssh | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Putty 0.81 logging appears broken Chris Townley <news@cct-net.co.uk> - 2024-05-02 17:32 +0100
  Re: Putty 0.81 logging appears broken Simon Tatham <anakin@pobox.com> - 2024-05-03 10:24 +0100
    Re: Putty 0.81 logging appears broken Chris Townley <news@cct-net.co.uk> - 2024-05-03 10:50 +0100

csiph-web