These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE Technology Lab

 
  • Topic is locked indefinitely.
 

IGB cannot decrypt web.config file
Author
Previous Topic Next Topic
Forgon
TURN LEFT
#1 - 2013-06-23 16:36:55 UTC
Hi,

I am currently playing around with an web app that has a database connection in asp.net. Before I upload the files I encrypted the web.config file using the aspnet_regiis.exe.

The problem is that app works great in IE, chrome and other browsers but it does not work in in game browser (which was my primary concern). I checked with custom error messages off and error seems to be directing at a line in web.config file concerning decrypting of this file. Since I cannot reproduce the error on any other browser I cant find a proper solution.

The app works in IGB if I dont encrypt the web.config but then it wont be secure enough.

Any help would be appreciated.
Steve Ronuken
Fuzzwork Enterprises
Vote Steve Ronuken for CSM
#2 - 2013-06-23 17:05:33 UTC
Uh, if the client needs to be able to decrypt it, you're passing along the key. Which means, for all intents and purposes, it's not encrypted.

Now, I don't use asp.net, but considering the database connections are going to be entirely server side, why does the file even need to be available to the client?

Woo! CSM XI!

Fuzzwork Enterprises

Twitter: @fuzzysteve on Twitter
Forgon
TURN LEFT
#3 - 2013-06-23 17:22:15 UTC
I am fairly new to the web development really, I mostly did desktop stuff.

I dont think web.config file can be accessed by the client directly but in order for the app to work you need to include it during deployment.

As far I understand browser has nothing to do with the decrption process, it is done by the web server. But for some reason IGB throws an error when I try to run the app :(
TheSkeptic
Federal Navy Academy
Gallente Federation
#4 - 2013-06-24 13:00:11 UTC
as you said... web.config should only really be used server side.

Any chance of giving us the actual error message you are seeing?

...