| Quote: | | | | | | | |
| I don't really agree with that too much, but I have a reason. First, if I was to try to gain unauthorized access to a network, I wouldn't use a copier. Second, passwords on these machines are always encrypted on these machines, so they couldn't get the password if they wanted. The username is going to be easy to find other ways. Third, if a user has access to a copier and they wanted to gain access to the network, they probably have the same access to a computer. A computer will give you a more detailed error and would be a "hacker's" preferred tool anyways.
When it comes down to it, the only way for an unauthorized user to gain access is to crack the password. If there is a way to extract the passwords off a bizhub 600, I need to know that trick.
The server connect error is almost like a customer saying "it don't work". You could have a few problems: DNS servers, smtp server name/address error, username problem, password problem, no smtp authentication, SSL encryption, incorrect sending protocol, firewall blocking ports, internet provider blocking ports, among a few others.
It would help greatly if they could provide a little more information about the actual "server connect error", like where it failed to connect.
Am I wrong? | |
| | |
You can disagree with the philosophy of the vagueness of the error message all you want. That isn't going to change the desire for it from the marketing side of things.
While I might like to have a more descriptive error message, even service techs are not supposed to know the inner details of things like passwords.
When all else fails, ethereal tells all.
And btw, e-mail passwords are in clear text by default. SMB passwords are another story.
Linear Mode
