Jaakko Niemi schrieb: > It is intended behaviour to get into a loop and error out > with totally useless error message? Surely not... please > tell the user if he's doing something wrong! > > And the client was from same version of Debian packages > as the server, for sure. I remember using username and > password for login.. have to retry this one of these > days.. too long gone to remember exactly.
Could you please install the latest version (0.6.4-13) and verify that you get this "error message" only when you use different networking options, e.g. the server has disabled LOGIN support or you try to connect from within the client without SSL encryption. You can test that as follows: Start "partimaged -L -g 10 -d /tmp" and try to connect with partimage. You should get an error message within partimage telling you that you that the connection was refused and you are using different networking options. The server should log, that it received a wrong banner and rejected/refused the connection. The server must not crash. (This is what I meant with intended behaviour: You tell the server to reject connections which use the LOGIN mechanism. The server does so and the client gets an error message. We could argue that the error message in the log file is not very descriptive. But this is not an important bug, imho.) If this is the behaviour you get, and not something completely different, then again I have to say that this is the correct behaviour and I will have to close this bug. At most I will accept if you set the importance to wishlist and retitle it to something like "Error logging in case of different networking options is insufficient". Cheers, Michael -- ------------------------------------------------------------ E-Mail: [EMAIL PROTECTED] WWW: http://www.teco.edu/ TecO (Telecooperation Office) Vincenz-Priessnitz-Str.1 University of Karlsruhe 76131 Karlsruhe, Germany ------------------------------------------------------------
signature.asc
Description: OpenPGP digital signature
