|
|
Rank: Newbie
Groups: Member
Joined: 4/13/2016
Posts: 4
|
We are on 6.0.32.3 of EO web controls. It looks like we are getting errors when enabling the FIPS algorithm mandated by the government. Do we need to upgrade to a newer version of is EO web not FIPS compliant? Quote:Line 194: protected void Application_Start(Object sender, EventArgs e)
Line 195: {
Line 196: EO.Web.Runtime.AddLicense(
Line 197: "GrbB27dprrbC7NOMy8XX8bto4+30EO2s3M316YxDl6Sxy7ul4Of2GfKe3MLd" +
Line 198: "DPSr2KTUDOWf6ekKy591pvD6DuSn6un26YxDl6Sxy7ua4/AAIr1GgaSxy59Z" + Quote:[Exception: License data provided by AddLicense is invalid.]
EO.Web.Internal.ev.d(String A_0) +404
EO.Web.Runtime.AddLicense(String license) +21
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
You have an extremely old version (about 8 years old). That version was not FIPS compliant. This issue was resolved years ago and the current version is FIPS compliant. So if it is acceptable to you, you can purchase a new license for the current version and it should work for you.
FPIS compliant is just one of the many issues resolved by the current version. The most important benefits of the current version is newer browser support. Browsers update very quickly these days and some of the popular browser today such as Google Chrome didn't even exist back then, others have made radical changes, such as the case of IE 11. The new version is throughly tested on them so it works much better on these browsers.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 4/13/2016
Posts: 4
|
Thanks for the quick response. Do you know if we upgraded to the new version if there is anything that is not compatible anymore from what we may have been using in our old version? Trying to gauge if this would be a seamless upgrade or not.
Thanks
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
I am not aware of any significant change between the current version and your version. The architecture of EO.Web has stayed the same during the years and almost all changes are incremental. So I think the upgrade is pretty much just a drop in and rebuild upgrade. You can try to download the new version from our download page and run it without a license key. If you run into any problems please let us know and we will be happy to help you further.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 4/13/2016
Posts: 4
|
I downloaded the new EOWeb.dll and replaced in my project reference. Is there another dll i need to reference in the new version?
Could not load file or assembly 'EO.Web' or one of its dependencies. Strong name signature could not be verified. The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.IO.FileLoadException: Could not load file or assembly 'EO.Web' or one of its dependencies. Strong name signature could not be verified. The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Assembly Load Trace: The following information can be helpful to determine why the assembly 'EO.Web' could not be loaded.
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
You will also need to reference EO.Base.dll. However you should not get a strong name verification error. What is the DLL version and how did you get the new DLL?
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 4/13/2016
Posts: 4
|
Thank you that fixed my issue. I needed to include the EO.base.dll also in my websites bin directory.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Great! Glad to hear that you got it working. Please feel free to let us know if you run into anything else.
|
|