epoptes team mailing list archive
-
epoptes team
-
Mailing list archive
-
Message #00079
[Bug 940114] Re: Epoptes crashes when a client with an invalid server's certificate connects
This was fixed in epoptes 0.4.4.
** Changed in: epoptes
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Epoptes
Developers, which is the registrant for Epoptes.
https://bugs.launchpad.net/bugs/940114
Title:
Epoptes crashes when a client with an invalid server's certificate
connects
Status in Epoptes:
Fix Released
Bug description:
After launching epoptes I see a preview screen, the user, but only 1
maybe 2 times. Then do not. In the console I have the information:
New connection from 192.168.0.223:36473
Disconnect from 192.168.0.223:36473
**Twisted error: when executing command if ./screenshot 100 75; then BAD_SCREENSHOTS=0; elif [ "$BAD_SCREENSHOTS" = 3 ]; then exit 1; else BAD_SCREENSHOTS=$(($BAD_SCREENSHOTS+1)); fi on client 127.0.0.1:49734: [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionDone'>: Connection was closed cleanly.
Unhandled error in Deferred:
Traceback (most recent call last):
Failure: twisted.internet.error.ConnectionDone: Connection was closed cleanly.
Screenshot for client 127.0.0.1:49734 timed out. Requesting a new one...
**Twisted error: when executing command if ./screenshot 100 75; then BAD_SCREENSHOTS=0; elif [ "$BAD_SCREENSHOTS" = 3 ]; then exit 1; else BAD_SCREENSHOTS=$(($BAD_SCREENSHOTS+1)); fi on client 127.0.0.1:49734: [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionDone'>: Connection was closed cleanly.
.
.
Screenshot for client 127.0.0.1:49714 timed out. Requesting a new one...
**Twisted error: when executing command if ./screenshot 100 75; then BAD_SCREENSHOTS=0; elif [ "$BAD_SCREENSHOTS" = 3 ]; then exit 1; else BAD_SCREENSHOTS=$(($BAD_SCREENSHOTS+1)); fi on client 127.0.0.1:49714: [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionDone'>: Connection was closed cleanly.
]
Strange, because the computers in the network have addresses 192.168.0.x, and the errors in the console 127.xxx
As if epoptes lose connection with their customers. When you click on the icon of customer information is not displayed if no information
To manage notifications about this bug go to:
https://bugs.launchpad.net/epoptes/+bug/940114/+subscriptions
References