Rocksolid Light

Welcome to RetroBBS

mail  files  register  newsreader  groups  login

Message-ID:  

If you think the system is working, ask someone who's waiting for a prompt.


devel / comp.security.ssh / Re: Putty 0.81 logging appears broken

SubjectAuthor
* Putty 0.81 logging appears brokenChris Townley
`* Re: Putty 0.81 logging appears brokenSimon Tatham
 `- Re: Putty 0.81 logging appears brokenChris Townley

1
Putty 0.81 logging appears broken

<v10f6o$3qpm0$1@dont-email.me>

  copy mid

https://www.rocksolidbbs.com/devel/article-flat.php?id=248&group=comp.security.ssh#248

  copy link   Newsgroups: comp.security.ssh
Path: i2pn2.org!i2pn.org!usenet.network!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: news@cct-net.co.uk (Chris Townley)
Newsgroups: comp.security.ssh
Subject: Putty 0.81 logging appears broken
Date: Thu, 2 May 2024 17:32:22 +0100
Organization: A noiseless patient Spider
Lines: 9
Message-ID: <v10f6o$3qpm0$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 02 May 2024 18:32:24 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="188854bce71d2012b14cca5f8ccef418";
logging-data="4024000"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19FhWVAz8DZWn5tOq71+xLWgDwaKwrliC4="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:zWqc4olI0ucbQ2JE5NPwWnxqn94=
Content-Language: en-GB
 by: Chris Townley - Thu, 2 May 2024 16:32 UTC

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

Re: Putty 0.81 logging appears broken

<81seyz2qq7.fsf@thyestes.tartarus.org>

  copy mid

https://www.rocksolidbbs.com/devel/article-flat.php?id=249&group=comp.security.ssh#249

  copy link   Newsgroups: comp.security.ssh
Path: i2pn2.org!i2pn.org!news.quux.org!nntp.terraraq.uk!nntp-feed.chiark.greenend.org.uk!ewrotcd!.POSTED.chiark.greenend.org.uk!not-for-mail
From: anakin@pobox.com (Simon Tatham)
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>
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])
 by: Simon Tatham - Fri, 3 May 2024 09:24 UTC

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

Re: Putty 0.81 logging appears broken

<v12c14$eut6$1@dont-email.me>

  copy mid

https://www.rocksolidbbs.com/devel/article-flat.php?id=250&group=comp.security.ssh#250

  copy link   Newsgroups: comp.security.ssh
Path: i2pn2.org!rocksolid2!news.neodome.net!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: news@cct-net.co.uk (Chris Townley)
Newsgroups: comp.security.ssh
Subject: Re: Putty 0.81 logging appears broken
Date: Fri, 3 May 2024 10:50:26 +0100
Organization: A noiseless patient Spider
Lines: 43
Message-ID: <v12c14$eut6$1@dont-email.me>
References: <v10f6o$3qpm0$1@dont-email.me>
<81seyz2qq7.fsf@thyestes.tartarus.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Fri, 03 May 2024 11:50:28 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="5b87cf1b1b012a670336968f6df19c4f";
logging-data="490406"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19xIIBQCtX3LBCd/CQPSWXNxWIjD94rD7I="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:huRXCxvehkbCpgsAGQj1c1TwWiw=
Content-Language: en-GB
In-Reply-To: <81seyz2qq7.fsf@thyestes.tartarus.org>
 by: Chris Townley - Fri, 3 May 2024 09:50 UTC

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


devel / comp.security.ssh / Re: Putty 0.81 logging appears broken

1
server_pubkey.txt

rocksolid light 0.9.81
clearnet tor