The file "wpkg.xml" is stored local.
If a package is to be removed, the line
"<remove cmd='(uninstallcommand)' />"
is taken from this local file.
the /uninstallcommand/ is executed with the privileges of SYSTEM or
Administrator.
I see a potential risk:
By modifying the local file "wpkg.xml" any user can start programs
with the
privileges of SYSTEM or Administrator.
But if someone managed to alter wpkg.xml, than that person probably can
execute tasks as SYSTEM or Administrator already?
not nessesarily.
1st: the file could be writable by a "Power User" or "Hauptbenutzer" in
German. (default in XP i think)
2nd: the File could be writable by anyone (lazy Admin)
3rd: there is the possibility of an security issue, giving a user
write-access to files.
4th: running a knoppix-cd could give me the possibility to modify files
on an nfts-partition. (yes, I could alter other files to gain access
into the system)
I know, it is a veeery long shot but anyway.
(...)
> (...)
>
> So maybe we should always use the "remove cmd" from the server?
Now we are doing this in all possible situations.
best regards (and thanks for the mailaddr.)
Gordon Klimm
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
wpkg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wpkg-users
