Summary: | antivirus hooks for portage | ||
---|---|---|---|
Product: | Portage Development | Reporter: | solar (RETIRED) <solar> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | VERIFIED LATER | ||
Severity: | enhancement | CC: | lordvan, prez, pYrania, seemant, wschlich |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Patch that adds the hooks to ebuild to do antivirus scanning |
Description
solar (RETIRED)
2003-08-09 10:05:56 UTC
Created attachment 15819 [details, diff]
Patch that adds the hooks to ebuild to do antivirus scanning
A Note on this patch. This adds the basic hooks but what action to take when a virus is found is not written yet. [ ${ret} != 0 ] && myfail="something here " For that I would want input from other devs. We could exit and refuse to install. Warn the user etc.. (or Prompt for input?) seemant reported a few bugs directly to me via irc and has been really helpfull in the testing, debugging phase. I'll be posting an updated patch in the next day or so. Lack of time to work on this feature. I still lack the time to support this feature, antiviral engines differ so much that it somewhat becomes difficult to want to even maintain such a feature when the dynamic differences between them vary so much. If anybody else has some creative ideas on protecting portage in such a way I'd love to hear about them or better see the code :) solved by introduction of portage bashrc handling some time ago and or the recent addition of hooks. |