9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Iban Nieto" <iban.nieto@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] problem with factotum
Date: Thu, 14 Sep 2023 12:49:20 -0400	[thread overview]
Message-ID: <16947101600.Cbbb1f.77199@composer.9fans.topicbox.com> (raw)
In-Reply-To: <CAJSxfmLO+7Pxz3kbM1+S=F2ydEUOw9OAfzUs=8H=k7j8hcqjRg@mail.gmail.com>

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


@igor I've followed some of your instructions (as you can see, the same procedure for acmed), but my setup is a bit different than yours. Could you please tell me what's wrong with my setup? (this is my very first time using tls in 9front).

@skip I've performed the entire procedure in the same namespace and in another ns by using line per line commands in the console and using scripts, all with the same luck. Also /srv/factotum is in place in my namespace as I have auth/factotum in my $home/lib/profile.

I guess that the problem could be factotum or the way the keys are added, but the thing is that I've already working factotum with ssh keys, so I have NO IDEA what's going on this case. Actually, after reading lots of manuals I can't find where is the problem, and with some probability is a silly one.

Thank you again!
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Te82df98419e38504-Mab6b11e0e4952d3ee3bb07eb
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

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

  reply	other threads:[~2023-09-14 16:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-13 18:33 Iban Nieto
2023-09-13 19:17 ` igor
2023-09-13 21:54 ` Skip Tavakkolian
2023-09-14 16:49   ` Iban Nieto [this message]
2023-09-14 20:51     ` ori
2023-09-29  8:02       ` Iban Nieto

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=16947101600.Cbbb1f.77199@composer.9fans.topicbox.com \
    --to=iban.nieto@gmail.com \
    --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).