> 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
