Closed GoogleCodeExporter closed 9 years ago
The steps listed in the origianl report do no reproduce the indicated
exception.
Here's what I tried:
1. Ran demo.cmd in the root of the ELMAH 1.0 distribution.
2. Modified web.config to change the trust level from Full to Medium.
3. Switched from SQLiteErrorLog to XmlFileErrorLog because the former is known
to
require full trust.
3. Deleted Default.aspx because it would cause a security exception in medium
trust
(but for a different reason) since its code tries to directly access sections
of the
configuration file.
4. Pointed the browser to the errors page by navigating to:
http://localhost:54321/elmah.axd
5. Generated a test exception by navigating to: http://localhost:54321/elmah.axd
All of the above steps demonstrated normal and by-design behavior and never
generated
a security exception as being reported in the issue. For reference, the modified
version of the web.config is attached.
It looks like that the shared hosting environment may be using a modified
version of
the default medium trust. As James points out in the following message, medium
trust
does grant read access to the COMPUTERNAME environment variable:
http://groups.google.com/group/elmah/msg/782374e4e6afaeae
> The following line shows that by default the COMPUTERNAME can be read
> through the Environment.MachineName call:
> <IPermission class="EnvironmentPermission" version="1"
> Read="TEMP;TMP;USERNAME;OS;COMPUTERNAME"/>
Original comment by azizatif
on 20 Jul 2009 at 11:09
Attachments:
Original comment by jamesdriscoll71
on 17 Jan 2010 at 11:52
Original comment by jamesdriscoll71
on 18 Jan 2010 at 12:04
Original issue reported on code.google.com by
isaac.n....@gmail.com
on 18 Jul 2009 at 2:08