> You can, for example, test this with command:
>
> "while true; do echo R; done | openssl s_client -connect ssl_host:443"
>
> Maybe there should be added something like "renegotiation_rate" ?
Real-world servers already do this. It's kind of redundant for OpenSSL
to
do this as well becau
Hello,
> > You can, for example, test this with command:
> >
> > "while true; do echo R; done | openssl s_client -connect ssl_host:443"
> >
> > Maybe there should be added something like "renegotiation_rate" ?
>
> Real-world servers already do this. It's kind of redundant for OpenSSL
> to
>
> > Real-world servers already do this. It's kind of redundant
> > for OpenSSL to
> > do this as well because almost all applications also support non-SSL
> > connections. A renegotiation callback might not be a bad idea though, so
> > that applications can better track the load clients are pl
Hello,
> > Application layer do not see this.
>
> Right, that's why I suggested making it visible to the application
> layer.
> The application layer already has to have code to handle excessive load
> because there are many ways to place load that are not visible at the SSL
> layer. Bette
