Are there any security issues leaving the PDB debug files on the live servers?
Are there any security issues keeping the .NET PDB files on the real server?
Are there any security issues keeping the .NET PDB files on the real server?
I have a webpage which checks for an encrypted cookie on page load to determine user identity. However, when I’m testing the page locally on my development box, I don’t have access to that cookie.
I’ve tried looking at the Microsoft site and Googling this but nobody seems to have an answer aside from the < and the >. There’s more to it than that though. I’ve noticed that the HTML entity starter of &# is invalid. Is there anything else? Does anyone have a complete list?
I’m trying to sanitize any data that’s inputted by making sure the data is valid for a particular field (e.g. a name can’t contain special characters/numbers etc..) However, I’m not sure what to do when it comes to a password field. Would I even need to bother with any sanitization as the password is simply hashed? If the user was to inject anything malicious via the password textbox, should I bother checking for anything suspicious? AFAIK, some users may (should!) have special characters such as ‘< >’, which would normally trigger a potential attack alert. Should I just leave the password field unsanitized? Limiting input for passwords is a last resort for me, as I feel users should use all sorts of characters in their passwords.
Host: GoDaddy Shared Hosting
Is it possible to restart server from ASP.NET application that is hosted by LocalSystem or LocalService account? This is working when I create custom administrative account and put AppPool to run under that account:
We have a swf file that we want to secure and make available only to authorized users.
This is a corporate site so Private. We want to limit access by IP address to USA/Canada or North America. Based on IP range, would allow user/pwd to get in otherwise -‘no access’. Just trying to limit hack exposure from anything overseas.
I am currently developing an MVC application in ASP.net. I am using AJAX.ActionLink to provide a delete link in a list of records, however this is very insecure. I have put this:
Of course cookies can be stolen and sessions hijacked, but how secure is the encryption itself of the session cookies (in ASP.NET Identity)? Could it be manipulated with modern hardware and a little bit of time?