Thread: Latest MS Security Update

Is anyone else having a problem with the security patch from August 10th? I'm referring to a security patch to the .NET 2.0 SP2 and .NET 3.5 SP1.

After applying this patch to my development machine, any user authentication causes a crash in the Security.vb module and I get the following error.

Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

System.TypeInitializationException was unhandled by user code
Message="The type initializer for 'AspDotNetStorefrontEncrypt.Encrypt' threw an exception."
Source="AspDotNetStorefrontEncrypt"
TypeName="AspDotNetStorefrontEncrypt.Encrypt"
StackTrace:
at AspDotNetStorefrontEncrypt.Encrypt.ComputeSaltedHa sh(Int32 Salt, String ClearPassword)
at AspDotNetStorefrontCommon.Password..ctor(String ClearPassword, Int32 Salt) in D:\Source Code\ASPDotNetStorefront\7.0.2.1\ASPDNSFCommon\Sec urity.vb:line 491

I have the source code but not for AspDotNetStorefrontEncrypt as this is a DLL. The only change to the development environment was the security patch.

Anyone????

Did you ever get your site working?

I have a pending MS update on my server and now im fearful of running it!

My dev server is working fine after all patches and is currently up to date. My dev is very 8 however so I am not sure if that comes into play as you are on ver 7.

Plus I am pretty sure our live server had a restart with all the latest updates and that is running fine (touch wood!)

we're running fine also with latest updates

Thanks for chiming in, I feel a little more comfortable now.

I didnt even notice they were on v 7 ... that could possibly be the issue.

Still no luck so far. I've been scouring the MS website to try to see if there's been any other problems reported with this patch. I ran into a similar problem about a year ago with VS2005 and one of the MS updates and wound up having to rebuild the machine. I would rather not have to do that again.

parrothead (LOVE the name by the way )

Since you are running an older version, this article may be of help.


https://support.aspdotnetstorefront....barticleid=208

Sounds like something along the lines of this. Check to see if the update actually installed .NET 3.5, in which case you'll have to remove it.

Keep in mind that you can't just uninstall 3.5, you'll have to remove .NET entirely and then reinstall just 2

.NET 3.5 was installed before (not sure why) and it was working fine. I am attempting to restore .NET 3.5 SP1 to its original state and see if it will play nicely in the sandbox again.

Thanks for the information.