<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sqlblog.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>On the Topic of Lost SA Passwords on SQL Server 2000…</title><link>http://sqlblog.com/blogs/argenis_fernandez/archive/2012/01/20/on-the-topic-of-lost-sa-passwords-on-sql-server-2000.aspx</link><description>&amp;#160; Since it looks like everything I blog about lately is showing how to get onto SQL instances to which you don’t have formal credentials, I figured what the heck – let’s do a post on SQL 2000. Earlier on today Saurabh Sapra [ twitter ] sent a tweet</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>re: On the Topic of Lost SA Passwords on SQL Server 2000…</title><link>http://sqlblog.com/blogs/argenis_fernandez/archive/2012/01/20/on-the-topic-of-lost-sa-passwords-on-sql-server-2000.aspx#41213</link><pubDate>Sat, 21 Jan 2012 19:18:15 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:41213</guid><dc:creator>John</dc:creator><description>&lt;p&gt;Is there a way of doing something similar for newer versions of SQL Server? There are plenty of posts explaining how to reset it to something you know or gain access to an instance you are locked out of, but nothing explaining how to tell you what it is.&lt;/p&gt;</description></item><item><title>re: On the Topic of Lost SA Passwords on SQL Server 2000…</title><link>http://sqlblog.com/blogs/argenis_fernandez/archive/2012/01/20/on-the-topic-of-lost-sa-passwords-on-sql-server-2000.aspx#41219</link><pubDate>Sun, 22 Jan 2012 09:26:28 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:41219</guid><dc:creator>Argenis</dc:creator><description>&lt;p&gt;@John no, I'm not aware of any means to do that. The SA password is kept in encrypted blobs in newer versions, in a way that I am not familiar with.&lt;/p&gt;
&lt;p&gt;You can definitely capture the password from memory if it has been reset very recently though. But it's very short lived.&lt;/p&gt;
</description></item><item><title>re: On the Topic of Lost SA Passwords on SQL Server 2000…</title><link>http://sqlblog.com/blogs/argenis_fernandez/archive/2012/01/20/on-the-topic-of-lost-sa-passwords-on-sql-server-2000.aspx#41748</link><pubDate>Wed, 15 Feb 2012 02:45:39 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:41748</guid><dc:creator>K. Brian Kelley</dc:creator><description>&lt;p&gt;@John, for 2005+, in memory or by brute force. You can export it, but I've not seen anyone figure out any weaknesses in the hash like with 2000 (where an all uppercase version of the password was hashed and included, thereby reducing the # of possibilities per slot and making brute forcing quicker). The reason this is important is that, unlike Windows, the SQL Server based logins contain a salt, thereby eliminating rainbow tables. &lt;/p&gt;
&lt;p&gt;2000 (and 7) is also susceptible to intercept across the network by looking at a packet trace if the sa account is used and the connection isn't encrypted. &lt;/p&gt;</description></item></channel></rss>