I'm creating a custom MembershipProvider for an ASP.NET MVC website, and I was planning on using LINQ to SQL for the internals, as I am for the rest of the website. Are there any issues with this, specifically any security issues it causes?
views:
240answers:
3
A:
Are you creating a membership provider and not using the default installation I see no problem.
Paulo Santos
2010-02-24 19:28:14
I'm not sure I understand your answer. The first part seems to be a question, followed immediately by a statement.
C. Ross
2010-02-24 20:00:32
A:
Depending on your implementation there should be no more of a security risk than writing the calls in TSQL or stored procedures.
Burt
2010-02-24 19:28:35
A:
Linq-To-SQL prevents SQL injection attacks; so any potential holes would normally be the result of logical errors created in the customer membership provider.
George Stocker
2010-02-24 20:10:44