Re: Server Name Indication (SNI) relayd

2014-07-24 Thread Reyk Floeter
On Thu, Jul 24, 2014 at 11:00:26AM +0100, Kevin Chadwick wrote:
 I am using and plan to use a single server for now anyway but is relayd
 SNI support planned at all?
 

yes.  but not yet.

 'Write programs that do one thing and do it well. Write programs to work
 together. Write programs to handle text streams, because that is a
 universal interface'
 
 (Doug McIlroy)

does it count to have multiple independent privsep processes that
exchange binaries imsgs instead of using text streams?  relayd has
parent, hce, pfe, relay, and ca.  ... ;-)

Reyk



Re: [Bulk] Re: Server Name Indication (SNI) relayd

2014-07-24 Thread Kevin Chadwick
On Thu, 24 Jul 2014 17:20:16 +0200
Reyk Floeter wrote:

  'Write programs that do one thing and do it well. Write programs to work
  together. Write programs to handle text streams, because that is a
  universal interface'
  
  (Doug McIlroy)  
 
 does it count to have multiple independent privsep processes that
 exchange binaries imsgs instead of using text streams?  relayd has
 parent, hce, pfe, relay, and ca.  ... ;-)

heh heh, no I believe the context is those that have any element that is
human facing (tools), atleast wherever performance is generally
adequate.

Out of interest I guess relayds ssl and nginx libressl privsep is
very similar?



Systemd logging for example and *conf would be ones that should have
taken this universal interface advise as the rare few who need binary
log performance can easily convert the logs or process them once and log
sizes are not an issue on modern hdd but with binary logs you add
difficulties for processing tool compatibility, sappend, recovery
issues from partially wiped or failing drives even more so on ext4 etc..