9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <russcox@gmail.com>
To: 9fans <9fans@cse.psu.edu>
Subject: [9fans] plan9port: recent changes
Date: Sun, 13 Feb 2005 19:41:45 -0500	[thread overview]
Message-ID: <ee9e417a05021316414b474f5a@mail.gmail.com> (raw)

Lots of little changes in the past week or so: autoindent for sam,
better label handling in awd et al., new diff flags -c and -a,
various stack overflow fixes (*cough* X11 *cough*), programs
should work better with SIGTSTP, SIGTTIN, and SIGTTOU,
lots of little bug fixes.

The big new additions are factotum and various supporting
libraries and programs.

Thanks to Lucho, plan9port now has a working factotum
that can be used with 9p to access files on protected servers:

	ibook=; factotum
	ibook=; sources='tcp!sources.cs.bell-labs.com!9fs'
	ibook=; 9p -a $sources read plan9/adm/users

	!adding key: role=client proto=p9sk1 dom=outside.plan9.bell-labs.com
	user[rsc]: bozo
	password:
	!
	-1:adm:adm:bootes
	0:none:adm:
	1:tor:tor:
	2:glenda:glenda:
	9999:noworld::
	10000:sys::
	10001:upas:upas:
	10002:bootes:bootes:
	ibook=; 9p -a $sources read plan9/NOTICE
	Copyright © 2002 Lucent Technologies Inc.
	All Rights Reserved
	ibook=; 

Over the weekend I added DSA and RSA signature support
to factotum and used them to implement an ssh-agent front
end for factotum:

	l=; factotum
	secstore password: 
	l=; eval `{9 ssh-agent}
	l=; ssh tux
	tux=; ^D
	l=; 

It's hard to see, but ssh used factotum via the ssh-agent
interface to authenticate to tux.  Also hard to see is the fact
that this is using SSH version 2 keys (SSH1 is also supported),
so this setup is ahead of Plan 9.

(Sadly, it's not too easy to move the DSA and RSA support back
into Plan 9, firstly due to the lack of an SSH2 client.  Also the 
factotum is completely different--simpler--inside.)

Enjoy.
Russ


             reply	other threads:[~2005-02-14  0:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-14  0:41 Russ Cox [this message]
2005-02-14 19:09 ` [9fans] " Russ Cox
2005-02-14 20:31   ` Bruce Ellis
2005-02-14 20:49     ` Russ Cox
2005-02-14 21:03       ` Skip Tavakkolian
2005-02-15  3:28         ` Andrew Simmons
2005-02-15  3:39           ` Russ Cox
2005-02-15  7:20       ` Tiit Lankots
2005-02-15  9:51       ` David Tolpin
2005-02-14 11:27 [9fans] " Aharon Robbins
2005-02-14 14:53 ` Russ Cox
2005-02-14 15:13 Aharon Robbins
2005-02-14 17:41 ` boyd, rounin

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=ee9e417a05021316414b474f5a@mail.gmail.com \
    --to=russcox@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).