"Debugging" a password dialog
Hi everybody, I am trying to get an application to run under Wine that requires a login with a username and a password. The program runs all fine, however I can't login with data that should work (and AFAIK works under Windows). Having entered the password, in the corresponding part of the dialog I only see "*****" (which is correct). However, when I change focus to some other part of that dialog afterwards, the password field shows "*************" (way more asterisks than before). The previous (i.e. correct) length of ****s is restored when setting the focus back onto the password field. I have reason to believe that the password I entered is not correctly passed on to the login procedure of the program. However, I am sort of badly lacking a nice idea how to efficiently debug this thingy and verify (falsify ;) that I'm right. So, does anybody have an idea? Bye, David
Dump a trace into a file, then grep for the username and password you entered? On Fri, 10 Dec 2004, David [iso-8859-15] G�mbel wrote:
Hi everybody,
I am trying to get an application to run under Wine that requires a login with a username and a password. The program runs all fine, however I can't login with data that should work (and AFAIK works under Windows).
Having entered the password, in the corresponding part of the dialog I only see "*****" (which is correct). However, when I change focus to some other part of that dialog afterwards, the password field shows "*************" (way more asterisks than before). The previous (i.e. correct) length of ****s is restored when setting the focus back onto the password field.
I have reason to believe that the password I entered is not correctly passed on to the login procedure of the program. However, I am sort of badly lacking a nice idea how to efficiently debug this thingy and verify (falsify ;) that I'm right. So, does anybody have an idea?
Bye,
David
On Samstag 11 Dezember 2004 01:42, Walt Ogburn wrote:
Dump a trace into a file, then grep for the username and password you entered?
Are you refering to using something like strace, or would you use a debug channel? If a debug channel, which ?-) Bye, and thanks for your input! David
Sorry, I was thinking of the debug channels, but I don't know which ones to use, short of turning on "trace+all." - Walter On Sat, 11 Dec 2004, David [iso-8859-1] G�mbel wrote:
On Samstag 11 Dezember 2004 01:42, Walt Ogburn wrote:
Dump a trace into a file, then grep for the username and password you entered?
Are you refering to using something like strace, or would you use a debug channel? If a debug channel, which ?-)
Bye, and thanks for your input!
David
On Montag 13 Dezember 2004 18:03, you (Andreas Mohr) wrote:
On Sun, Dec 12, 2004 at 01:21:44AM -0800, Walt Ogburn wrote:
Sorry, I was thinking of the debug channels, but I don't know which ones to use, short of turning on "trace+all."
Probably something like +edit,+relay,+string
Thanks, I'll try that ;) Bye, David
David Gümbel wrote:
Hi everybody,
I am trying to get an application to run under Wine that requires a login with a username and a password. The program runs all fine, however I can't login with data that should work (and AFAIK works under Windows).
Having entered the password, in the corresponding part of the dialog I only see "*****" (which is correct). However, when I change focus to some other part of that dialog afterwards, the password field shows "*************" (way more asterisks than before). The previous (i.e. correct) length of ****s is restored when setting the focus back onto the password field.
Are you sure this isn't a security feature of the program? Does the program exhibit this behaviour in Windows?
I have reason to believe that the password I entered is not correctly passed on to the login procedure of the program. However, I am sort of badly lacking a nice idea how to efficiently debug this thingy and verify (falsify ;) that I'm right. So, does anybody have an idea?
It is unlikely, but not impossible to be a bug in the edit control. That code has been around for ages and is well tested, but then again this program could be using some really weird side effects. I would look elsewhere though. What is the password being checked against? Is it going over the network? Is it reading in a file off the disk and processing it? Is it using cryptography functions? Answering these will give you some clues with which to start debugging with. Rob
On Samstag 11 Dezember 2004 02:09, Robert Shearman wrote:
David Gümbel wrote:
I am trying to get an application to run under Wine that requires a login with a username and a password. The program runs all fine, however I can't login with data that should work (and AFAIK works under Windows).
Having entered the password, in the corresponding part of the dialog I only see "*****" (which is correct). However, when I change focus to some other part of that dialog afterwards, the password field shows "*************" (way more asterisks than before). The previous (i.e. correct) length of ****s is restored when setting the focus back onto the password field.
Are you sure this isn't a security feature of the program? Does the program exhibit this behaviour in Windows?
I don't think so, no, but I'll check again. I am, however, pretty sure this is not a feature.
I have reason to believe that the password I entered is not correctly passed on to the login procedure of the program. However, I am sort of badly lacking a nice idea how to efficiently debug this thingy and verify (falsify ;) that I'm right. So, does anybody have an idea?
It is unlikely, but not impossible to be a bug in the edit control. That code has been around for ages and is well tested, but then again this program could be using some really weird side effects. I would look elsewhere though.
OK, that sounds a lot like I was wrong assuming the problem is in the password dialog ;)
What is the password being checked against? Is it going over the network? Is it reading in a file off the disk and processing it? Is it using cryptography functions? Answering these will give you some clues with which to start debugging with.
The password is (I think) stored in a database file on disk. There's no networking involved at all, and I don't believe there's crypto being used. I'll try to look elsewhere now, that is - not in the dialog part of the system. Thank you for you input, I appreciate it. Bye, David
participants (5)
-
Andreas Mohr -
David Gümbel -
David Gümbel -
Robert Shearman -
Walt Ogburn