bitmask-dev.git/src/leap/bitmask/backend, branch 0.7.0rc1 [bitmask-dev] Revert "Fix soledad imports (#5989)." 2014-09-26T13:13:44+00:00 Tomás Touceda chiiph@leap.se 2014-09-26T13:13:44+00:00 0db3d5a4aecc0a3c271b92c6187922c50d46df0a This reverts commit 7fcc4f40eaa8214de8ae20cd71d173337ad64290. 
This reverts commit 7fcc4f40eaa8214de8ae20cd71d173337ad64290.
Don't defer action to thread here. 2014-09-03T18:00:50+00:00 Ivan Alejandro ivanalejandro0@gmail.com 2014-09-01T21:31:36+00:00 4f4520d938f726b344e1a71949f83aa385d92acd We already are running the methods in a thread from the backend. 
We already are running the methods in a thread from the backend.
make the login not wait for eip it cannot-start-eip 2014-08-19T03:08:20+00:00 Kali Kaneko kali@leap.se 2014-08-19T03:02:09+00:00 9f8c6bdda8ca6274e2d013d6528ab4ff83b35654 






Fix soledad imports (#5989).
2014-08-18T14:36:09+00:00

drebs
drebs@leap.se

2014-08-18T14:36:09+00:00

7fcc4f40eaa8214de8ae20cd71d173337ad64290












fix uncatched error with missing polkit. Closes: #5955
2014-08-06T14:54:34+00:00

kali
kali@katsi

2014-08-05T17:43:25+00:00

9a7485bcaf5460d68b7f601927500299bb2ca9f0












Add cancel button for EIP connection.
2014-08-01T20:40:04+00:00

kali
kali@katsi

2014-07-28T00:00:37+00:00

3b469a2c006381ba9e56c1de92be4e87ad67e51b

Closes: #4035

This falls in the "quick" workaround category.

A proper state machine that extends the four basic connection states
is hence needed. We have to accomodate design to have a
connection-oriented state machine in the backend (I would favor a
twisted protocol for this), and a more lightweight one that conducts
the gui-level changes (ie, change the actions / buttons / labels
accordingly).

Since this "cancel" functionality has been long postponed, I chose
to do one more ugly hack here, that is, show and hide dance with a
button that just calls the bitmask-root to kill the vpn process. It
should work well enough until we get to the reorganization needed for a
clean process control for eip.





Closes: #4035

This falls in the "quick" workaround category.

A proper state machine that extends the four basic connection states
is hence needed. We have to accomodate design to have a
connection-oriented state machine in the backend (I would favor a
twisted protocol for this), and a more lightweight one that conducts
the gui-level changes (ie, change the actions / buttons / labels
accordingly).

Since this "cancel" functionality has been long postponed, I chose
to do one more ugly hack here, that is, show and hide dance with a
button that just calls the bitmask-root to kill the vpn process. It
should work well enough until we get to the reorganization needed for a
clean process control for eip.







Add frontend alive check to the backend.
2014-07-24T18:23:20+00:00

Ivan Alejandro
ivanalejandro0@gmail.com

2014-07-22T14:33:09+00:00

ce88b52295881a3dd1bc0efec8e72b1d3a235e87

Stop the backend if the frontend process does not exist any more and
backend is not a daemon.





Stop the backend if the frontend process does not exist any more and
backend is not a daemon.







Merge remote-tracking branch 'refs/remotes/ivan/feature/add-backend-alive-check' into develop
2014-07-24T18:19:02+00:00

Tomás Touceda
chiiph@leap.se

2014-07-24T18:19:02+00:00

faadf8dc3bb1e49adc23c64d5a851b7eea0ce2ee












Restrict access to the zmq certificates folder.
2014-07-23T15:03:44+00:00

Ivan Alejandro
ivanalejandro0@gmail.com

2014-07-23T15:03:44+00:00

227a31d8892c67c64beebe5135cc850dfa71c3c6












Add heartbeat to check if backend is alive.
2014-07-21T20:11:33+00:00

Ivan Alejandro
ivanalejandro0@gmail.com

2014-07-21T20:03:47+00:00

68b1be8ef443b088cf5c1f7f964e1bd7ad42408e

Send a 'ping' request every 2 secs to ensure that the backend is
running.
Use polling instead of recv on the backend_proxy. This was already
implemented for the signaler.





Send a 'ping' request every 2 secs to ensure that the backend is
running.
Use polling instead of recv on the backend_proxy. This was already
implemented for the signaler.