9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Tim Newsham <tim.newsham@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Now with authentication
Date: Fri, 22 Jan 2010 13:44:57 -1000	[thread overview]
Message-ID: <6bbd67bc1001221544w14f4d6c4n452e89123568039c@mail.gmail.com> (raw)
In-Reply-To: <fe41879c1001221451g30267f72s4a1e3ae2689f7cb2@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1590 bytes --]

The OpenSSL DLL is necessary to run the executable.  Off hand I couldnt tell
you why you got the botch message.  If you could provide more details on
what traffic you see, or a way to reproduce, I can look into it.  You just
need to have the proper openssl DLL in your path.  The windows installer
copies it into your windows system32 directory.  You don't really need the
rest of the stuff that it puts into c:\openssl, so it doesnt matter where
you have it.

On Fri, Jan 22, 2010 at 12:51 PM, Akshat Kumar
<akumar@mail.nanosouffle.net>wrote:

> Hi Newsham,
>
> Is OpenSSL necessary for authenticating to 9P servers?
> Currently, I get a "failed to mount ...: <22> botch" error when
> trying to authenticate. Also, is it necessary to compile ninefs
> with OpenSSL, or will the pre-compiled binary find and use
> c:\openssl if it's there?
>
>
> Thanks,
> ak
>
> On Thu, Jan 21, 2010 at 1:50 PM, Tim Newsham <tim.newsham@gmail.com>
> wrote:
> > The Jan5 binaries were broken, thanks for those who reported
> > the problem.  I've uploaded new binaries and updated the README
> > to include instructions on installing OpenSSL binaries.
> >
> > On Jan 5, 10:16 am, Tim Newsham <tim.news...@gmail.com> wrote:
> >> I added p9sk1/p9any authentication support to npfs and added support
> >> for authentication to ninefs. The README has been updated with new
> >> build instructions (OpenSSL is now a dependency) and an updated binary
> >> has been put in the downloads area.
> >
> >
>
>


--
Tim Newsham | www.thenewsh.com/~newsham | thenewsh.blogspot.com

[-- Attachment #2: Type: text/html, Size: 2233 bytes --]

      reply	other threads:[~2010-01-22 23:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <40a8b1cb-6670-4a38-95d4-be7fb03b2420@a21g2000yqc.googlegroups.com>
2010-01-21 21:50 ` Tim Newsham
2010-01-22 22:51   ` Akshat Kumar
2010-01-22 23:44     ` Tim Newsham [this message]

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=6bbd67bc1001221544w14f4d6c4n452e89123568039c@mail.gmail.com \
    --to=tim.newsham@gmail.com \
    --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).