summaryrefslogtreecommitdiff
path: root/NEWS.rst
blob: 45f1012fad27a21f6200da93fdba709ccf79c141 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
==================================
User-facing changes in Leap Client
==================================

Release 0.2.0 (2013-1-XX)
--------------------------

This release is a functionally working version in Debian Wheezy and Ubuntu 12.04.
It is able to connect to a preconfigured leap provider and autoconfigures a EIP connection.

Python Support
''''''''''''''
This release supports Python2.6 and Python2.7

New Features
''''''''''''
- First run wizard: allows to register an user with the selected provider. It also downloads all
  the config files needed to connect to the eip service on this provider.
- Network checks: we do some basic network testing and warn user in case we cannot find a
  suitable network interface, or if the virtual interface dissapears after a successful eip connection.
- Debug mode and logfiles: the leap-client script allows to be invoked with the --debug flag.
  It also accepts a --logfile option that is useful for documenting bug reports.

Dependencies
''''''''''''
See the ``README.rst`` for a step-to-step install guide.

The following libraries are needed:

- PyQt4
- libgnutls
- openvpn

for building the package dependencies, you will need also:

- python-setuptools
- python-dev
- libgnutls-dev

Leap-Client depends on the following python packages:

- pyopenssl
- requests
- psutil
- netifaces
- jsonschema
- srp
- pycrypto
- keyring

We are freezing the python-gnutls library dependency for this release due to a bug in ubuntu, see:
https://bugs.launchpad.net/ubuntu/+source/python-gnutls/+bug/1027129


Configuration files
'''''''''''''''''''

Config files are created under ``~/.config/leap``
Currently user should be able to completely remove this folder and have it auto-generated in the first run.

- Current eip service config is stored in ``eip.json``
- Under ``.config/leap/providers``, there is a per-provider folder that contains:
  - ``provider.json``, with all options for connecting to this provider.
  - ``eip-service.json``, with eip-specific configuration options,
  - ``keys/ca``, for a copy of the ca certificates used in the tls connections to provider.
  - ``keys/client``, for a local copy of leap user certificates used in the eip connection.
- ``leap.conf`` for general application configurations (gui windows geometry, ...).