Thanks Jochen, that's very clear.
One thing became clear in a customer meeting the other day - All data should be encrypted in transit, and encrypted at rest. Is there any recommended ways of partitioning customer data in a secure way - or would we need to run physically separate servers to achieve this? s On Thursday, August 13, 2015 at 9:14:55 AM UTC+1, Jochen Schalanda wrote: > > Hi Simon, > > support for HTTPS in the GELF HTTP input will be added in Graylog 1.2.0. > If you cannot wait that long, you could put a reverse proxy or a small tool > like stunnel (https://www.stunnel.org/index.html) in front of the input. > > > Cheers, > Jochen > > On Thursday, 13 August 2015 10:08:59 UTC+2, Simon H wrote: >> >> Does anyone know if you can post GELF over HTTPS? I can't seem to find >> any info on this, but suspect my customers will want to know their data is >> going over an encrypted link >> >> I'm guessing one way would be to proxy the data through apache or >> similar, but wanted to ask first. >> >> s >> > -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/4029c404-69ef-42df-8850-dc40ba5e3941%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
