I've just replaced the last dBA and don't know the sa password

I've just replaced the last dBA and don't know the sa password

Post by David Geisbus » Fri, 11 Jul 1997 04:00:00



Does anyone out there know how to get in ?? Is there a backdoor ?

 
 
 

I've just replaced the last dBA and don't know the sa password

Post by Ron Lander » Fri, 11 Jul 1997 04:00:00


David,

If you are running integrated or mixed security mode then any user that is
in the
Windows NT Admin group will be treated as having sa access by SQL Server.

All you need to do then is just login and change the password.

Ron



| Does anyone out there know how to get in ?? Is there a backdoor ?
|

 
 
 

I've just replaced the last dBA and don't know the sa password

Post by Roy Harv » Fri, 11 Jul 1997 04:00:00


David,

Quote:>Does anyone out there know how to get in ?? Is there a backdoor ?

If the server is using standard security, you may find an installation
of SQL Enterprise Manager with the server registered to connect as sa.
It does not ask for the password.

Once you get connected as sa, you can set the password using the
sp_password system stored procedure.

Roy

 
 
 

I've just replaced the last dBA and don't know the sa password

Post by Neil Pik » Fri, 11 Jul 1997 04:00:00


If it's 4.x then you can hex-edit the master.dat.  If it's 6.x then you'd
better hope one of their machines has SQL enterprise manager on with the
password registered in it (so you can logon and then change it)

 Neil Pike MVP/MCSE
 Protech Computing Ltd (MS Solution Provider)
 Using Virtual Access 4.00 build 213a (32-bit) on NT 4.0 SP3

 
 
 

I've just replaced the last dBA and don't know the sa password

Post by Mike Pos » Fri, 11 Jul 1997 04:00:00


Actually, it doesn't matter what security mode SQL Server is running in.
You can force a trusted connection into the server via Standard security
mode as well - as long as you didn't take the extra steps to disable this!



> David,

> If you are running integrated or mixed security mode then any user that
is
> in the
> Windows NT Admin group will be treated as having sa access by SQL Server.

> All you need to do then is just login and change the password.

> Ron



> | Does anyone out there know how to get in ?? Is there a backdoor ?
> |

 
 
 

I've just replaced the last dBA and don't know the sa password

Post by David Bratto » Sat, 12 Jul 1997 04:00:00



> Actually, it doesn't matter what security mode SQL Server is running in.
> You can force a trusted connection into the server via Standard security
> mode as well - as long as you didn't take the extra steps to disable this!



> > David,

> > If you are running integrated or mixed security mode then any user that
> is
> > in the
> > Windows NT Admin group will be treated as having sa access by SQL Server.

> > All you need to do then is just login and change the password.

> > Ron



> > | Does anyone out there know how to get in ?? Is there a backdoor ?
> > |

There is a step by step description of how to break in using this method
starting on page 167 of "SQL Server 6.5 Secrets" from IDG. But a good
DBA will have closed this hole. It's the second thing I do when I
install
a new server.

______________________________________________________________________________
David Bratton
University of Houston System                    THE BILL OF RIGHTS

 
 
 

1. triggers don't get exported, dba jobs don't run

Hi,
we migrated from 8.0.x under Novell Netware to 8.1.7 under Redhat 6.2.

Now we've got two problems:

- database jobs (dba_jobs package) don't run although they should
- when I export the database (either fill database export or all objects of
an specific user) and import the resulting dump into another 8.1.7
database, the triggers get lost

Do you have an idea how to solve this problems ?

Thx

Peter

2. Help! Mainframe <--> PC Data Transfers

3. I've done the 'impossible', but I don't know HOW! :\

4. tbload

5. Don't know the field name but do know the column order

6. users table

7. DBA Studio--Don't need password ?

8. function to count business days?

9. Oninit didn't work fine and I don't know why

10. Funny Behaving Locate - don't know where's the problem

11. Don't know if it's possible : grouping

12. SQL Server 'sa' password

13. MS SQL 6.5 'sa' password lost