undefined | Better HN

0 pointstime4tea28d ago0 comments

Thanks for the info, but I'm a bit confused, sorry.

The reason for hitch was that tls and caching are a different concern, and the current recommendation is to use haproxy, which also isnt integrated into varnish/vinyl.

But you say that the reason to migrate off hitch is that its not integrated?

But what happend to separation of concerns, then? Is the plan to integrate tls termination into vinyl? Is this a change of policy/outlook?

Thanks!

0 comments

perbu27d ago

Varnish Software released hitch to facilitate TLS for varnish-cache.

Now that Varnish has been renamed, Varnish Software will keep what has been referred to as a downstream version or a fork, which has TLS built in, basically taking the TLS support from Varnish Enterprise.

This makes Hitch a moot point. So, I assume it'll receive security updates, but not much more.

Wrt. separation of concerns. Varnish with in-core TLS can push terabits per second (synthetic load, but still). Sure, for my blog, that isn't gonna matter, but having a single component to run/update is still valuable.

In particular using hitch/haproxy/nginx for backend is cumbersome.

TLS is a primary concern on the internet today.

time4teaOP27d ago

Totally agree. But, if i may, the docs on varnish and tls are hella confusing. I just re-read the varnish v9 docs, and its not clear at all that/if it supports tls termination.

Literally every doc, from the install guide to the "beef in the sandwich" talks about it NOT supporting tls termination... then one teeny para in "extra features in v9.0" mentions 'use -A flag'...

This is cool! But also, worth mentioning. Sure I know its an open source project so you don't owe anyone anything, but also one with a huge company behind it - and this is a huge change of stance and also, sounds cool.

perbu26d ago

https://github.com/varnish/varnish/issues/33

It should be fixed fairly quick.

perbu27d ago

we're not at all a huge company. we're 80 people with a lot on our plates trying to juggle this on top of everything else.

but I truly appreciate the feedback. I'll reach our to the team working on this and see if I can make this a bit clearer.

slink_vinyl27d ago

So because perbu was clearly talking with his varnish software hat on, here's the perspective from someone working on Vinyl Cache FOSS only:

I already commented on the separation of concerns in the tutorial, and the unpublished project which one person from uplex is working on full time will have the key store in a separate process. You might want to read the intro of the tutorial if you have not done so.

But the main reason for why the new project will be integrating TLS more deeply has not been mentioned: It is HTTP/3, or rather QUIC. More on that later this year.

j / k navigate · click thread line to collapse

0 comments

perbu27d ago

Varnish Software released hitch to facilitate TLS for varnish-cache.

This makes Hitch a moot point. So, I assume it'll receive security updates, but not much more.

In particular using hitch/haproxy/nginx for backend is cumbersome.

TLS is a primary concern on the internet today.

time4teaOP27d ago

Totally agree. But, if i may, the docs on varnish and tls are hella confusing. I just re-read the varnish v9 docs, and its not clear at all that/if it supports tls termination.

Literally every doc, from the install guide to the "beef in the sandwich" talks about it NOT supporting tls termination... then one teeny para in "extra features in v9.0" mentions 'use -A flag'...

perbu26d ago

https://github.com/varnish/varnish/issues/33

It should be fixed fairly quick.

perbu27d ago

we're not at all a huge company. we're 80 people with a lot on our plates trying to juggle this on top of everything else.

but I truly appreciate the feedback. I'll reach our to the team working on this and see if I can make this a bit clearer.

slink_vinyl27d ago

So because perbu was clearly talking with his varnish software hat on, here's the perspective from someone working on Vinyl Cache FOSS only:

But the main reason for why the new project will be integrating TLS more deeply has not been mentioned: It is HTTP/3, or rather QUIC. More on that later this year.

j / k navigate · click thread line to collapse