summaryrefslogtreecommitdiff
path: root/src/leap/bitmask
AgeCommit message (Collapse)Author
2015-09-18[bug] correctly return expected value for methods that check servicesKali Kaneko
these methods were returning None, and therefore breaking soledad password change (since it checks whether mail is enabled before changing soledad pass after srp pass change). - Resolves: #7470
2015-09-18[bug] show unread emails after sync completeIvan Alejandro
Right after a complete sync we show the unread emails. - Resolves: #7453
2015-09-17[style] pep8 fixesKali Kaneko
2015-09-18[feat] remove taskthread dependencyRuben Pollan
Refactor ivan's code (aa4b684d0682ff9faf1577653fa5ceabbc6e0f20) to remove the time.sleep. - Resolves: #7414
2015-09-17[bug] fix assignment of the incoming serviceKali Kaneko
the second callback was actually broken, not being called when it was supposed to be. the reason is that IncomingMail.startService returns a deferred which callback is called with the loopingCall instance only when the loopingCall is stopped.
2015-09-16[bug] authenticate logout calls to apiKali Kaneko
logout calls were not being authenticated, so we were receiving 401 return code.
2015-09-14[pkg] revert attempt to be compatible with logbook 0.6.0Kali Kaneko
we need the 'multi' feature all the same, so we'll be depending on logbook >= 0.7.0.
2015-09-11[bug] fix importKali Kaneko
there's an error in the import
2015-09-10[bug] add compatibility for logbook versions < 0.7.0Kali Kaneko
for the version in ubuntu trusty, the call for the zeromq handler initialization gets one less argument
2015-09-07[bug] fix argument number on window raise eventIvan Alejandro
- Resolves: #7415
2015-09-02[feat] load credentials from environment variableIvan Alejandro
Look for file defined in the `BITMASK_CREDENTIALS` env variable and load `provider`, `username` and `password` data. Trigger login if they were loaded correctly. The credentials file should look like this: [Credentials] username = my-account@my-provider.com password = secret - Resolves: #7419
2015-08-24[pkg] add icon for mail-only buildsKali Kaneko
2015-08-24[feat] allow to disable EIP on buildKali Kaneko
2015-08-24[bug] handle disabled registration, error 403.Ivan Alejandro
If the user wants to register a new account we check whether the provider allows registration or not right after getting the provider.json file and show an error msg on the wizard if not allowed. Also, there is a new signal to handle the error raised by the server if a registration attempt is made but is rejected with error 403. - Resolves: #6594
2015-08-14[bug] handle eip-config not providing locationsIvan Alejandro
Is valid for a provider not to provide locations for their gateways. - Resolves: #7281
2015-08-12[bug] fail more clearly if we got incorrect version stringKali Kaneko
on the sumo tarball, the _version file for leap/bitmask submodule wasn't being frozen, and hence BITMASK_VERSION was None. this was breaking the provider tests w/o any clear error message. - Related: #7322
2015-08-11[feat] add soledad sync progress to the UIIvan Alejandro
Register to Soledad's sync (send and receive) events and display the progress in the UI. - Resolves: #7353
2015-08-07[bug] workaround wrong qtplugins path rewritten in the libsKali Kaneko
this is a bug in macholib, there's a missing letter in the plugins path, so unless we fix this they cannot be loaded from the bundle. See: https://bitbucket.org/pydica/pyside-setup/commits/4b8be97e5a00b577fe30ce9aa7e5723ff2a66f94 Quoting from http://code.activestate.com/lists/pythonmac-sig/23278/: """ The problem might be this line: @rpath/Contents/mageformats/libqtiff.dylib The "i" from "imageformats" is missing! This _might_ be related to the unusual case that "libqtiff" has no path at all, or something else is funny, and we end up with a name that will not be found at all. Then the loader finds the plugin in the installed Qt, which causes it to load everything again from there. """
2015-08-07[bug] raise the maxfiles limit in OSXKali Kaneko
due to zmq, we are hitting the limit and getting app crashes. - Resolves: #7319
2015-08-07[doc] clarify that backend lives in a subprocessKali Kaneko
2015-08-07[bug] schedule signal emitting in reactor threadKali Kaneko
2015-08-07[feat] add path to gpg binary in the bundleKali Kaneko
2015-08-07[feat] add util function fo find location when frozenKali Kaneko
2015-08-07[test] fix SRP testsRuben Pollan
The tests where using deferToThread to run without need, I remove it and now it's easier to debug when one test fails. - Resolves: #7343
2015-08-05[feat] Move the updater code from the launcherRuben Pollan
The new pyinstaller method will rule out the launcher, we need the updater working inside bitmask client. - Closes: #7291
2015-07-24[feat] enable '--danger' for stable versionsIvan Alejandro
Is useful for new providers to be able to use the stable Bitmask version with this flag to be able to use custom certificates. - Resolves: #7250
2015-07-24[style] pep8 commentsIvan Alejandro
2015-07-20[refactor] minor reordering of events registrationKali Kaneko
Also, do not raise assertionerror, log warning instead.
2015-07-20[bug] start the events server when reactor is runningKali Kaneko
otherwise, events are not correctly registered - Resolves: #7149
2015-07-20[bug] prevent logbook subscriber to failIvan Alejandro
Fix: If the logbook controller is not started the stop call will fail. Trying to start it twice fails.
2015-07-20[style] grammar fixkwadronaut
- Resolves: #7284
2015-07-06[bug] run zmq log subscriber in backgroundIvan Alejandro
Prevent locks caused by the zmq log handler reaching the zmq's HWM (High water mark / buffer limit) and causing some components to block until the buffer is empty (running the zmq handler for instance). We run the zmq handler in the background all the time to prevent this. - Resolves: #7222
2015-06-30[style] fix typoKali Kaneko
s/self/sync
2015-06-29[bug] log contains exported PGP private keyIvan Alejandro
Due to #7139 (the logbook log centralizer) logs from 3rd party libs are included in the centralized logs with lots of debug information and we don't want that. We use the existing silencer to exclude logs that are not from leap modules. - Resolves: #7185
2015-06-22[bug] make sure log path existsIvan Alejandro
The logger is the first thing to be created and on a first run the config path won't exist. This way we make sure the path always exists.
2015-06-22[feat] log lsb_release info if availableKali Kaneko
if the lsb_release utility is present on system, log part of its output so we can have more information about the platform bitmask is running on. - Resolves: #7162 - Releases: 0.9.0
2015-06-22[feat] add log rotation featureIvan Alejandro
Rotate bitmask.log file on each start.
2015-06-22[feat] handle twisted/logging logs with logbookIvan Alejandro
Forward Twisted logs to logging and use logbook to handle logging logs. Store the bitmask logs on the config folder.
2015-06-22[feat] support new psutil APIIvan Alejandro
API to get the children has changed on latest psutil, this takes care of it.
2015-06-22[feat] replace old log handler with new oneIvan Alejandro
Replace logging.getLogger with custom get_logger. Remove some unneeded dependencies and reorder other.
2015-06-22[feat] add a zmq based logger, change log windowIvan Alejandro
- Add a new handler for a zmq/thread-safe log send between components. - Update the log window to use this new handler. - Remove old custom handler We have implemented a new handler that uses logbook, so this one is no longer needed. - Adapt log silencer to new handler - Use log file always as default - Related: #6733
2015-06-10[bug] don't run event server on the standaloneIvan Alejandro
We don't need to run the event server on the backend if we are running from the standalone bundle since the launcher takes care of that. - Related: #7126
2015-06-08[bug] fix attribute error on mail conductorKali Kaneko
due to remaining bits that had not been changed after a refactor. - Resolves: #7093
2015-06-05bug regression: polkit agent is not automatically launched #6652Parménides GV
Polkit was being launched and detected correctly, but Bitmask didn't propagate this result to upper layers, so mainwindow thought the platform wasn't initialized and then quitted without explanation. Tested on debian testing, on June 5th 2015, using i3 window manager. - Resolves: #6652
2015-06-01[bug] do not unset soledad proxy object too earlydrebs
The backend was unsetting the soledad proxied object before actually calling the soledad close() method and this was causing the application to hang when exitting. As the local soledad component's cancel_bootstrap() method is called before the close() method, we'd better not unset the proxied object there, and let only the close method do it. This commit fixes this by just removing the line that unsets the proxied object in the wrong place.
2015-05-29[bug] move events server init to backenddrebs
If the events server is initialized in a different process than the backend, the txzmq socket raises an "zmq.error.ZMQError: Interrupted system call" exception during the events server initialization. Despite that, communication seems to work flawlessly after the initialization. Moving the events server initialization to the same process as the backend causes the exception to not be raised during events server intialization.
2015-05-27[feat] adapt to new events api on commonIvan Alejandro
- Related: #6359
2015-05-21[bug] fix soledad bootstrap sync issuesRuben Pollan
* Instead of checking if soledad is still syncing for the timeuot cancel the delayed call. * Count retries properly. * Now soledad sync only returns SoledadError (#6981).
2015-05-08[feat] use txzmq in backenddrebs
Before this commit, the backend used plain pyzmq bindings for communicating with the frontend. This implements the txzmq twisted-powered bindings instead. Closes: #6360
2015-04-29[feat] update api port for pinned riseupIvan Alejandro
- Related: #6876