From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: From: erik quanstrom Date: Tue, 21 Aug 2007 14:10:26 -0400 To: 9fans@cse.psu.edu Subject: Re: [9fans] Authenticated SMTPD or factotum's p9cr In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: aecd3e9c-ead2-11e9-9d60-3106f5b1d025 > Hm, /rc/bin/service/tcp25 runs as "none" and where as it can read the certificate *that's easy), but I could have sworn it could not access the "eve" factotum (I use "proxima" as a replacement for "bootes", I have a feeling there are namespace issues that Bell Labs ought to take into consideration - but that's just a shot in the dark). I fixed it initially by running factotum within tcp25 and adding the essential keys to it, which improved things, but left me with the "protocol botch". My problem is that I cannot identify the casue of the botch (factotum's diagnostics - here's me looking a gift horse in the mouth - are no adequate) and that is where everything sticks. I don't want to mess with the factotum code unless it becomes essential, but I guess it's one route to identify the problem. i believe one needs to run services that need to talk to factotum from service.auth. i don't run smtp with authentication, but i do run ssh. ssh needed it's key in factotum and to be run from service.auth. - erik