Fri 21 Dec 2007
Gmail + Internet Explorer = Trouble
Posted by Syd Tash under Alerts
A California security company is warning that a flaw in Internet Explorer (IE) could allow a hacker to access your Google Gmail account. A hacker must have direct physical access to the computer. So this is mostly a concern to those who use public computers, or who share their computer with others.
When combined with a flaw in the way Gmail displays its URLs, the vulnerability could expose your Gmail account signin info, and therefore could allow someone to get into your account. Your confidential data remains in the browser cache until you clear your history by clicking Tools, Internet Options, Clear History.
Microsoft denied the problem exists in IE, but could not immediately explain away the bug. No comment yet from Google.
If you are a Gmail user, always clear your history after you exit your account. Or switch to the Firefox browser.
Syd Tash is a noted computer security consultant and author of How to Protect Your Computer Online. He has been keeping Internet surfers safe and secure since the last century. Find out how he does it; protect your own computer with five layers of protection right here: = > http://MyPCSecuritySite.com
You may include these Tips in your Web sites and publications, provided they remain unchanged and include the above paragraph, with the author’s name and Web site. You can also get a direct URL to this post. Click the title, then copy the URL in the browser address bar.
If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!
One Response to “ Gmail + Internet Explorer = Trouble ”
Comments:
Leave a Reply
` `Trackbacks & Pingbacks:
-
Pingback from Internet Explorer History » Gmail + Internet Explorer = Trouble
January 11th, 2008 at 11:12 pm[...] Syd Tash wrote an interesting post today on Gmail + Internet Explorer = TroubleHere’s a quick excerptYour confidential data remains in the browser cache until you clear your history by clicking Tools, Internet Options, Clear History. Microsoft denied the problem exists in IE, but could not immediately explain away the bug. … [...]
