Scheme 9 from Empty Space (pun intended and originally a reference
to the movie, not to the OS) is an interpreter for R4RS Scheme.
In 2008 Bakul Shah pointed out that an interpreter with that name
should run on the Plan 9 OS and helped me port it. Ever since the
Plan 9 port has been in varying
Awesome work!
On 2 Jul, 2015, at 4:11 pm, Nils M Holm n...@t3x.org wrote:
Scheme 9 from Empty Space (pun intended and originally a reference
to the movie, not to the OS) is an interpreter for R4RS Scheme.
In 2008 Bakul Shah pointed out that an interpreter with that name
should run on
as per http://wiki.9front.org/bounties
replace p9sk1 with something better
I'm looking to start on this, does anyone have thoughts on improvements?
At the moment I am intending to just replace the DES keys with AES but
is there any call for more structural changes?
I was thinking that an
I hadn't looked at the bounties page recently. It includes
improve the tls(3) device $10 - The TLS device implements the record layer
protocols of Transport Layer Security version 1.0 and Secure Sockets Layer
version 3.0. It does not implement the handshake protocols, which are
responsible for
I think just replacing des keys with AES is not worth it. there is so little
data that des is quite secure (imho).
replacing p9sk1 with pki is much more useful. rus posted to 9fans about wanting
to do this so a terminal could cache tickets to speed auth when the auth server
is remote - I
Personally, I think two separate things are called for.
1) A straight-forward update to use AES
2) Some public key system.
The p9sk1 *model* is great, and it'd be a real shame to drop it. Doing the
upgrade and teaching should be easy, although there's tedious work in telling
all the things to
On 2 July 2015 at 13:30, Anthony Sorace a...@9srv.net wrote:
The p9sk1 *model* is great, and it'd be a real shame to drop it.
There always seems to be trouble setting it up, which suggests that the
documentation people typically first see might need revising
(or better pointers if it exists
On 2 July 2015 at 17:44, Skip Tavakkolian skip.tavakkol...@gmail.com
wrote:
isn't it settled that keeping of secrets and exchange thereof are the
domain of factotum?
I hope so.
I think that I'd avoid putting the negotiation and certificate stuff (as
such) in the kernel device.
Speaking as an amateur, I'd be tempted to investigate pushing the Plan
9 paradigm further and see how hard it would be to fragment the kernel
into asymmetric portions. To be more specific,
isn't it settled that keeping of secrets and exchange thereof are the
domain of factotum?
On Thu, Jul 2, 2015 at 6:14 AM, Charles Forsyth charles.fors...@gmail.com
wrote:
I hadn't looked at the bounties page recently. It includes
improve the tls(3) device $10 - The TLS device implements the
Wanted: more
ciphers, support for user certificates, support for certificate
verification. ECDSA! ECDHE!
client certs, client side DHE and ECDHE already done in 9front, just
take it :)
--
cinap
11 matches
Mail list logo