9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "ron minnich" <rminnich@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: [9fans] plan9 as an imaps server
Date: Mon, 28 May 2007 23:48:58 -0700	[thread overview]
Message-ID: <13426df10705282348y7f7a0f72o9800ec872c05d755@mail.gmail.com> (raw)

I am certain that others have done this, the wiki says they have.
Although, I do plan to update the wiki once I understand this. SO is
claiming it is time to throw in the towel and just buy a Mac as a mail
server. Shudder.

After I boot I have this:

cpu% cat /mnt/factotum/ctl

So, the ctl is empty. OK, let's add the secstore bits for the key:
cpu% auth/secstore -n -G factotum > /mnt/factotum/ctl
auth/secstore: error: account expired

Ah, well. I am telling it to use the nvram key, but something is still
expired. Um, what
account? It's not all that clear, I'll do a pull and see if it gets
better. Anyway:
cpu% slay secstored | rc
cpu% cd
cpu% cd auth/secstore/
cpu% ./8.secstored  # my hacked secstored

Let's try that again.
cpu% auth/secstore -n -G factotum > /mnt/factotum/ctl
account expired at Mon May 28 19:25:22 EDT 2007
, current time is Mon May 28 19:25:22 EDT 2007
; not that we care
cpu% cat /mnt/factotum/ctl
key proto=rsa size=1024 ek=10001 etc. etc. etc. service=tls
role=client etc. etc.

now I tried to get in and it still failed. I have to do this:

cpu% slay listen | rc
cpu% aux/listen -q -t /rc/bin/service.auth -d /rc/bin/service tcp

Boy, that seems wrong to me!

At this point, from the mac, I am getting a password prompt.

tlssrv reports this much:
roo May 28 19:31:07 76.103.89.146!62785 tls reports recv HClientKeyExchange
	etc. etc.

roo May 28 19:31:07 76.103.89.146!62785 tls reports tls secrets

roo May 28 19:31:07 76.103.89.146!62785 tls reports recv HFinished

roo May 28 19:31:07 76.103.89.146!62785 tls reports send HFinished

roo May 28 19:31:07 76.103.89.146!62785 tls reports tls finished

roo May 28 19:31:07 76.103.89.146!62785 tls reports open

: imap4d debugging enabled
* OK roo.hsd1.ca.comcast.net. IMAP4rev1 server ready



i.e. we're getting the nice socket, and imap4d is starting up. It does
not much like my password. not sure why ... but will look more and let
you all know.

thanks

ron


             reply	other threads:[~2007-05-29  6:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29  6:48 ron minnich [this message]
2007-05-29  7:01 ` Skip Tavakkolian
2007-05-29  7:38 ` Steve Simon
2007-05-29 16:04   ` ron minnich
2007-05-29 16:10     ` erik quanstrom
2007-05-29 16:14       ` ron minnich

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=13426df10705282348y7f7a0f72o9800ec872c05d755@mail.gmail.com \
    --to=rminnich@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).