Re: sqlagentcmdexec
From: BarbS (BarbS_at_discussions.microsoft.com)
Date: 09/22/04
- Next message: Kyle Morris: "Cant create/edit stored procs in VS.Net"
- Previous message: Howard: "Re: URGENT:Cannot force SSL Encryption on from SQL Client"
- In reply to: Mark Allison: "Re: sqlagentcmdexec"
- Next in thread: Mark Allison: "Re: sqlagentcmdexec"
- Reply: Mark Allison: "Re: sqlagentcmdexec"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 22 Sep 2004 09:07:02 -0700
Thank You. My question is, will there be a problem if I change this password.
This seems to be a system assigned password.
"Mark Allison" wrote:
> BarbS,
>
> All passwords should be "strong" to deter brute force cracking. I
> presume you have a brute force cracker? If so, your tool will crack any
> SQL login if the passwords are weak. Your password should be at least 10
> chars long and have a mix of random letters and numbers, so that a
> dictionary attack cannot be done (this is usually the first phase of a
> brute force crack).
>
> This area is being tightened up in SQL 2005.
>
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
>
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
>
> BarbS wrote:
> > I have a software program that crack the password for sqlagentcmdexec. Should
> > the password be changed to make it complex? Thank You.
>
- Next message: Kyle Morris: "Cant create/edit stored procs in VS.Net"
- Previous message: Howard: "Re: URGENT:Cannot force SSL Encryption on from SQL Client"
- In reply to: Mark Allison: "Re: sqlagentcmdexec"
- Next in thread: Mark Allison: "Re: sqlagentcmdexec"
- Reply: Mark Allison: "Re: sqlagentcmdexec"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
