From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cron authentication
Date: Mon, 28 Jul 2003 15:44:35 -0600 [thread overview]
Message-ID: <Pine.LNX.4.44.0307281528550.30573-100000@fbsd.cpsc.ucalgary.ca> (raw)
In-Reply-To: <Pine.LNX.4.44.0307281440380.30573-100000@fbsd.cpsc.ucalgary.ca>
I believe I figured it out after a bit of experimenting with it.
What threw me off originally was the fact that I could run auth/cron on
non-auth cpu servers without any problem, however I realized that the
factotum for the host owner knew how to authenticate to the auth server,
and had the proper capabilities to become me...
at least it stopped working when I deleted the keys from the cpu server's
factotum :)
by the way, do you think that it's a bad idea to give secstore access to a
cpu server's hostowner?
andrey
prev parent reply other threads:[~2003-07-28 21:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 20:47 andrey mirtchovski
2003-07-28 21:44 ` andrey mirtchovski [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=Pine.LNX.4.44.0307281528550.30573-100000@fbsd.cpsc.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--cc=9fans@cse.psu.edu \
/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).