IE 7 and .NET Framework 1.1 Setting Trust for the intranet

[Anonymous]

While upgrading to IE 7, I found that my .NET applications that I run off of
my company Intranet file servers have stopped working and the only way to
get them working again is to trust the application as oppose to the source.
I used to use the .NET Wizard and adjust the .NET Security for the local
intranet to full trust and add the dns location to the list of intranet
sites in IE. But now that will not work. I do not want to have to retrust
an application every time I update it or add a new application. Does anyone
have a work around or ideas?

Thanks,
Bill

[Anonymous]

Giving Full Trust to local intranet is, IMO, a bit too loose on the
security. If I want to make some .NET code available to all computers in our
local network without installing on each computer, I place the code in a
network share, to which users have read and execute but not write
permissions, and create a code group pointing to that network folder with
full trust. This way, no user but myself can drop executable code into that
folder and all .NET code in that folder is guaranteed to run security-wise.
With this sutup, the computers with IE7 installed in our office do not have
the security issue as you described.

"Bill S" wrote in message
news:[email protected]...
While upgrading to IE 7, I found that my .NET applications that I run off of
my company Intranet file servers have stopped working and the only way to
get them working again is to trust the application as oppose to the source.
I used to use the .NET Wizard and adjust the .NET Security for the local
intranet to full trust and add the dns location to the list of intranet
sites in IE. But now that will not work. I do not want to have to retrust
an application every time I update it or add a new application. Does anyone
have a work around or ideas?

Thanks,
Bill

[Anonymous]

Norman,

Does your users connect to those local network share through their NetBios
names or DNS names or DNS Aliases? I am using a DNS alias, I did not seem
to have this problem using netbios names. How did you go about creating
your code group. Is it an active directory group?

Thanks,
Bill

"Norman Yuan" wrote in message
news:[email protected]...
Giving Full Trust to local intranet is, IMO, a bit too loose on the
security. If I want to make some .NET code available to all computers in our
local network without installing on each computer, I place the code in a
network share, to which users have read and execute but not write
permissions, and create a code group pointing to that network folder with
full trust. This way, no user but myself can drop executable code into that
folder and all .NET code in that folder is guaranteed to run security-wise.
With this sutup, the computers with IE7 installed in our office do not have
the security issue as you described.

"Bill S" wrote in message
news:[email protected]...
While upgrading to IE 7, I found that my .NET applications that I run off of
my company Intranet file servers have stopped working and the only way to
get them working again is to trust the application as oppose to the source.
I used to use the .NET Wizard and adjust the .NET Security for the local
intranet to full trust and add the dns location to the list of intranet
sites in IE. But now that will not work. I do not want to have to retrust
an application every time I update it or add a new application. Does anyone
have a work around or ideas?

Thanks,
Bill

[Anonymous]

It does not matters what network library/protocol is. Just create a code
group with its URL pointing to a network file share. See detail of my reply
to another post this morning with subject "Deployment of dll (framework
version 2.0)".


"Bill S" wrote in message
news:[email protected]...
Norman,

Does your users connect to those local network share through their NetBios
names or DNS names or DNS Aliases? I am using a DNS alias, I did not seem
to have this problem using netbios names. How did you go about creating
your code group. Is it an active directory group?

Thanks,
Bill

"Norman Yuan" wrote in message
news:[email protected]...
Giving Full Trust to local intranet is, IMO, a bit too loose on the
security. If I want to make some .NET code available to all computers in our
local network without installing on each computer, I place the code in a
network share, to which users have read and execute but not write
permissions, and create a code group pointing to that network folder with
full trust. This way, no user but myself can drop executable code into that
folder and all .NET code in that folder is guaranteed to run security-wise.
With this sutup, the computers with IE7 installed in our office do not have
the security issue as you described.

"Bill S" wrote in message
news:[email protected]...
While upgrading to IE 7, I found that my .NET applications that I run off of
my company Intranet file servers have stopped working and the only way to
get them working again is to trust the application as oppose to the source.
I used to use the .NET Wizard and adjust the .NET Security for the local
intranet to full trust and add the dns location to the list of intranet
sites in IE. But now that will not work. I do not want to have to retrust
an application every time I update it or add a new application. Does anyone
have a work around or ideas?

Thanks,
Bill