Age | Commit message (Collapse) | Author |
|
|
|
srp auth breaking with 1.0 api
|
|
|
|
|
|
Changing this now to be able to test different providers by
just updating our local config file.
|
|
So we officially can say this is a generic client now.
Branding config file is still at pkg/branding/config.py
Note that with this change the package is called now leap-client
so you will have to remove old installs of leap-foo-client in your
path (from previous branded builds).
Changing the package name was an AWFUL and painful idea, and we will not
do that again. (launcher is another story). Lesson learned.
|
|
|
|
|
|
|
|
using a quite lame cryptedfile by the moment until dbus bug
makes gnome-keyring usable again or we come up with the
encrypted database solution. we might want to explore the
option of using this python-keyring with the different
native backends for win and macosx.
for now: we generate a random secret that we store in the qsettings file.
so, the whole thing is just to avoid plaintext stuff.
for this, we could have done rot13, haha.
|
|
|
|
hopefully it's a bit more clear now.
developer: feedback welcome. are you able to get it running
with the instructions listed here?
|
|
|
|
|
|
Conflicts:
src/leap/eip/config.py
src/leap/eip/specs.py
|
|
|
|
and a jsonvalidate function too,
that calls to jsonchemea.validate(self, data) with self.schema
We're using the specs to both purposes now:
* providing a type casting system for our config options (work in
progress for the type casting)
* json schema validation
|
|
|
|
|
|
2) uses distribute instead of setuptools.
3) creates symlinks to PyQT and sip.so.
|
|
|
|
|
|
|
|
Close #502
|
|
|
|
|
|
ping the listed gateway.
|
|
of the unability to pip install PyQt4.
postmkvenv workaround for PyQt libs for manual use.
pip install breaks because they don't have a standard setup.py
installation process
|
|
also test_requires using parse_requirements
|
|
|
|
renamed setup-->pkg because name collision
|