Re: http://sourceware.org/bugzilla/show_bug.cgi?id=11441

[Dave Brolley <brolley at redhat dot com>]

Thanks again for your feedback!

On 05/04/2010 01:28 PM, Frank Ch. Eigler wrote:
> > > Re. stap --server-status=trusted, how would stap determine the
> > > trustedness of remote servers?  Do they advertise their ssl/signing
> > > keys?
> > >        
> > As a trusted peer, successfully establishing a ssl connection is
> > sufficient. As a trusted signer, I was thinking that the server would
> > sign some random chunk of data and that stap would verify the signature
> > in the same way that staprun verifies a signed module.
> >      
> So it would require an active search&  trial connections.  How about
> 'stap --server=search' or something like that, to produce a listing of
> nearby peers?  Filtering on trustedness etc. could be done by the user
> via grep.
I should have thought about this more before responding. Active 
search/connection is not necessary. This information would be obtained 
using nss functions against the databases of trusted ssl peers and signers.
> Hm, how should the client decide whether to look for a server vs.
> attempting local compilation of a script?  'stap --server=XXX' i.e.,
> on user's demand?  Or automatically (in case of a pass 2/4 error
> indicating missing debuginfo/kernel-devel)?
Certainly there is a need for on demand specification. I do also like 
the idea of automatically looking for a server if the client host lacks 
required information.

Dave