From: vic.thacker@fastmail.fm
To: "leimy2k via 9fans" <9fans@9fans.net>
Subject: Re: [9fans] dp9ik port
Date: Thu, 30 Sep 2021 19:24:58 +0900 [thread overview]
Message-ID: <d93dadde-7210-4021-b447-c1c8edb22a89@www.fastmail.com> (raw)
In-Reply-To: <CAHwi9bxS4EMqGhd1ZemCEnG3B2PAUXpeAJy+fsobDOfaKnLVpg@mail.gmail.com>
As it is a 9front specific question, you might consider posting to the 9front mailing list.
To know more about 9front mailing lists, see http://lists.9front.org/.
Sincerely,
Vic
On Thu, Sep 30, 2021, at 07:08, Eli Cohen wrote:
> hello all,
>
> I wanted to check back in about the continuing saga to port a dp9ik
> patch upstream.
>
> where I believe we left off in that discussion, there was advice to
> make a roadmap, involving some kinds of software development
> techniques I don't understand at all, to be completely honest... I
> have tried to keep after that a bit and try to figure out a roadmap
> based on what I have done before and what it would take to do this.
>
> before I ever started on this project at all, I had looked into dp9ik
> before to re-implement it in javascript for another project, so I do
> know a little about the login process and how dp9ik works as a
> pre-shared key authenticator for an encrypted connection. (not the
> math behind that though! just ported what was necessary to javascript)
>
> I started doing the same thing kinda, just back-porting stuff to send
> a patch upstream. it rapidly started becoming as much of a mess as my
> efforts to port to javascript, what was only C to C! I'm not a
> professional here at all...
>
> I did note it seemed helpful to have both types of plan 9 systems and
> both types of drawterm because of slight differences in the keyboard
> input
>
> thanks everyone!
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T21443e91804188d5-Me62cbc087d029bc83969e6bf
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-09-30 10:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 22:08 Eli Cohen
2021-09-30 10:24 ` vic.thacker [this message]
2021-09-30 12:17 ` Stuart Morrow
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=d93dadde-7210-4021-b447-c1c8edb22a89@www.fastmail.com \
--to=vic.thacker@fastmail.fm \
--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).