9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: cinap_lenrek@felloff.net
To: 9fans@9fans.net
Subject: Re: [9fans] drawterm problems after susupdate
Date: Wed, 22 Feb 2023 14:41:34 +0100	[thread overview]
Message-ID: <10F87849896FBB9A4D16B30C0CCC3EEF@felloff.net> (raw)
In-Reply-To: <16769066020.f79b.46675@composer.9fans.topicbox.com>

I think it would be better to direct 9front specific questions
to the 9front mailinglist unless you understand the scope
well enougth that it might as well apply to plan9 in general.

Anyway here you go (yes, this is 9front specific answer):

This is likely due to the removal of devssl from the kernel.
The cpu (and import) porotocols have been removed from 9front
for a while now (but the binaries would still remain on your
file-system) and replaced by rcpu(1), which uses devtls.

The cpu/import programs where the only ones still using devssl.

A drawterm exist that is maintained and supports both the
previous cpu as well as the new rcpu protocols.


The new rcpu service (also handling rimport/rexport and rx)
has the following listen script: /rc/bin/service/tcp17019

if(~ $#* 3){
        remote=$2!`{cat $3/remote}
fn server {
        ~ $#remote 0 || echo -n $netdir $remote >/proc/$pid/args
        rm -f /env/'fn#server'
        . <{n=`{read} && ! ~ $#n 0 && read -c $n} >[2=1]
exec tlssrv -a /bin/rc -c server

I fear a bit that given you where still be using cpu protocol
with an old drawterm that you probably havnt even upgraded your
authentication server to the new dp9ik key as well.

P9sk1 is still supported in 9front (factotum and authserver),
but has long been disabled in the authserver listen script by
default (passing -N to auth/authsrv).

So please make sure you have set a new key as well as have the
-N flag passed in /rc/bin/service.aith/tcp567 like:

exec /bin/auth/authsrv -N $3


9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Te0c7fa564759b89c-Mc8862432d943dea5b65423b9
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2023-02-22 13:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20 15:23 fijal
2023-02-22 13:41 ` cinap_lenrek [this message]
2023-02-22 19:06   ` fijal

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=10F87849896FBB9A4D16B30C0CCC3EEF@felloff.net \
    --to=cinap_lenrek@felloff.net \
    --cc=9fans@9fans.net \


* 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).