Perimeter
11/28/2011
12:46 PM
Taher Elgamal
Taher Elgamal
Commentary
Connect Directly
RSS
E-Mail
50%
50%
Repost This

SSL's Future

SSL will evolve to meet requirements for e-commerce and mobile

So what will happen to the current e-commerce world based on SSL and all of the new authentication methods under way?

SSL has been the target for a variety of attacks, many of which have been in the news lately. I believe that it will be extremely difficult to fundamentally change the models for e-commerce after 15 years of growth, despite the fraud and threats we know about. The appropriate way to manage fraud better is to work on the existing systems to improve how parties assure themselves of the identities of others involved in transactions.

There is actually more than one way that authentication can be supported within the SSL framework as it stands.

Any strong authentication can simply be used after the one-sided server authentication and encryption session has been established. At this point, the server can request any authentication information from the client, and the authentication can happen within the encrypted session. Each website can choose the authentication method it desires, as long as browser and client support can be established somehow.

Alternatively, the strong authentication method desired could be used to “unlock” a private key with a digital certificate on the client side that can be used to provide the client authentication requested by the SSL server.

Either way, the current infrastructure can, in fact, support multiple authentication methods that will help us mitigate the dependence on user passwords.

I wish that the technical community could collaborate on improving the existing e-commerce infrastructure. Many improvements are needed, for sure, but incremental improvements have always worked better than calling for a new infrastructure that would not be possible to actually put together.

My prediction is that SSL will grow with the e-commerce needs and that new versions and new implementations will meet the expectations for growing e-commerce and mobile commerce requirements.

Recognized in the industry as the "inventor of SSL," Dr. Taher Elgamal led the SSL efforts at Netscape. He also wrote the SSL patent and promoted SSL as the Internet security standard within standard committees and the industry. Dr. Elgamal invented several industry and government standards in data security and digital signatures area, including the DSS government standard for digital signatures. He holds a Ph.D. and M.S. in Computer Science from Stanford University.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-5704
Published: 2014-04-15
The mod_headers module in the Apache HTTP Server 2.2.22 allows remote attackers to bypass "RequestHeader unset" directives by placing a header in the trailer portion of data sent with chunked transfer coding. NOTE: the vendor states "this is not a security issue in httpd as such."

CVE-2013-5705
Published: 2014-04-15
apache2/modsecurity.c in ModSecurity before 2.7.6 allows remote attackers to bypass rules by using chunked transfer coding with a capitalized Chunked value in the Transfer-Encoding HTTP header.

CVE-2014-0341
Published: 2014-04-15
Multiple cross-site scripting (XSS) vulnerabilities in PivotX before 2.3.9 allow remote authenticated users to inject arbitrary web script or HTML via the title field to (1) templates_internal/pages.tpl, (2) templates_internal/home.tpl, or (3) templates_internal/entries.tpl; (4) an event field to ob...

CVE-2014-0342
Published: 2014-04-15
Multiple unrestricted file upload vulnerabilities in fileupload.php in PivotX before 2.3.9 allow remote authenticated users to execute arbitrary PHP code by uploading a file with a (1) .php or (2) .php# extension, and then accessing it via unspecified vectors.

CVE-2014-0348
Published: 2014-04-15
The Artiva Agency Single Sign-On (SSO) implementation in Artiva Workstation 1.3.x before 1.3.9, Artiva Rm 3.1 MR7, Artiva Healthcare 5.2 MR5, and Artiva Architect 3.2 MR5, when the domain-name option is enabled, allows remote attackers to login to arbitrary domain accounts by using the corresponding...

Best of the Web