<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://weblogs.asp.net/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>How to manipulate files inside Inetpub/wwwroot all day without being bugged by UAC</title><link>http://weblogs.asp.net/bleroy/archive/2007/03/14/how-to-manipulate-files-inside-inetpub-wwwroot-all-day-without-being-bugged-by-uac.aspx</link><description>A lot has been written about UAC . Some choose to disable it. I chose not to and I&amp;#39;m doing just fine. At least, I don&amp;#39;t have to type in my password on every prompt like on some other OS that likes to mock us on TV ;) Anyway, the one place where</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP1 (Build: 20510.895)</generator><item><title>re: How to manipulate files inside Inetpub/wwwroot all day without being bugged by UAC</title><link>http://weblogs.asp.net/bleroy/archive/2007/03/14/how-to-manipulate-files-inside-inetpub-wwwroot-all-day-without-being-bugged-by-uac.aspx#6956224</link><pubDate>Thu, 12 Mar 2009 08:01:03 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:6956224</guid><dc:creator>victor</dc:creator><author>victor</author><description>&lt;p&gt;Thanks very much. Bertrand Le Roy. I will also do some reading from the best parctice. &lt;/p&gt;
&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=6956224" width="1" height="1"&gt;</description></item><item><title>re: How to manipulate files inside Inetpub/wwwroot all day without being bugged by UAC</title><link>http://weblogs.asp.net/bleroy/archive/2007/03/14/how-to-manipulate-files-inside-inetpub-wwwroot-all-day-without-being-bugged-by-uac.aspx#6955294</link><pubDate>Wed, 11 Mar 2009 17:30:37 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:6955294</guid><dc:creator>Bertrand Le Roy</dc:creator><author>Bertrand Le Roy</author><description>&lt;p&gt;@Victor: please don't take my advice as the official Microsoft recommendation but only as my opinion. If those developers must publish the development site to the production server, this seems quite normal. I'm not sure what to do if that is not acceptable. One thing you might want to do is turn on write audits on that directory. That won't prevent attacks from insiders but it would enable you to find who's responsible for it.&lt;/p&gt;
&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=6955294" width="1" height="1"&gt;</description></item><item><title>re: How to manipulate files inside Inetpub/wwwroot all day without being bugged by UAC</title><link>http://weblogs.asp.net/bleroy/archive/2007/03/14/how-to-manipulate-files-inside-inetpub-wwwroot-all-day-without-being-bugged-by-uac.aspx#6953442</link><pubDate>Wed, 11 Mar 2009 08:26:56 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:6953442</guid><dc:creator>victor</dc:creator><author>victor</author><description>&lt;p&gt;I am an IT auditor. I find that there were developers who had modify rights on inetpub directory in the production environment. How risky or dangerous it is? please help&lt;/p&gt;
&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=6953442" width="1" height="1"&gt;</description></item><item><title>re: How to manipulate files inside Inetpub/wwwroot all day without being bugged by UAC</title><link>http://weblogs.asp.net/bleroy/archive/2007/03/14/how-to-manipulate-files-inside-inetpub-wwwroot-all-day-without-being-bugged-by-uac.aspx#2030539</link><pubDate>Thu, 15 Mar 2007 07:38:32 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:2030539</guid><dc:creator>Bertrand Le Roy</dc:creator><author>Bertrand Le Roy</author><description>&lt;p&gt;Dean: you're absolutely right, so for a dev machine, the inetpub folder may be dependable and just giving access may be acceptable but on a production server, well, in this case just leave everything on I suppose.&lt;/p&gt;
&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=2030539" width="1" height="1"&gt;</description></item><item><title>re: How to manipulate files inside Inetpub/wwwroot all day without being bugged by UAC</title><link>http://weblogs.asp.net/bleroy/archive/2007/03/14/how-to-manipulate-files-inside-inetpub-wwwroot-all-day-without-being-bugged-by-uac.aspx#2030373</link><pubDate>Thu, 15 Mar 2007 05:49:49 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:2030373</guid><dc:creator>Speednet</dc:creator><author>Speednet</author><description>&lt;p&gt;rbuckton, your comments are right on target!&lt;/p&gt;
&lt;p&gt;I have been thinking exactly the same thing. &amp;nbsp;What malware is going to try and run the VS2005 IDE?&lt;/p&gt;
&lt;p&gt;UAC desperately needs fine-tuning controls, which an advanced user can manipulate. &amp;nbsp;It can be changed to work exactly like a learning firewall, giving the user the ability to remember a rule or ask every time. &amp;nbsp;Wouldn't that be the best approach?&lt;/p&gt;&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=2030373" width="1" height="1"&gt;</description></item><item><title>re: How to manipulate files inside Inetpub/wwwroot all day without being bugged by UAC</title><link>http://weblogs.asp.net/bleroy/archive/2007/03/14/how-to-manipulate-files-inside-inetpub-wwwroot-all-day-without-being-bugged-by-uac.aspx#2029812</link><pubDate>Thu, 15 Mar 2007 03:13:07 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:2029812</guid><dc:creator>Dean Harding</dc:creator><author>Dean Harding</author><description>&lt;p&gt;&amp;gt; Yes, you're absolutely right, but giving rights on the folder presents the&lt;/p&gt;
&lt;p&gt;&amp;gt; same risks as far as shell extensions are concerned.&lt;/p&gt;
&lt;p&gt;Except that they WOULDN'T have those rights on every OTHER folder marked Admin-only (System32, Program Files, etc).&lt;/p&gt;
&lt;p&gt;I guess it depends on how &amp;quot;valuable&amp;quot; your InetPub folder is compared to those other folders. Either way, I think there are risks doing it both ways... but that's the nature of security; you've got to take risks in the interest of actually being able to DO stuff :)&lt;/p&gt;&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=2029812" width="1" height="1"&gt;</description></item><item><title>re: How to manipulate files inside Inetpub/wwwroot all day without being bugged by UAC</title><link>http://weblogs.asp.net/bleroy/archive/2007/03/14/how-to-manipulate-files-inside-inetpub-wwwroot-all-day-without-being-bugged-by-uac.aspx#2029235</link><pubDate>Thu, 15 Mar 2007 02:08:45 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:2029235</guid><dc:creator>David Taylor</dc:creator><author>David Taylor</author><description>&lt;p&gt;Bertrand, like you I have left UAC enabled for the last few months of running Vista.&lt;/p&gt;
&lt;p&gt;However I am not that worried if many technical people turn it off as they know how to fix their machine if it gets trashed. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;What I care about is that my mother, father and other non-technical people leave it on. &amp;nbsp;We should remember that 95% of people are not very technical, and if that 95% have UAC enabled Vista is a huge win.&lt;/p&gt;&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=2029235" width="1" height="1"&gt;</description></item><item><title>re: How to manipulate files inside Inetpub/wwwroot all day without being bugged by UAC</title><link>http://weblogs.asp.net/bleroy/archive/2007/03/14/how-to-manipulate-files-inside-inetpub-wwwroot-all-day-without-being-bugged-by-uac.aspx#2029194</link><pubDate>Thu, 15 Mar 2007 02:03:11 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:2029194</guid><dc:creator>rbuckton</dc:creator><author>rbuckton</author><description>&lt;p&gt;There are times where I wish there was a way to &amp;quot;pre-authorize&amp;quot; certain applications for UAC. &amp;nbsp;I always run Visual Studio elevated and the prompt seems a bit cumbersome in those cases. &amp;nbsp;I think you should be able to authorize certain applications as approved without the need to accept a UAC prompt. &amp;nbsp;You could define the trusted startup parameters for the application (e.g. what are the valid commad line options that can be supplied). &amp;nbsp;Pre-authorized applications would then just need some type of bubble tip after launch that appears above the icon in the taskbar, or differentiate the window with slightly different window chrome (say a red or orangeish cast to the aero glass style) for applications running elevated.&lt;/p&gt;
&lt;p&gt;Beyond that I am a big fan of UAC. Vista makes large-scale operations affecting a protected folder efficient by determining up front everything that will need elevation when beginning a copy, move, delete, etc. operation. &amp;nbsp;It's the one-by-one changes that become cumbersome. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;One of the more difficult to understand features of UAC is attempting to write a file to a protected location by an application that doesnt understand UAC. &amp;nbsp;Instead of denying the operation, a special folder structure under your profile folders that matches the protected directory structure is created for those files. &amp;nbsp;Vista needs a way to track and merge these changes easily after the fact, rather than having to do it manually.&lt;/p&gt;&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=2029194" width="1" height="1"&gt;</description></item><item><title>re: How to manipulate files inside Inetpub/wwwroot all day without being bugged by UAC</title><link>http://weblogs.asp.net/bleroy/archive/2007/03/14/how-to-manipulate-files-inside-inetpub-wwwroot-all-day-without-being-bugged-by-uac.aspx#2029056</link><pubDate>Thu, 15 Mar 2007 01:34:46 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:2029056</guid><dc:creator>Bertrand Le Roy</dc:creator><author>Bertrand Le Roy</author><description>&lt;p&gt;Yes, you're absolutely right, but giving rights on the folder presents the same risks as far as shell extensions are concerned.&lt;/p&gt;
&lt;p&gt;If you have shell extensions that you're unsure about, I guess it's just better to leave UAC on, not give additional permissions and not run as admin...&lt;/p&gt;
&lt;p&gt;Ultimately, I see people disabling UAC as a whole and while it would be best to leave it on and bear with the alerts, such tricks can help in that it's better to have it partially on (and know the risks) than have it completely off.&lt;/p&gt;
&lt;p&gt;As always, the best protection is skeptical computing.&lt;/p&gt;
&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=2029056" width="1" height="1"&gt;</description></item><item><title>re: How to manipulate files inside Inetpub/wwwroot all day without being bugged by UAC</title><link>http://weblogs.asp.net/bleroy/archive/2007/03/14/how-to-manipulate-files-inside-inetpub-wwwroot-all-day-without-being-bugged-by-uac.aspx#2029015</link><pubDate>Thu, 15 Mar 2007 01:24:28 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:2029015</guid><dc:creator>Dean Harding</dc:creator><author>Dean Harding</author><description>&lt;p&gt;Yes, but running explorer as an administrator also means all your explorer extensions and so on are running as administrator.&lt;/p&gt;
&lt;p&gt;I guess it just depends on where you think the threats are coming from :-)&lt;/p&gt;&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=2029015" width="1" height="1"&gt;</description></item></channel></rss>