Server problems caused by 'transparent' self-signed SSL certificatesOne of the issues with allowing self-signed SSL certificates to be
automatically used for transparent encryption over Right now, a server-side program that care can more or less assume that
a SSL-encrypted connection means either that it is securely talking
to the real end user's machine or that the end user has been actively
compromised (which it can't do anything about). It may thus use things
like 'you can only talk to this service over If you allow self-signed SSL certificates to be used transparently
for encryption in However, the web server does not know and cannot know this information,
since it has no way of finding out if it is talking to the real end
machine or to a man in the middle. As such, server side applications
can no longer assume that a (Server side applications cannot do things like feed Javascript to the client browser to see if it is really connecting directly to them, because the man in the middle can rewrite that Javascript on the fly.) (In theory the one way out of this is to require everything to have client side certificates. However, I do not believe that this is any more practical than trying to make all server side applications instantly give up any 'SSL means security' beliefs that they may have.) (3 comments.)
|
These are my WanderingThoughts GettingAround This is part of CSpace, and is written by ChrisSiebenmann. * * * Atom feeds are available; see the bottom of most pages. Categories: links, linux, programming, python, snark, solaris, spam, sysadmin, tech, unix, web |