Joe Souza joe.so...@netmotionwireless.com wrote:
It is at the very least ignorant to call Microsoft's CreateProcess
behavior braindead.
What else is it then?
If anything it shows your complete lack of understanding of the issue.
Really? Let's see how good your understanding of the Win32 API
Joe Souza joe.so...@netmotionwireless.com wrote:
Stop sending HTML!
In Win32, WinExec is merely a wrapper around CreateProcess.
CreateProcess needs to support the same semantics that WinExec did.
It does: the Win16 API does NOT support LFNs, just SFNs. With this
precondition (which you did
You can blame the Mail app on Android for the HTML.
You have illustrated below exactly the reason why CreateProcess needs to handle
unquoted paths. Thanks for helping me make my point.
-Original Message-
From: Stefan Kanthak [mailto:stefan.kant...@nexgo.de]
Sent: Wednesday, July 30,
Joe Souza joe.so...@netmotionwireless.com wrote:
You can blame the Mail app on Android for the HTML.
I dont: I but blame PEBKAC for the HTML or other deficiencies.
You have illustrated below exactly the reason why CreateProcess
needs to handle unquoted paths. Thanks for helping me make my
Michael Cramer mike.cra...@outlook.com wrote:
sudo make-me-a-sandwich.py
How is this different from any other temporary, per-process elevation system?
0. neither sudo nor make-me-a-sandwich.py nor the OS where these programs
typically run have a CreateProcess*() system call which
Michael Cramer mike.cra...@outlook.com wrote:
I think you're arguing semantics here.
Of course.
Of course the specifics of how a particular program is executed
will be different between command line and GUI-based OS'.
Really?
Is there any need for this difference you state?
BTW: what is the
So reading the links you provided I semi-agree with you. I think the
problem boils down to this part of your initial e-mail:
PS: yes, it needs administrative privileges to write C:\Program.exe.
BUT: all the user account(s) created during Windows setup have
administrative privileges.
My
Gynvael Coldwind wrote:
So reading the links you provided I semi-agree with you. I think the
problem boils down to this part of your initial e-mail:
PS: yes, it needs administrative privileges to write C:\Program.exe.
BUT: all the user account(s) created during Windows setup have