Re: if I encrypt key data why do I want or need SSL?
- From: "Rob R. Ainscough" <robains@xxxxxxxxxxx>
- Date: Tue, 28 Mar 2006 14:13:58 -0800
How would they put junk data into my system? Are you assuming they've been
able to hack in via an account? Unless ADO.NET 2.0 has some fundamental
security flaws when communicating to a SQL server? I could encrypt the
entire message also, all that SSL does for me is provide encrypted access to
external sources beyond the control of my security.
Slammer real world impact has been relatively low threat (which has been
countered via a patch a long time ago) -- in fact, it will provide zero
benefit in my situation (even if the SQL server is not patched) -- gaining
Windows Service security context (sends 376 bytes to UDP port 1434 for
buffer overflow) means nothing to the way my security is established -- the
only way they can obtain any value is if they were able to locate my strong
name DLL responsible for all security aspects, assuming they could get into
the DLL and somehow decompile it (without the public/private key pair) they
would then have to discover where in the DLL the call is to get the
encrypted key and then also have to realize that key needs to be
unencrypted.
In fact, the way my security is enforced has minimal reliance on the OS or
the SQL server -- about all a hacker could do is delete or change data and
that is assuming they have found a flaw in the OS/Service (i.e. slammer) --
data changes will soon be rejected by my applications as they will not
validate and be rejected as bogus data.
Can you provide details of how you might attack a strongly named assembly?
Opening the file in binary will not be terribly helpful and you can't
decompile it to any useful context, so please explain?
Web Services use the same approach, none of my web service will do anything
if they don't get a valid encrypted key as a parameter to all and any method
made available by the service and any sensitive data passed to from a web
service is always encrypted.
Rob
"Andy" <ajj3085@xxxxxxxxxxxx> wrote in message
news:1143573820.754223.139480@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
It sounds like it would still be possible for an attacker to put junk
data into your system. Take your encrypted value, and replace it with
another encrypted value. SSL would prevent this kind of tampering,
since the whole message is signed, not just individual fields.
Leaving port 1433 open to the internet has caused problems in the past;
perhaps you heard of the slammer worm?
Even with a strongly named assembly you are still open to some kinds of
attacks.
Finally you may need to communicate data with a web service at some
point, and I doubt you'd want to provide your key to the 3rd party.
.
- Follow-Ups:
- Re: if I encrypt key data why do I want or need SSL?
- From: Andy
- Re: if I encrypt key data why do I want or need SSL?
- From: Henning Krause [MVP]
- Re: if I encrypt key data why do I want or need SSL?
- References:
- if I encrypt key data why do I want or need SSL?
- From: Rob R. Ainscough
- Re: if I encrypt key data why do I want or need SSL?
- From: Andy
- if I encrypt key data why do I want or need SSL?
- Prev by Date: Custom Security
- Next by Date: Re: if I encrypt key data why do I want or need SSL?
- Previous by thread: Re: if I encrypt key data why do I want or need SSL?
- Next by thread: Re: if I encrypt key data why do I want or need SSL?
- Index(es):
Relevant Pages
|