>> There's a "start" member to "struct Srv" that doesn't
>> seem to exist in
>
> You should apply this patch (from plan9port):
Thanks, David, that seems to have worked so far.
++L
superb!
On 30 Mar 2012, at 03:10 AM, blstu...@bellsouth.net wrote:
> Thanks to the support of Coraid, I am pleased to announce
> that a native SSHv2 implementation is now available in
> contrib. It's available in:
>
> contrib/blstuart/ssh
>
> You'll also need the backported p9p factotum in:
>
Hi group, I need help configuring a plan9 server (auth+dns+dhcp+fs).
I already have a plan9 system with /lib/ndb/local, /cfg/$sysname/cpurc
configured as per the wiki and other net sources. I compiled the
pccpuf kernel with no problems and declared it at /n/9fat/plan9.ini,
and I am able to boot th
> You'll also need the backported p9p factotum in:
>
> contrib/quanstro/root/sys/src/cmd/auth/factotum
How big is the dependency on p9p factotum? Is it just syntactic or
is there some needed functionality in p9p factotum which the sources
version doesn't provide?
> 1) I can not resolv any name from my terminal, even though my server's
> ndb database has declared a subnet with an default dns entry.
Does 'cat /net/ndb' on the terminal show a 'dns=' entry?
> 2) I can not authenticate to the server with any user from my terminal
> system even though I can see
> How big is the dependency on p9p factotum? Is it just syntactic or
> is there some needed functionality in p9p factotum which the sources
> version doesn't provide?
It's a strong one: it implements DSA sign/verify.
BTW, without patching ndb/cs as mentioned before one won't be able to
connect b
> contrib/quanstro/root/sys/src/cmd/auth/factotum
Nfactotum misses proto=mschap which is used by cifs(4) for doing NTLM.
> contrib/blstuart/ssh
It's great! All thumbs up!
Would it be hard to add cooked mode (-C)?
--
- Yaroslav
>> contrib/quanstro/root/sys/src/cmd/auth/factotum
>
> Nfactotum misses proto=mschap which is used by cifs(4) for doing NTLM.
1. Is Nfactotum the back port of factotum from p9p?
2. Any chance that these different branches could be brought together?
I note that the "9p.h" extension is trivial, I
> Would it be hard to add cooked mode (-C)?
never mind: it's easy to simulate by binding /dev/nul over /dev/consctl.
"fn name @{block}" doesn't cause block to run in a sub-shell, although
it accepts the syntax.
Is it someting should not be tried, or something shoud be fixed?
>> You'll also need the backported p9p factotum in:
>>
>> contrib/quanstro/root/sys/src/cmd/auth/factotum
>
> How big is the dependency on p9p factotum? Is it just syntactic or
> is there some needed functionality in p9p factotum which the sources
> version doesn't provide?
Quite big. Actually
On Fri Mar 30 07:43:57 EDT 2012, yari...@gmail.com wrote:
> "fn name @{block}" doesn't cause block to run in a sub-shell, although
> it accepts the syntax.
> Is it someting should not be tried, or something shoud be fixed?
should be fixed.
- erik
>> contrib/quanstro/root/sys/src/cmd/auth/factotum
>
> Nfactotum misses proto=mschap which is used by cifs(4) for doing NTLM.
Isn't mschap implemented in
contrib/quanstro/root/sys/src/cmd/auth/factotum/chap.c?
There's a Proto structure for it at the bottom of the file.
BLS
On Fri Mar 30 06:48:39 EDT 2012, yari...@gmail.com wrote:
> > contrib/quanstro/root/sys/src/cmd/auth/factotum
>
> Nfactotum misses proto=mschap which is used by cifs(4) for doing NTLM.
what's the basis for this claim? it might be broken, since we don't use it
much, but it's not missing.
- erik
On Fri Mar 30 08:50:23 EDT 2012, blstu...@bellsouth.net wrote:
> >> You'll also need the backported p9p factotum in:
> >>
> >> contrib/quanstro/root/sys/src/cmd/auth/factotum
> >
> > How big is the dependency on p9p factotum? Is it just syntactic or
> > is there some needed functionality in p9p
>> Would it be hard to add cooked mode (-C)?
>
> never mind: it's easy to simulate by binding /dev/nul over /dev/consctl.
The other thing I've noticed is that when I'm connecting
from Plan 9 to a UNIX system, running ssh in vt is
handy. It makes all the stuff like readline and color
ls happy, pl
> 1. Is Nfactotum the back port of factotum from p9p?
>
> 2. Any chance that these different branches could be brought together?
no. this is a rewrite.
> I note that the "9p.h" extension is trivial, I see no reason for the
> Plan 9 distribution not to include it. But the differences between
>
> btw., the POSIX -q option to grep is needed only on non-POSIX systems, that
> do
> not provide /dev/null, right?
grep(1) has a -s option. this is obviously useful because for
large files with early matches, most of the file need not be read.
- erik
On Mar 30, 5:35 am, 9f...@hamnavoe.com (Richard Miller) wrote:
> > 1) I can not resolv any name from my terminal, even though my server's
> > ndb database has declared a subnet with an default dns entry.
>
> Does 'cat /net/ndb' on the terminal show a 'dns=' entry?
>
this is the info cat /net/ndb g
On Fri Mar 30 02:08:59 EDT 2012, 0in...@gmail.com wrote:
> > There's a "start" member to "struct Srv" that doesn't
> > seem to exist in
>
> You should apply this patch (from plan9port):
>
[...]
this should no longer be necessary. as a temporary measure,
i've added the change to lib9p, and the
> contrib/quanstro/root/sys/src/cmd/auth/factotum
contrib/install quanstro/nfactotum. move your old factotum out of the way
first.
- erik
> So, save for the ipwg, everything seems ok. The server akenaton as
that could be your problem. there's no route out.
- erik
> > 2) I can not authenticate to the server with any user from my terminal
> > system even though I can see the attempted conecction in the fossil
> > console.
>
> Running the auth/debug command on the terminal may reveal a clue.
I ran auth/debug, this is what it tells:
no p9sk1 keys found in fac
> So, save for the ipwg, everything seems ok. The server akenaton as
> ip=10.0.0.2 and it's ndb database has declared all these services.
> Why then, isn't dns working?
I had to use an IP number in the ipgw pair in the ipnet to force it to appear
in /net/ndb. I'm not sure whether this is expecte
2012/3/30 erik quanstrom :
>> contrib/quanstro/root/sys/src/cmd/auth/factotum
>
> contrib/install quanstro/nfactotum. move your old factotum out of the way
> first.
here's how one may work out contrib/install conflicts:
% contrib/install quanstro/nfactotum # may report conflicts
% replica/pull -
> contrib/install quanstro/nfactotum. move your old factotum out of the way
> first.
Is it safe to use the new factotum as a kernel module? Is it standard
in 9atom?
++L
> contrib/install quanstro/nfactotum. move your old factotum out of the way
> first.
Is it safe to use the new factotum as a kernel module? Is it standard
in 9atom?
++L
Not that I remember: I think we independently rewrote it in a concurrent
style,
in Limbo in my case, a little differently although I studied p9p's when it
was available.
On 30 March 2012 14:03, erik quanstrom wrote:
> so russ i think with input from charles, rewrote factotum so that the
> protoc
"dinner time, hold on while i grep my desk for my car keys" - ken anon
On 31 March 2012 00:13, erik quanstrom wrote:
>> btw., the POSIX -q option to grep is needed only on non-POSIX systems, that
>> do
>> not provide /dev/null, right?
>
> grep(1) has a -s option. this is obviously useful becaus
On Fri Mar 30 09:56:24 EDT 2012, lu...@proxima.alt.za wrote:
> > contrib/install quanstro/nfactotum. move your old factotum out of the way
> > first.
>
> Is it safe to use the new factotum as a kernel module? Is it standard
> in 9atom?
if you mean, is it safe to build into /boot, the answers a
On 2012-03-30, at 6:56 AM, Lucio De Re wrote:
> I had to use an IP number in the ipgw pair in the ipnet to force it to appear
> in /net/ndb. I'm not sure whether this is expected but undocumented
> bahaviour or a bug, but a domain name didn't cut it. I'd be curious to know.
A hostname can ma
(I am slightly embarrassed to have made three conflicting posts in
succession. The Google-group interface was, for some reason, not sending my
posts through. So I kept trying over 12 hours, and every time I rewrote my
post. Anyway, that's not important any more.)
Before I end I must mention that
Forwarding it to the list so people don't bother to debug themselves.
It's tested with cifs and a local change which enables upas/fs to do
IMAP with NTLM auth.
-- Forwarded message --
From: Yaroslav
Date: 2012/3/30
Subject: Re: [9fans] SSHv2
To: erik quanstrom
2012/3/30 erik qu
On Fri Mar 30 07:44:12 EDT 2012, yari...@gmail.com wrote:
> "fn name @{block}" doesn't cause block to run in a sub-shell, although
> it accepts the syntax.
> Is it someting should not be tried, or something shoud be fixed?
you've misunderstood the current grammar. you have defined 2 functions
nam
> /n/sources/contrib/quanstro/root/sys/src/cmd/auth/factotum/chap.c:153,166
> - /sys/src/cmd/auth/factotum/chap.c:154,163
> c->state = "read challenge";
> if((nchal = convreadm(c, (char**)(void*)&chal)) < 0)
> goto out;
> - if(astype == AuthMSchap && nchal != MSch
> you've misunderstood the current grammar. you have defined 2 functions
> name and '@' as {block}. the binding, illustrated with parens is
> fn (name @) {block}
> the production in the grammer is
> FN words brace
> but since once production for words is words -> keyword, a keyword
> Then, how would you explain this:
it should be self-explanitory.
> term% fn x @{x=y}
> term% whatis x
> fn x {x=y}
creates to functions x and '@' definition {x=y}.
> term% fn 'x @'{x=y}
> term% whatis 'x @'
> fn 'x @' {x=y}
quoting disables any interpretation in rc; this isn't
the bourne she
> no p9sk1 keys found in factotum
So, put one in and try again.
auth/factotum -g 'proto=p9sk1 user= dom= !password?'
where and are your username and authdom
>> term% fn x @{x=y}
>> term% whatis x
>> fn x {x=y}
>
> creates to functions x and '@' definition {x=y}.
The question is why it discards @ here?
>> So, save for the ipwg, everything seems ok. The server akenaton as
>
> that could be your problem. there's no route out.
>
> - erik
But that's not relevant when trying to reach machines
on the same subnet:
> I have to machines declared in ndb/local, akenaton ip 10.0.0.2 and
> nefertiti ip 1
> surely you need to use the "user" attribute. if you don't please send
> a copy of chap that doesn't give compiler warnings.
The user attribute is available at the end of CR protocol, upon 'attr'
rpc request.
The attached chap.c compiles cleanly here.
- yk
/*
* CHAP, MSCHAP
*
* The client
> - if(astype == AuthMSchap && nchal != MSchallen)
> - c->state = "write user";
Who slipped up with the indentation? I hope it was not intentional.
++L
On Mar 30, 2012, at 12:19 , Yaroslav wrote:
>>> term% fn x @{x=y}
>>> term% whatis x
>>> fn x {x=y}
>>
>> creates to functions x and '@' definition {x=y}.
>
> The question is why it discards @ here?
Erik's point is that rc isn't discarding it. You have a list. It sets x
equal to that function,
I see now. Thank you guys!
> Erik's point is that rc isn't discarding it. You have a list. It sets x
> equal to that function, then sets @ equal to that same function.
>
> : iota; fn x @{x=y}
> : iota; whatis x
> fn x {x=y}
> : iota; whatis '@'
> fn @ {x=y}
45 matches
Mail list logo
