Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Evan VanDyke found onsocssl on IDS 11.7 far slower than onsoctcp (15.1 versus 2.7 seconds for 20 images) even with more VPs. Benjamin Thompson planned to test later, needing it only because SQLI sends passwords in clear. Madison Pruet suggested the simple password encryption CSM; Benjamin found it by searching SPWDCSM. The SSL slowdown was not solved.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
We are in the process of implementing SSL in transit encryption for IDS 11.7.
We are testing on a few servers, and there is an obvious performance drop when
using onsocssl. I have tried implementing more VPs to boost performance, but
it has a minimal effect. The primary data we need encrypted are image blobs.
To give an example of performance drop, an onsoctcp connection serving up 20
images takes 2.682 seconds. The same request, but with onsocssl, takes 15.1
seconds. This is obviously an unacceptable degredation in performance.
I'm hoping for any advice on what can be done to boost performance. Has anyone
else faced this kind of performance drop when using ssl on IDS?
Hi,
I can't help at the moment but we will be testing this in the next month or
two and would be happy to confer then if that's useful for you.
I don't know about you but the only reason we need this is because the SQLI
protocol sends the db credentials, specifically the password, in the clear. It
would a nice enhancement to encrypt the password by default.
Ben.
Why not use the simple password encryption CSM?
From: "BENJAMIN THOMPSON" <benjamin.thompson@bskyb.com>
To: ids@iiug.org
Date: 08/03/2015 03:02 PM
Subject: Re: SSL Performance [35553]
Sent by: ids-bounces@iiug.org
Hi,
I can't help at the moment but we will be testing this in the next month or
two and would be happy to confer then if that's useful for you.
I don't know about you but the only reason we need this is because the SQLI
protocol sends the db credentials, specifically the password, in the clear.
It
would a nice enhancement to encrypt the password by default.
Ben.
***************************************************************************=
****
Forum Note: Use "Reply" to post a response in the discussion forum.
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.