9front - general discussion about 9front
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] secstore on Raspberry Pi
Date: Fri, 29 Jul 2022 15:54:58 +0200	[thread overview]
Message-ID: <CAFSF3XNv3WR8wfCv=W8pdtqOZyEd3-F76DTfZ9h_3kdMxKoajw@mail.gmail.com> (raw)
In-Reply-To: <1612830253.499365.1659024712431@office.mailbox.org>

sahu, your email also seems to always land in my spam.

who is in control of mailbox.org?
i was gonna blame YOU for enabling the dmarc/dkim hipster-security
traps, but i guess some bigger group of people got tricked to use the
same default configuration, which enables all those "optional"
security features (literal sabotage). google must love it bec. their
email in turn comes always though bec. they ignore security.

On 7/28/22, sahu@mailbox.org <sahu@mailbox.org> wrote:
> Hello cinap,
> thank you very much for the explanation!
> When I run "echo $auth" without any change of /n/pidos/cmdline.txt, I get a
> new line only, but when I add "auth=cirno" there, cirno will be echoed after
> reboot.
> Is this a hint for a misconfiguration of the "ipnet=..." part of
> /lib/ndb/local?
> Thanks and best regards,
> sahu
>> cinap_lenrek@felloff.net hat am 27.07.2022 18:59 CEST geschrieben:
>> dialing $auth
>> thats not the same as a environment variable.
>> a dialstring containing $xxx will do a ndb lookup relative
>> to your ip addresses, looking for a attribute named xxx
>> and then substituting its value.
>> dialing $cpu would find the cpu=bla attribute in your ipnet=
>> for example and then dial bla.
>> same for $auth.
>> --
>> cinap

      reply	other threads:[~2022-07-29 13:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27 14:51 sahu
2022-07-27 14:59 ` Jacob Moody
2022-07-28 16:04   ` sahu
2022-07-27 16:59 ` cinap_lenrek
2022-07-28 16:11   ` sahu
2022-07-29 13:54     ` hiro [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:

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

  git send-email \
    --in-reply-to='CAFSF3XNv3WR8wfCv=W8pdtqOZyEd3-F76DTfZ9h_3kdMxKoajw@mail.gmail.com' \
    --to=23hiro@gmail.com \
    --cc=9front@9front.org \


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