Larry Hall (Cygwin) wrote:
Carlo Florendo wrote:
Neeraj Garg (TRANSPORT) wrote:
I am not sure if that was request for help or just a witty comment
back. I am willing to help Cygwin dev get in touch with appropriate
folks in Windows Vista team to resolve the issue.
It was a witty comment and it really involves the windows kernel. In
any case, please do all you can so that your Vista team contacts read
this (c/o Corinna Vinschen)
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1020271&SiteID=1&mode=1
<http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1020271&SiteID=1&mode=1>
I know CreateProcess call should have worked.
Yes, it should have, at least, in older windows versions. But vista
has had some sort of security elevation issues that causes process
creation problems.
I am not in that team to give you information on what has changed in
Vista compared to XP. All I can say is that I would like to see the
product fixed and am willing to offer help.
PS: Some Vista users mentioned to me that Cygwin does not work and
hence I am involved to make sure we can work together to make it work.
If any dev would like to work with Vista dev team to get the product
ready soon, please let me know.
Neeraj
There have been discussions lately, precisely on process spawning on
Cygwin. It appears to be a serious "security" bug on Vista. For
details, read the thread started by Corinna Vinschen (senior cygwin
developer) on:
Wholy crap - Microsoft really is insane. This is not a "security bug",
it is yet another example of the sort of design philosophy that makes
Windows the pile of S**t that it is. 6 million lines (Vista is
presumably much more than even that - thats the number I heard for XP)
of that kind of thinking is why virus/spy authors have such an easy
task. Microsoft really doesn't have any idea what it takes to make a
system secure, do they?
--
Greg
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/