From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] ssh to a unix host
Date: Sun, 30 Dec 2012 09:54:54 -0500 [thread overview]
Message-ID: <a3eda929f1d835f1cd807da693809337@kw.quanstro.net> (raw)
In-Reply-To: <B7A84076-D1B0-4325-9B97-C85B88052BA9@gmail.com>
> On 30 Dec 2012, at 13:20, erik quanstrom wrote:
>
> > On Sun Dec 30 08:16:19 EST 2012, lemonkandy@gmail.com wrote:
> >>> we hope to halve that resolved soon, but feel free to submit a
> >>> patch. :-)
> >>>
> >>
> >> Wouldn't mind looking into it. I'm not sure which source files would
> >> need to be looked at or modified. Pointers? I guess I should at
> >> least read up on factotum?
> >
> > /sys/src/cmd/ssh/sshtun.c:^auth_req
> >
>
> I looked in several places for this, but can't find it. I seem to
> have a different source tree to you. Looked in:
>
> /sys/src/cmd/
>
> After running '9fs sources', also looked under
>
> /n/sources/nix/nix/sys/src/cmd/
> /n/sources/plan9/sys/src/cmd/
>
> They contain directories ssh1 and ssh2 but not plain ssh. Certainly
> can't find the file sshtun.c
>
> term% du -a /sys/src/cmd | grep sshtun
> term%
hmm, i guess the labs made more changes than i thought.
; g auth_req /n/sources/plan9/sys/src/cmd/ssh2
/n/sources/plan9/sys/src/cmd/ssh2/netssh.c:81: int auth_req(Packet *, Conn *);
/n/sources/plan9/sys/src/cmd/ssh2/netssh.c:2536: switch (auth_req(p, c)) {
/n/sources/plan9/sys/src/cmd/ssh2/netssh.c:2877: sshdebug(c, "auth_req publickey for user %s", user);
/n/sources/plan9/sys/src/cmd/ssh2/netssh.c:2934: auth_req(Packet *p, Conn *c)
/n/sources/plan9/sys/src/cmd/ssh2/netssh.c:2968: sshdebug(c, "auth_req password");
- erik
next prev parent reply other threads:[~2012-12-30 14:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-30 12:53 Andrew Kilroy
2012-12-30 12:58 ` erik quanstrom
2012-12-30 13:14 ` Andrew Kilroy
2012-12-30 13:20 ` erik quanstrom
2012-12-30 14:48 ` Andrew Kilroy
2012-12-30 14:54 ` erik quanstrom [this message]
2012-12-30 13:54 ` Andrew Kilroy
2012-12-30 13:57 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a3eda929f1d835f1cd807da693809337@kw.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).