On Jun 14, 2007, at 2:22 PM, Bill Witherspoon wrote:
> When I drop the same user/pass into the connection dialog it doesn't
> work. That's when I noticed that the password is being hashed in the
> .cnxml file.
That 'hashing' is actually a pretty weak obscuring technique. It is
not considered secure, but is simply a placeholder for developers to
add their own security - preferably something not openly published!
Would you try something to see if we can figure this out? Below is
code from dbMsSQL.py. The line numbers are the lines from the current
version of the file; the lines without numbers are the debugging code
I want you to insert.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
24 port = str(connectInfo.Port)
25 if not port or port == "None":
26 port = 1433
27 host = "%s:%s" % (connectInfo.Host, port)
28 user = connectInfo.User
29 password = connectInfo.revealPW()
30 database = connectInfo.Database
31
32 # hack to make this work. I am sure there is a better way.
33 self.database = database
34
print "host:", host
print "user:", user
print "password:", password
print "database:", database
print "kwargs:", kwargs
35 self._connection = pymssql.connect(host=host, user=user,
password=password,
36 database=database, **kwargs)
37 return self._connection
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Now try running the dialog that isn't working, and post what gets
printed out. If that's not the correct connection parameters, then we
can figure out why.
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
