Triggering via email is not universal, because your email client can be configured to remove any attachments or this will be done by AV on email server side (corporate environment). Classic wormable vector implies sending crafted data directly to a process input (network port).
-
-
Why not just remove the requirement for "database update channel" and specify "no user interaction"? If that's the real reason for that requirement, then problem solved.
-
Btw, returning to step back, probably "the truth is out there", if attachment is small and GMail places it "as is" on a web-page (attachment will be downloaded among other web page data), FS stack will see it. But in case of not small attachments this situation is excluded.
End of conversation
New conversation -
-
-
Even when no browsers are running into my system?)
-
Is this a new requirement? LOL!
- 2 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

