You are not logged in.
Pages: 1
Hey guys,
I've just come over to Arch after far too long running CentOS. I spent a lot of time there maintaining a custom nginx RPM which linked statically against LibreSSL. Basically the idea is to allow easy migration of the one thing everyone's most worried about (the websever) without dealing with an OS-wide replacement of OpenSSL.
I based my build on the existing nginx-custom package, which supplied the systemd scripts, although I've stripped the build back a lot, as I also aim to keep it very minimal.
Anyway, given I'm on day 0 with Arch Linux, I'd appreciate if anyone can point at anything dumb going on in this build. You can download it at the below address, on a server which is being served the very package I'm talking about.
http://176.58.124.142/nginx-libressl-1. … src.tar.gz
With that said, is this the sort of thing worth submitting to AUR? Any advice appreciated.
Last edited by technion (2015-04-03 08:09:18)
Offline
Hey guys,
I've just come over to Arch after far too long running CentOS. I spent a lot of time there maintaining a custom nginx RPM which linked statically against LibreSSL. Basically the idea is to allow easy migration of the one thing everyone's most worried about (the websever) without dealing with an OS-wide replacement of OpenSSL.
[...]
I like the idea of nginx with libressl; but if maintenance is your concern; wouldn't you be better of with the stock nginx which (uses openssl and) is automatically updated from the repos?
With that being said, can't you compile based on the existing libressl package?
Offline
I like the idea of nginx with libressl; but if maintenance is your concern; wouldn't you be better of with the stock nginx which (uses openssl and) is automatically updated from the repos?
With that being said, can't you compile based on the existing libressl package?
Maintenance isn't so much a concern (I always had my CentOS/Redhat RPM updated the very day of any major issue) as much moving my web services to what I view as a better platform. Thanks for linking me the libressl package, but the comments on that package are enough to point out the instability that people in general are in for if they try to deploy libressl globally. Deploying it for one specific application (nginx in this case) is a lot easier to test and keep stable.
Offline
You can always submit to the AUR. If it turns out the package isn't used by anyone you can always pull it later. My advice would be to just give it a shot (if you are willing to maintain the package that is).
Offline
Pages: 1