Package Details: nginx-mainline-boringssl 1.13.4-1

Git Clone URL: https://aur.archlinux.org/nginx-mainline-boringssl.git (read-only)
Package Base: nginx-mainline-boringssl
Description: Lightweight HTTP server and IMAP/POP3 proxy server, mainline release
Upstream URL: https://nginx.org
Licenses: custom
Conflicts: nginx
Provides: nginx
Submitter: 4679kun
Maintainer: kasei
Last Packager: kasei
Votes: 2
Popularity: 0.019371
First Submitted: 2015-12-05 02:14
Last Updated: 2017-09-25 06:29

Required by (65)

Sources (5)

Latest Comments

RubenKelevra commented on 2017-07-15 00:21

Hey kasel,

I thought more about those once:

nginx_http2_hpack.patch - increases compression on h/2
nginx__dynamic_tls_records.patch - increases responsiveness on h/2

Best regards

Ruben

kasei commented on 2017-07-10 08:41

@RubenKelevra yeah, I know those patchs. But this package is for who want boringssl. so I won't apply cloudflare's patchs to this package. If you just want chacha20 check aur/nginx-mainline-mod4679 for nginx with cloudflare's patch.

RubenKelevra commented on 2017-07-05 14:03

Hey kasei,

just me again, wondering if you know these patches:

https://github.com/cloudflare/sslconfig/tree/master/patches

Sounds interesting, but I'm not sure if they still apply.

If you get time and fun to play around - maybe take a look. :)

Best regards

Ruben

RubenKelevra commented on 2017-07-03 23:41

I was wondering, why TLS1.3 isn't working, is this as expected? I thought BoringSSL and Nginx already got support for them. :)

RubenKelevra commented on 2017-07-01 18:28

Thanks kasei!

The version Tag would work fine, the main reason I’ve asked for is not really to see the version of boringssl but beeing able to identify which version of boring-ssl is being built-in into which version of this package.

I’ve used to maintain nginx-mainline-libressl but I dropped it, but you can take a look at it, if you need an inspiration. :)

kasei commented on 2017-07-01 08:59

1. Changed checksum algorithm to sha256.
2. I do thought about set a boringssl version, but didn't find a good way to show two softwares' version in pkgver. I can only set a commit id in pkgver, like "1.13.2.6c8366e1".

RubenKelevra commented on 2017-06-30 14:48

Does this package use boringssl from master-branch? What do you think about changing to explicit versions like 2214? This would allow updates of boringssl and shows which version is running.

RubenKelevra commented on 2017-06-30 14:42

Hey!

Nice package, but I like to see SHA2 instead of the ancient 20 years unsafe MD5 hashes for those packages. :)