X
Tap here to go to the mobile version of the site.

Support Forum

Prevent Accessing C Drive

Posted

I wish to install Mozilla Firefox version 22.0 in my lab computer for student use. However, I have ran into a Security Issue with this browser. When you type "C:" in the search bar, Firefox will display the contents of the C Drive. IE and Chrome do not. I have spent the last 3 days researching this issue without finding a fix that would work. I have tried use the add-on BlockSite, installing a third-party .adm (although the documentation did not point to what specific policies to edit), and modifying the browser.js file. (as described here: http://nitishkumar.net/2010/06/23/restricting-browsing-with-mozilla-firefox-for-business-scenario/) Is there any way to prevent Firefox from displaying this?

Just to note: I have already configured Active Directory Group Policies to hide the C Drive and prevent the user from searching the C drive through Windows Explorer, IE, and Google Chrome.

I wish to install Mozilla Firefox version 22.0 in my lab computer for student use. However, I have ran into a Security Issue with this browser. When you type "C:" in the search bar, Firefox will display the contents of the C Drive. IE and Chrome do not. I have spent the last 3 days researching this issue without finding a fix that would work. I have tried use the add-on BlockSite, installing a third-party .adm (although the documentation did not point to what specific policies to edit), and modifying the browser.js file. (as described here: http://nitishkumar.net/2010/06/23/restricting-browsing-with-mozilla-firefox-for-business-scenario/) Is there any way to prevent Firefox from displaying this? Just to note: I have already configured Active Directory Group Policies to hide the C Drive and prevent the user from searching the C drive through Windows Explorer, IE, and Google Chrome.

Chosen solution

Never mind. I figured out the issue I was having. The placement of the new code was incorrect on the site:

http://nitishkumar.net/2010/06/23/restricting-browsing-with-mozilla-firefox-for-business-scenario/

The proper location of the added code was at the end of the "Show or hide browser chrome based on the whitelist" section in the OnLocationChanged function at line 11264. Once I moved following code to this location it worked:

if (location.match(/^file:/)|| location.match(/^\//)|| location.match(/^resource:/)|| location.match(/^c:/)|| (!location.match(/^about:blank/) && location.match(/^about:/))) { loadURI("about:blank"); }

However, I did need to manually remove and recreate all user accounts on the system before this change would replicate to them. In other words, this change did not fix the issue for all the accounts on the computer, but new accounts added after the fix would receive the fix.

Read this answer in context 0

Chosen Solution

Never mind. I figured out the issue I was having. The placement of the new code was incorrect on the site:

http://nitishkumar.net/2010/06/23/restricting-browsing-with-mozilla-firefox-for-business-scenario/

The proper location of the added code was at the end of the "Show or hide browser chrome based on the whitelist" section in the OnLocationChanged function at line 11264. Once I moved following code to this location it worked:

if (location.match(/^file:/)|| location.match(/^\//)|| location.match(/^resource:/)|| location.match(/^c:/)|| (!location.match(/^about:blank/) && location.match(/^about:/))) { loadURI("about:blank"); }

However, I did need to manually remove and recreate all user accounts on the system before this change would replicate to them. In other words, this change did not fix the issue for all the accounts on the computer, but new accounts added after the fix would receive the fix.

Never mind. I figured out the issue I was having. The placement of the new code was incorrect on the site: http://nitishkumar.net/2010/06/23/restricting-browsing-with-mozilla-firefox-for-business-scenario/ The proper location of the added code was at the end of the "Show or hide browser chrome based on the whitelist" section in the OnLocationChanged function at line 11264. Once I moved following code to this location it worked: if (location.match(/^file:/)|| location.match(/^\//)|| location.match(/^resource:/)|| location.match(/^c:/)|| (!location.match(/^about:blank/) && location.match(/^about:/))) { loadURI("about:blank"); } However, I did need to manually remove and recreate all user accounts on the system before this change would replicate to them. In other words, this change did not fix the issue for all the accounts on the computer, but new accounts added after the fix would receive the fix.
FireAtWill 0 solutions 1 answers

zombie,

Thanks heaps for this, I am trying to do the same thing.

Excuse my nub-ness, but where can I find the "browser.js" file in version 22, please?

zombie, Thanks heaps for this, I am trying to do the same thing. Excuse my nub-ness, but where can I find the "browser.js" file in version 22, please?