Get your own customer support community
 

Code injection intrusion attempt triggered by Google Desktop Action

Hi James,

Thanks for replying to me by email to my question about “code injection intrusion attempt alert when using Google Desktop” (SPF Ticket #001-00-266757). This was occurring when, after a desktop search, I clicked on the file to open it. Thanks for the tips on how to make an exception for googledesktop.exe so as to allow code injections and buffer overflows.

My question, James, is not whether I can make an exception, but should I make an exception for googledesktop.exe? What concerns me are issues like Google’s “single sign on” (SSO). Mike Howard (Kim Cameron on GOOGs single sign on design vulnerability) has written about this. So has Kirk Cameron (Hole in Google SSO service). Supposedly, Google fixed this bug in September according to ZDNet (Google closes hole in Single Sign-On service).

As a skeptic and cynic (and mildly paranoid), I hesitate to make an exception. I denied each attempt and still had access to the file. So I was happy. I still don’t understand the injection attempt and thus hesitate to make an exception. It may be perfectly ok for all I know; but then again, it may be perfectly exploitable. I don’t know.

Take care,

--jerry
 
silly I’m just double-checking.
Inappropriate?
1 person has this question

User_default_medium