Nп/п : 62 из 92
От : Bob Latham 2:5075/128 27 июл 23 20:23:09
К : Theo 27 июл 23 22:30:08
Тема : Re: Nettle can`t SSH into RaspPi
----------------------------------------------------------------------------------
@MSGID: <5acaae0566bob@sick-of-spam.invalid>
5882b8dd
@REPLY: e6kmz@news.chiark.greenend.org.uk>
4435ab8a
@REPLYADDR Bob Latham <bob@sick-of-spam.invalid>
@REPLYTO 2:5075/128 Bob Latham
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-ID:
<5acaae0566bob@sick-of-spam.invalid>
@RFC-References: <5ac99d449fbob@sick-of-spam.invalid>
<2bb1bfc95a.BrianNews@brianhowlett.me.uk> LWdmz@news.chiark.greenend.org.uk> <5ac9f81ac4bob@sick-of-spam.invalid>
e6kmz@news.chiark.greenend.org.uk>
@TZUTC: 0100
@PID: NewsHound/v1.53-32 RC1
@TID: FIDOGATE-5.12-ge4e8b94
In article
e6kmz@news.chiark.greenend.org.uk>,
Theo <theom+news@chiark.greenend.org.uk> wrote:
> Bob Latham <bob@sick-of-spam.invalid> wrote:
> > In article LWdmz@news.chiark.greenend.org.uk>,
> > Theo <theom+news@chiark.greenend.org.uk> wrote:
> >
> > > Using Nettle`s own SSH implementation (which uses libssh2) is the
> > > way forward these days. That`s the one Gerph has contributed to
> > > recently: https://github.com/dpt/Nettle/
> >
> > > I think it should need a recompile with a newer libssh2 for newer
> > > cipher support. There is infrastructure there to build it using
> > > his JFPatch-as-a-service, but I`m not sure if those builds are made
> > > available anywhere.
> >
> > > I`ll take a todo to look at that, but no promises on
> > > timeline...
> >
> > Thanks for that Theo.
> That was less painful than I thought. Here is a test build:
> http://www.chiark.greenend.org.uk/~theom/ephemeral/Nettle_0-2050b-1_arm.zip
> This is a rebuild with a much more modern libssh2 than the one from
> 2010.
> Please give this a try and let me know if it fixes the problem. I
> have a Pi running Raspberry Pi OS `bullseye` and both this one (I`m
> tentatively calling it 0.2050b but that`s not official) and 0.2043b
> managed to SSH in successfully, but this one went through much more
> quickly while 0.2043b printed several screenfuls of dots (I suspect
> they were arguing over which ciphers to support).
> If it`s looking good I`ll upstream the changes and if that`s all
> happy I`ll put a new version on riscos.info where PackMan should
> pick it up.
I can indeed ssh into my pi with this latest build all be it with
many lines of dots first.
Well done and thank you. Greatly appreciate what you`ve done.
One slight oddity though which is probably going to show my ignorance
more than anything else.
When you log in, is shows the usual default..
pi@name:~$
But it became clear very quickly that in fact it was at..
pi@name:~/home/pi~$
I don`t think it`s possible to get above that into the root and then
into boot or etc.
Why would it do that, putty.exe doesn`t?
I`m most grateful for you efforts but I don`t really understand what
it`s doing.
Thanks again.
Bob.
--- NewsHound/v1.53-32 RC1
* Origin: None (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5075/128
@PATH: 5075/128 5020/1042 4441