Fixing a Hole in the Web
Technology Review (01/12/10) Naone, Erica
A fix that the Internet Engineering Task Force recently approved to patch a vulnerability in the protocol that encrypts sensitive Web-based communications and transactions is expected by experts to take a year or more to be fully deployed. The patch fixes the Transport Layer Security (TLS) protocol, which is built into Web browsers and servers and shields critical information, and which has supplanted the Secure Socket Layer protocol. By exploiting the TLS flaw, an attacker can commandeer the first moment of the encrypted conversation between a Web browser and server and insert a command of his own. Exploiting the vulnerability requires the hacker to first carry out a man in the middle attack to capture traffic between the client and the server, and then take advantage of TLS' renegotiation feature. This feature permits a Web server or client to revise some of the parameters of an encrypted session while the session is taking place. Security professional Frank Breedijk says the protocol is patched by a draft fix that effectively produces two versions of TLS--thus keeping the danger of attack alive if either the client or the server fails to install the patch. Apache Software Foundation founding director Ben Laurie says that this double installation requirement makes the fix "unprecedented," so browser makers working to correct the problem will need to make accommodations for a period in which the client will continue communicating with unpatched servers.
Tuesday, January 12, 2010
Blog: Fixing a Hole in the Web
Subscribe to:
Post Comments (Atom)
Blog Archive
-
►
2012
(35)
- ► April 2012 (13)
- ► March 2012 (16)
- ► February 2012 (3)
- ► January 2012 (3)
-
►
2011
(118)
- ► December 2011 (9)
- ► November 2011 (11)
- ► October 2011 (7)
- ► September 2011 (13)
- ► August 2011 (7)
- ► April 2011 (8)
- ► March 2011 (11)
- ► February 2011 (12)
- ► January 2011 (15)
-
▼
2010
(183)
- ► December 2010 (16)
- ► November 2010 (15)
- ► October 2010 (15)
- ► September 2010 (25)
- ► August 2010 (19)
- ► April 2010 (21)
- ► March 2010 (7)
- ► February 2010 (6)
- ▼ January 2010 (6)
-
►
2009
(120)
- ► December 2009 (5)
- ► November 2009 (12)
- ► October 2009 (2)
- ► September 2009 (3)
- ► August 2009 (16)
- ► April 2009 (4)
- ► March 2009 (20)
- ► February 2009 (9)
- ► January 2009 (19)
-
►
2008
(139)
- ► December 2008 (15)
- ► November 2008 (16)
- ► October 2008 (17)
- ► September 2008 (2)
- ► August 2008 (2)
- ► April 2008 (12)
- ► March 2008 (25)
- ► February 2008 (16)
- ► January 2008 (6)
-
►
2007
(17)
- ► December 2007 (4)
- ► November 2007 (4)
- ► October 2007 (7)
Blog Labels
- research
- CSE
- security
- software
- web
- AI
- development
- hardware
- algorithm
- hackers
- medical
- machine learning
- robotics
- data-mining
- semantic web
- quantum computing
- Cloud computing
- cryptography
- network
- EMR
- search
- NP-complete
- linguistics
- complexity
- data clustering
- optimization
- parallel
- performance
- social network
- HIPAA
- accessibility
- biometrics
- connectionist
- cyber security
- passwords
- voting
- XML
- biological computing
- neural network
- user interface
- DNS
- access control
- firewall
- graph theory
- grid computing
- identity theft
- project management
- role-based
- HTML5
- NLP
- NoSQL
- Python
- cell phone
- database
- java
- open-source
- spam
- GENI
- Javascript
- SQL-Injection
- Wikipedia
- agile
- analog computing
- archives
- biological
- bots
- cellular automata
- computer tips
- crowdsourcing
- e-book
- equilibrium
- game theory
- genetic algorithm
- green tech
- mobile
- nonlinear
- p
- phone
- prediction
- privacy
- self-book publishing
- simulation
- testing
- virtual server
- visualization
- wireless
No comments:
Post a Comment