Groups | Search | Server Info | Login | Register
Groups > comp.security.ssh > #15471
| From | Simon Tatham <anakin@pobox.com> |
|---|---|
| Newsgroups | comp.security.ssh |
| Subject | Re: Putty 0.81 logging appears broken |
| Date | 2024-05-03 10:24 +0100 |
| Message-ID | <81seyz2qq7.fsf@thyestes.tartarus.org> (permalink) |
| References | <v10f6o$3qpm0$1@dont-email.me> |
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
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