From: "Frank D. Engel, Jr." <firstname.lastname@example.org>
Subject: Re: [9front] Introduction and regarding guidance
Date: Wed, 1 Jun 2022 20:27:09 -0400 [thread overview]
Message-ID: <email@example.com> (raw)
If you need something to start with, something I personally find
annoying is that when I connect to one of my CPU servers using drawterm
I am prompted for my secstore password *twice* instead of just once.
I looked at it a while back and figured out why it was happening, at it
made sense (I would need to dig in again as it has been a while, but it
was something to the effect of the first one being used to authenticate
to the file server before factotum was up, then the second one being
used to populate factotum?), but I couldn't immediately think of a
"good" secure way to fix it at the time and have just been living with
it for now.
I definitely wouldn't mind that being fixed if it can be done safely,
though this might be somewhat challenging for a beginner, as for one
thing you would basically need to have at least a bit of a cluster setup
to reproduce it.
On 6/1/22 6:43 PM, firstname.lastname@example.org wrote:
> Quoth Deepak kr. Mahato <Deepakkrmahato@proton.me>:
>> Could anyone please guide me in what other concepts I should start looking
>> into and how do I familiarize myself with 9front and get started in working
>> with its codebase so that I may be able to make valuable contributions.
> use it and fix the stuff that annoys you.
> there's nobody here to tell you want to work on; this is
> your hobby, you get to decide how you go about it.
> there are some old gsoc idea lists, I guess.
next prev parent reply other threads:[~2022-06-02 0:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 20:36 Deepak kr. Mahato
2022-06-01 22:43 ` ori
2022-06-02 0:27 ` Frank D. Engel, Jr. [this message]
2022-06-02 1:54 ` Noam Preil
2022-06-02 3:05 ` sirjofri
2022-06-02 3:21 ` noam
2022-06-02 4:22 ` william
2022-06-02 4:55 ` Mart Zirnask
2022-06-02 5:02 ` sirjofri
2022-06-02 14:44 ` Deepak kr. Mahato
2022-06-02 14:50 ` Stanley Lieber
2022-06-02 14:51 ` Christos Margiolis
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).