> So, can anyone suggest the preferred way of enforcing 128-bit SSL
> throughout an entire ColdFusion site that runs using an Apache-like
> Web server?
>
> If I take out the jrunfilter line in the config file, and rely on the
> file extensions to pass requests to ColdFusion, it
well it can differ between web servers but among the CGI variables the
webserver will pass to CF there should be a CERT_KEYSIZE variable in
the CGI scope. That's if you can't get it to happen on the server end,
which should be possible. It was still called Netscape Enterprise
Server the last I used
Yeah, that's exactly what happens, the connection is denied. An you
can only do it at the vhost level, I believe. N'mind then. ;) Just
thought I'd throw it out there.
cheers,
barneyb
On 9/13/05, Mike Chabot <[EMAIL PROTECTED]> wrote:
> Removing support for anything other than 128-bit connecti
Removing support for anything other than 128-bit connections is
another option. The two concerns that come to mind are the error
message that the user sees and whether or not I can lock down specific
directories, as opposed to the entire site. The last time I tested
removing support for 56-bit SSL,
the ColdFusion pages make it through the
> restriction because there is a "jrunfilter" (like and ISAPI filter)
> which captures all the ColdFusion requests before the Web server SSL
> check is reached.
>
> So, can anyone suggest the preferred way of enforcing 128-bit S
. All the ColdFusion pages make it through the
restriction because there is a "jrunfilter" (like and ISAPI filter)
which captures all the ColdFusion requests before the Web server SSL
check is reached.
So, can anyone suggest the preferred way of enforcing 128-bit SSL
throughout an entire
6 matches
Mail list logo
