9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Steve Simon <steve@quintile.net>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] osc drawterm big sur
Date: Fri, 20 Nov 2020 10:30:00 +0000	[thread overview]
Message-ID: <516379FE-29D9-49CF-B5FC-F4FB7D493A8B@quintile.net> (raw)
In-Reply-To: <5baace02-ca9a-42ee-88d1-01743aae3772@sirjofri.de>


ok,

this drawterm is working fine for me now.

the cocoa build fails to start, not even prompting me for secstore passwords.

the metal build works with a small match (bodge?) applied, and i backported the /dev/secstore change from an old drawterm i have here.

i assume /dev/secstore was removed as it is bad security practice - which is true. i added it back under the -S option so it is not the default.

NB to be really sure your secrets have gone i suggest you have “cp /dev/null /mnt/term/dev/secstore” in your profile - overwrite them rather than just truncating the file.

i have submitted pull requests on github for these changes.

-Steve

> On 19 Nov 2020, at 2:59 pm, sirjofri <sirjofri+ml-9fans@sirjofri.de> wrote:
> 
> Hello,
> 
> I'm not on OSX, but:
> 
> 19.11.2020 12:40:00 Steve Simon <steve@quintile.net>:
>> there is no /mnt/term/dev/secstore device containing my secstore when i 
> authenticated to drawterm, so i need to authenticate to secstore again in my profile which is irritating. this may be by design as having drawterm know. all my secrets feels a bit foolish.
> 
> I never got anything secstore related working with drawterm. I always needed to get my secrets after drawterm connected separately (eg in profile). I personally would like to have the secrets fetched by drawterm. It seems like it only fetches them to connect with the cpu server and then forgets about the keys.
> 
> Because of that, it seems like you can safely remove these drawterm lines from your profile. I never heard of anybody to get this working properly...
> 
> sirjofri

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T8287ca5a12c53519-M786e9acef9c166e2635b3a12
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

      reply	other threads:[~2020-11-20 10:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-18 13:17 Steve Simon
2020-11-18 13:54 ` Michael Engel
2020-11-18 16:37 ` ori
2020-11-19 11:25   ` Daniel Morandini via 9fans
2020-11-19 11:40     ` Steve Simon
2020-11-19 14:58       ` sirjofri
2020-11-20 10:30         ` Steve Simon [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=516379FE-29D9-49CF-B5FC-F4FB7D493A8B@quintile.net \
    --to=steve@quintile.net \
    --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).