I guess by now it must be clear that I am no longer maintaining GnuDIP. I don't have either the time or inclination. I am still willing to help someone else though. Two people have full access to the GnuDIP site, having expressed interest in extending GnuDIP, but I guess they have no time either.
===
About endianness ...
GnuDIP only ever exchanges character information - never binary. So this should not be an issue. The message here indicates that the password has failed to validate. It would be good to add a statement to minidip.pl to log the the password that has been passed to make sure it is correct.
I wonder if the case could somehow be getting changed? Or perhaps there is some sort of character encoding issue? The only other thing I can think of is that there may some sort of non-display character at the end of the lines in gnudip.conf that have the passwords (e.g.. carriage return). This would get tacked onto the passord when gnudip.conf was read. If this was true for other lines in gnudip.conf, then I would expect minidip.pl to fail misearably long before it gets to checking any passwords.
Subject: Re: [GnuDIP] A way to get more debug info From: Devin Reade <[EMAIL PROTECTED]> Date: 2002-10-03 13:43:08Sean McAvoy wrote:Minidip stil uses the same perl script to update, except it has no web interface or DB, you simply add hosts/passwords in the config. The really bizare thing is that when I use the config on an x86 system, it works. When I use it on a Motarola Coldfire processor (running uCLinux), it gives me an invalid login error...That sounds like an endianness issue. -- Devin Reade <[EMAIL PROTECTED]>
-- Creighton MacDonnell http://macdonnell.ca/ ------------------------------------------------------- This sf.net email is sponsored by: viaVerio will pay you up to $1,000 for every account that you consolidate with us. http://ad.doubleclick.net/clk;4749864;7604308;v? http://www.viaverio.com/consolidator/osdn.cfm -- GnuDIP Mailing List http://lists.sourceforge.net/lists/listinfo/gnudip2-general
