Request for the permission of type 'System.Net.WebPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.
164 views
Skip to first unread message
Darian
Nov 9, 2009, 11:48:25 PM11/9/09
to ASProxy
My hosting provider recently made a change that broke ASProxy. Below
is a message the hosting provider sent out before the change that
warned of applications breaking with the change. It would be
appreciated if ASProxy can be configured to run in such a secured
environment.
Urgent Maintenance Notice
------------------
When: 11/4 at 12 AM Midnight
What: Platform Security Changes
Impact:10 minute service interruption. Possible extended downtime for
some customers.
Details:
On November 4th, we will be changing your web server to run ASP .Net
in a medium trust environment which will cause extended downtime for
some customers. This is an important security change necessary to
protect your server and data and is the Microsoft recommended trust
level for Shared .net hosting. Using medium trust will prevent
applications from accessing shared resources and eliminates any
application interference. A small percentage of websites will NOT be
operational after this security change although a majority of websites
will not be affected or can be adjusted. In order to ensure that your
application has a smooth transition when we make this change, we
encourage you to review your application as soon as possible to ensure
that it is compatible with Medium Trust standards. Websites that are
not compatible with medium trust may be completely non-operational or
show significant errors.
Note: THIS CHANGE DOES NOT AFFECT COLDFUSION CODE.
Please review the information below about this change and how it may
apply to your application. If you are unsure of how this change
applies to you, please contact your developer to review, or contact
Hosting.com support for migration options. In many cases, Hosting.com
support can make specific security exceptions ahead of time so that
you do not experience any downtime.
Permcalc.exe
Permcalc.exe can be downloaded as part of the .net 2.0 SDK and used to
determine what trust level your application currently requires.
Manual: http://msdn.microsoft.com/en-us/library/ms165077(VS.80).aspx
.net 2.0 SDK
http://www.microsoft.com/downloads/details.aspx?FamilyID=fe6f2099-b7b4-4f47-a244-c96d69c35dec&displaylang=en
Please see the below Microsoft article for more information on these
changes.
http://msdn.microsoft.com/en-us/library/ms998341.aspx
We will be enabling OleDb, ODBC, and MySQL connections as well as SQL
Native Client connections by default.
Applications with known issues:
DotNetNuke:
In order to allow DotNetNuke to function in medium trust, a minor
change is necessary in your web.config file.
Change this: <trust level="Full" originUrl="http://some_site_or_ip/.*"/
>
To this: <!-- <trust level="Full" originUrl="http://
some_site_or_ip/.*"/> -->
ASP .net Storefront
ASP .net storefront users will need to upgrade to at least version
7.0.2.5 SP1 or move to a VPS or dedicated solution once Medium Trust
is implemented. See https://support.aspdotnetstorefront.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=208
for more details.
ASPcompat=true
Unfortunately this option requires high trust to function. If you
application requires this functionality you will need to move to a VPS
or dedicated solution. Some applications are coded with this
functionality enabled but do not actually require it. Please consult
with a support representative for more information.
See this article for more information on the aspcompat tag:
http://msdn.microsoft.com/en-us/library/zwk9h2kb.aspx
“Strong Named” DLLs
Some 3rd party applications provide component DLLs that are “strong
named” or use unmanaged code and will need to go through an approval
process in order to be used in our medium trust environment. If you
have any concerns about an application of this nature, please contact
our support as soon as possible so that we can address your concerns
as soon as possible.
Payment Gateways
Most payment gateways require DLLs to be approved and additional
permissions added for their API's. Please let us know if you are using
a payment gateway as soon as possible so that we can make the
neccessary configuration changes ahead of time. This will help to
minimize any impact to your site. Also, please note that the .net API
for Linkpoint does not function in a medium trust environment. In
order to use the Linkpoint api in our shared environment you will need
to use the Perl or CF based versions. Alternatively this can be
supported in our .net Professional and VPS environments.
Another change we are making to your server is the installation
of .Net 3.5 Service Pack 1. This is a set of bug fixes and security
patches released by Microsoft that will make the .Net platform run
more reliably and securely. This should have minimal impact on pre-
existing code, but if you have any third party software running on
your site, you may want to verify with them that no updates are needed
to run properly under SP1. For more information, see the following
information at Microsoft:
.Net 3.5 SP1 Overview:
http://www.microsoft.com/downloads/details.aspx?familyid=AB99342F-5D1A-413D-8319-81DA479AB0D7&displaylang=en
.NET 3.5 SP1 List of Changes:
http://msdn.microsoft.com/en-us/library/dd310284.aspx
.NET 3.5 SP1 Readme:
http://download.microsoft.com/download/A/2/8/A2807F78-C861-4B66-9B31-9205C3F22252/dotNet35SP1Readme.htm
Please contact our support as soon as possible with any questions or
concerns you might have regarding this upcoming change.
Thank you,
Hosting Support Team
is a message the hosting provider sent out before the change that
warned of applications breaking with the change. It would be
appreciated if ASProxy can be configured to run in such a secured
environment.
Urgent Maintenance Notice
------------------
When: 11/4 at 12 AM Midnight
What: Platform Security Changes
Impact:10 minute service interruption. Possible extended downtime for
some customers.
Details:
On November 4th, we will be changing your web server to run ASP .Net
in a medium trust environment which will cause extended downtime for
some customers. This is an important security change necessary to
protect your server and data and is the Microsoft recommended trust
level for Shared .net hosting. Using medium trust will prevent
applications from accessing shared resources and eliminates any
application interference. A small percentage of websites will NOT be
operational after this security change although a majority of websites
will not be affected or can be adjusted. In order to ensure that your
application has a smooth transition when we make this change, we
encourage you to review your application as soon as possible to ensure
that it is compatible with Medium Trust standards. Websites that are
not compatible with medium trust may be completely non-operational or
show significant errors.
Note: THIS CHANGE DOES NOT AFFECT COLDFUSION CODE.
Please review the information below about this change and how it may
apply to your application. If you are unsure of how this change
applies to you, please contact your developer to review, or contact
Hosting.com support for migration options. In many cases, Hosting.com
support can make specific security exceptions ahead of time so that
you do not experience any downtime.
Permcalc.exe
Permcalc.exe can be downloaded as part of the .net 2.0 SDK and used to
determine what trust level your application currently requires.
Manual: http://msdn.microsoft.com/en-us/library/ms165077(VS.80).aspx
.net 2.0 SDK
http://www.microsoft.com/downloads/details.aspx?FamilyID=fe6f2099-b7b4-4f47-a244-c96d69c35dec&displaylang=en
Please see the below Microsoft article for more information on these
changes.
http://msdn.microsoft.com/en-us/library/ms998341.aspx
We will be enabling OleDb, ODBC, and MySQL connections as well as SQL
Native Client connections by default.
Applications with known issues:
DotNetNuke:
In order to allow DotNetNuke to function in medium trust, a minor
change is necessary in your web.config file.
Change this: <trust level="Full" originUrl="http://some_site_or_ip/.*"/
>
To this: <!-- <trust level="Full" originUrl="http://
some_site_or_ip/.*"/> -->
ASP .net Storefront
ASP .net storefront users will need to upgrade to at least version
7.0.2.5 SP1 or move to a VPS or dedicated solution once Medium Trust
is implemented. See https://support.aspdotnetstorefront.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=208
for more details.
ASPcompat=true
Unfortunately this option requires high trust to function. If you
application requires this functionality you will need to move to a VPS
or dedicated solution. Some applications are coded with this
functionality enabled but do not actually require it. Please consult
with a support representative for more information.
See this article for more information on the aspcompat tag:
http://msdn.microsoft.com/en-us/library/zwk9h2kb.aspx
“Strong Named” DLLs
Some 3rd party applications provide component DLLs that are “strong
named” or use unmanaged code and will need to go through an approval
process in order to be used in our medium trust environment. If you
have any concerns about an application of this nature, please contact
our support as soon as possible so that we can address your concerns
as soon as possible.
Payment Gateways
Most payment gateways require DLLs to be approved and additional
permissions added for their API's. Please let us know if you are using
a payment gateway as soon as possible so that we can make the
neccessary configuration changes ahead of time. This will help to
minimize any impact to your site. Also, please note that the .net API
for Linkpoint does not function in a medium trust environment. In
order to use the Linkpoint api in our shared environment you will need
to use the Perl or CF based versions. Alternatively this can be
supported in our .net Professional and VPS environments.
Another change we are making to your server is the installation
of .Net 3.5 Service Pack 1. This is a set of bug fixes and security
patches released by Microsoft that will make the .Net platform run
more reliably and securely. This should have minimal impact on pre-
existing code, but if you have any third party software running on
your site, you may want to verify with them that no updates are needed
to run properly under SP1. For more information, see the following
information at Microsoft:
.Net 3.5 SP1 Overview:
http://www.microsoft.com/downloads/details.aspx?familyid=AB99342F-5D1A-413D-8319-81DA479AB0D7&displaylang=en
.NET 3.5 SP1 List of Changes:
http://msdn.microsoft.com/en-us/library/dd310284.aspx
.NET 3.5 SP1 Readme:
http://download.microsoft.com/download/A/2/8/A2807F78-C861-4B66-9B31-9205C3F22252/dotNet35SP1Readme.htm
Please contact our support as soon as possible with any questions or
concerns you might have regarding this upcoming change.
Thank you,
Hosting Support Team
SalarSoft
Nov 12, 2009, 9:28:40 AM11/12/09
to ASProxy
There is way to get an ASP.NET application to work in medium or
minimal trust environment. But it requires to specify what website the
application is trying to connect to. This means you will have access
to limit number of websites and because it is against what ASProxy
philosophy is, it won't be implemented in ASProxy.
You can read this article to see how to change the web.config file to
make asproxy to work with certain sites.
http://www.codeguru.com/cpp/sample_chapter/article.php/c12477/
> .net 2.0 SDKhttp://www.microsoft.com/downloads/details.aspx?FamilyID=fe6f2099-b7b...
> .Net 3.5 SP1 Overview:http://www.microsoft.com/downloads/details.aspx?familyid=AB99342F-5D1...
> .NET 3.5 SP1 Readme:http://download.microsoft.com/download/A/2/8/A2807F78-C861-4B66-9B31-...
minimal trust environment. But it requires to specify what website the
application is trying to connect to. This means you will have access
to limit number of websites and because it is against what ASProxy
philosophy is, it won't be implemented in ASProxy.
You can read this article to see how to change the web.config file to
make asproxy to work with certain sites.
http://www.codeguru.com/cpp/sample_chapter/article.php/c12477/
>
> Please see the below Microsoft article for more information on these
> changes.http://msdn.microsoft.com/en-us/library/ms998341.aspx
> Please see the below Microsoft article for more information on these
>
> We will be enabling OleDb, ODBC, and MySQL connections as well as SQL
> Native Client connections by default.
>
> Applications with known issues:
> DotNetNuke:
> In order to allow DotNetNuke to function in medium trust, a minor
> change is necessary in your web.config file.
> Change this: <trust level="Full" originUrl="http://some_site_or_ip/.*"/
>
>
>
> To this: <!-- <trust level="Full" originUrl="http://
> some_site_or_ip/.*"/> -->
>
> ASP .net Storefront
> ASP .net storefront users will need to upgrade to at least version
> 7.0.2.5 SP1 or move to a VPS or dedicated solution once Medium Trust
> is implemented. Seehttps://support.aspdotnetstorefront.com/index.php?_m=knowledgebase&_a...
> We will be enabling OleDb, ODBC, and MySQL connections as well as SQL
> Native Client connections by default.
>
> Applications with known issues:
> DotNetNuke:
> In order to allow DotNetNuke to function in medium trust, a minor
> change is necessary in your web.config file.
> Change this: <trust level="Full" originUrl="http://some_site_or_ip/.*"/
>
>
>
> To this: <!-- <trust level="Full" originUrl="http://
> some_site_or_ip/.*"/> -->
>
> ASP .net Storefront
> ASP .net storefront users will need to upgrade to at least version
> 7.0.2.5 SP1 or move to a VPS or dedicated solution once Medium Trust
> .NET 3.5 SP1 Readme:http://download.microsoft.com/download/A/2/8/A2807F78-C861-4B66-9B31-...
Darian
Nov 12, 2009, 5:24:59 PM11/12/09
to ASProxy
I'm not an ASP developer. From what I understood of the article I
would specify a trust in the web.config file like so:
<system.net>
<settings>
<trust level="Medium" originUrl="http://www.microsoft.com/"/>
<httpWebRequest useUnsafeHeaderParsing="true"/>
</settings>
</system.net>
I've done the above and I still get the error (when accessing
http://www.microsoft.com/).
Have I done it wrong, or will I need to modify the application code?
would specify a trust in the web.config file like so:
<system.net>
<settings>
<trust level="Medium" originUrl="http://www.microsoft.com/"/>
<httpWebRequest useUnsafeHeaderParsing="true"/>
</settings>
</system.net>
I've done the above and I still get the error (when accessing
http://www.microsoft.com/).
Have I done it wrong, or will I need to modify the application code?
Reply all
Reply to author
Forward
0 new messages