I am currently using 1024 bit dhparams for maximum compatibility
Here is my ssllabs report :
https://www.ssllabs.com/ssltest/analyze.html?d=filterbypass.me
If i remove the DH from my cipher suites , will handshake simulation be
still a success for all browsers listed in the ssllabs report above
Hello!
On Tue, Jul 01, 2014 at 03:10:07AM -0400, khav wrote:
> Thanks Maxim and GreenGecko for the insights
>
>
> The worker process does match my number of cpu cores (running on 8 cores
> atm)
Good. It may be also good idea to make sure you don't have
multi_accept enabled, just in case.
>
Thanks Maxim and GreenGecko for the insights
The worker process does match my number of cpu cores (running on 8 cores
atm)
How can i know the number of handshakes per seconds occurring on the
server
The openssl speed result have been posted on http://pastebin.com/hNeVhJfa
for readability
Yo
Hello!
On Sat, Jun 28, 2014 at 01:14:16AM -0400, khav wrote:
> For my site , ssl seems to be slow even though i got A+ on sslabs
> (implemented ocsp stapling, Forward Secrecy , spdy)
Note that SSL Labs grades are about security, not about speed.
> Here is the result from pingdom
>
> http://t
Hi!
On Sat, 2014-06-28 at 01:14 -0400, khav wrote:
> For my site , ssl seems to be slow even though i got A+ on sslabs
> (implemented ocsp stapling, Forward Secrecy , spdy)
>
> Here is the result from pingdom
>
> http://tools.pingdom.com/fpt/#!/cc2MfH/https://www.filterbypass.me/
>
>
> Notice
For my site , ssl seems to be slow even though i got A+ on sslabs
(implemented ocsp stapling, Forward Secrecy , spdy)
Here is the result from pingdom
http://tools.pingdom.com/fpt/#!/cc2MfH/https://www.filterbypass.me/
Notice the high connect time and high ssl negociation time
Here is my ng
