Re: Adding parameterized values. Which is more secure.
From: Raterus (moc.liamtoh_at_suretar.reverse)
Date: 09/10/04
- Next message: Paul Glavich [MVP - ASP.NET]: "Re: Web Services Encryption"
- Previous message: Ryan Taylor: "Adding parameterized values. Which is more secure."
- In reply to: Ryan Taylor: "Adding parameterized values. Which is more secure."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 10 Sep 2004 14:17:31 -0400
You would get a better answer on microsoft.public.dotnet.framework.adonet, but I don't think it really matters. Adding the extra values just allows sql server to more efficiently process the parameters, it doesn't do anything more to secure it.
"Ryan Taylor" <rtaylor@stgeorgeconsulting.com> wrote in message news:OEXtPC1lEHA.896@TK2MSFTNGP12.phx.gbl...
> Hello.
>
> Adding some data to a sql server 2000 table. Is the later more secure than
> the former? If so, why?
>
> SqlCommand sqlCmd = new SqlCommand(update, sqlConn);
>
> sqlCmd.Parameters.Add("@hashedPass", user.HashedPassword);
>
>
>
> SqlCommand sqlCmd = new SqlCommand(update, sqlConn);
>
> sqlCmd.Parameters.Add("@hashedPass", SqlDbType.NVarChar, 255).Value =
> user.HashedPassword;
>
>
>
> Thanks in advance.
>
> Ryan Taylor
>
>
- Next message: Paul Glavich [MVP - ASP.NET]: "Re: Web Services Encryption"
- Previous message: Ryan Taylor: "Adding parameterized values. Which is more secure."
- In reply to: Ryan Taylor: "Adding parameterized values. Which is more secure."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
