|
|
|
[
Permlink
| « Hide
]
Sergey Koshcheyev - 20/Dec/05 03:01 PM
The proposed solution involves avoiding the use of IdentityHashCodeProvider. This might unfortunately lead to subtle bugs at runtime, so I don't want to go that route. If somebody finds an implementation of identity hash map for .NET that is usable under restrictive security settings, please let us know.
The IdentityHashCodeProvider issue is (I believe) solved in 1.2.0.Alpha1 build since that version uses RuntimeHelpers.GetHashCode method instead of a custom IL-based solution.
I'm reopening this issue to track any other changes needed to make NH run under medium trust. I ran FxCop on NHibernate and it didn't report any serious security errors beyond some issues with GetObjectData methods, so I guess I will just add the AllowPartiallyTrustedCallers attribute both to NH and to Iesi.Collections.
Any plans on when this will be incorporated into a release?
The APTCA attribute will be part of Beta1. I don't know how much it will help though so I'm still leaving the issue open.
Verified that NH works under medium trust (example is in SVN). The only significant limitation is that DynamicProxy throws a SecurityException so proxies have to be disabled.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||