Epoptes crashes when a client with an invalid server's certificate connects

Bug #940114 reported by kadkarol
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Epoptes
Fix Released
Medium
Unassigned

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

Related branches

Revision history for this message
Alkis Georgopoulos (alkisg) wrote :

> New connection from 192.168.0.223:36473
> Disconnect from 192.168.0.223:36473

I think the problem is because you have an old epoptes-client version installed in your chroot, or you don't have an up to date certificate. Please try the following:

sudo chroot /opt/ltsp/i386 dpkg-query -W epoptes-client
diff /etc/epoptes/server.crt /opt/ltsp/i386/etc/epoptes/server.crt

If you see that the client version is old, or that the certificates differ, follow the instructions in http://www.epoptes.org/installation to update the package and the certificate in your chroot, and then run ltsp-update-image.

Changed in epoptes:
status: New → Incomplete
Revision history for this message
kadkarol (karol-sienkowski) wrote :

I have new version client in chroot (epoptes-client 0.4.3-0ubuntu1~natty1). I update certyficate and nothing helps. sometimes I can preview the four screens, sometimes six and sometimes first I still did not work.

Revision history for this message
Fotis Tsamis (ftsamis) wrote :

kadkarol,

The client with IP 192.168.0.223 doesn't have the correct server's certificate.

If this is an ltsp client, please make sure you have correctly followed the instructions in http://www.epoptes.org/installation (execute epoptes-client -c in your chroot and ensure that it doesn't throw any errors, and then execute ltsp-update-image outside the chroot.)

If it's a standalone client, execute epoptes-client -c or transfer the server.crt manually.

Of course epoptes shouldn't crash when there is a client with a wrong certificate, so this is a bug...

Changed in epoptes:
importance: Undecided → Medium
status: Incomplete → Confirmed
summary: - I can not preview the user's screen in ubuntu ltsp environment
+ Epoptes crashes when a client with an invalid server's certificate
+ connects
Revision history for this message
kadkarol (karol-sienkowski) wrote :

Hi,
I think this is not the fault of the certificates. Once the communication with the client and the second time is not with the same client.
I changed nothing else in the configuration. Today, I waited to start epoptes until all thin clients logging. Epoptes works well!

Revision history for this message
Alkis Georgopoulos (alkisg) wrote :

This was fixed in epoptes 0.4.4.

Changed in epoptes:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.