rss
Documentation updates (modules states, small reorganization)
I've just updated the Licorn® documentation:
- the modules states are now clearly defined; the code is not yet up-to-date, but it's the next thing to do on core, backends and extensions.
- backends documentation is a little more clean than before. The URL to access it is better spelled and doesn't display a 403 HTTP error anymore: http://docs.licorn.org/core/backends.
- French translation has progressed a little, on the related subjects.
Mounting all volumes
With #500 implemented, Licorn® now supports mounting any kind of volumes on the local machine, provided you add extensions.volumes.mount_all_fs = True in your /etc/licorn/licorn.conf file.
This makes licornd provide the same functionnalities as udisks, allowing to avoid it completely when you run licornd on your laptop or desktop machine.
End-User-formatted (vfat/nfts/iso9660/udf) volumes will be mounted with the UID of the console user. Other types (ext*/btrfs/reiserfs/xfs/jfs) will be mounted the standard way, with acl and user_xattr options.
If for any reason you plug your device in before logging in on your machine, just launch the following commands:
del vol -a add vol -a
And licornd will remount the volumes accordingly for you.
Note: I didn't test the behavior when logged in remotely. I don't think an ssh remote login will be treated like a normal local login. This will probably be implemented in a future enhancement if needed.
Volumes and Rdiff-backup extensions entered the repository
Theses extensions are ready for wider testing. They have their documentation setup ( volumes and rdiffbackup).
A major thread rewrite has been done during this dev cycle.
CLI and WMI related parts are coming in.
First official extension: openssh
Tonight I sprint-coded the OpenSSH extension, removed all openssh-related code in LMC.configuration, and added system-service-related code to SystemController class.
Guess what:
- It works like a charm :-)
- I readded the missing functionnalities from previous releases (the AllowGroups configuration directive), and added much more (enable/disable ssh extension and service, check other configuration directives, verify the sshd is running...)
By the way, members of remotessh are allowed to connect, and members of admins too (regardless of their remotessh member status: this is cool because you (the reader) are probably already a member of admins, and you won't ever notice the sshd group-authorization enforcement ;-)
The OpensshExtension module can serve as an extension model: it seems quite clean (and short) to me.
This work would not have been so easy without the ConfigFile class Robin wrote. I enhanced it a little, but it's so practical!!
Modules (backends and extensions) renamed, better handling
To avoid conflict with eventual future backends and to stick a little more with reality, the unix backend has been renamed to shadow, and the ldap backend has been renamed to openldap. They are held in files shadow.py and openldap.py in the ShadowBackend and OpenldapBackend classes. Much readable, isn't it?
Configuration, testsuite, documentation website are up-to-date with this change.
Module loading is now much more clean: the backends and extensions do not need to be instanciated in their python file anymore, this is taken care by the manager. This makes code much understandable (I hope), shorter, and more standard. Sphinx autodoc can now be used on backends classes too, whereas it wasn't possible before.
core.backends.classes has dissapeared (the related code is now directly inside core.backends.__init__), and idem for extensions.classes (now in extensions.__init__).
So, The python modules filenames and controller classes names changed, and are shorter: e.g. dnsmasq.py holds the DnsmasqBackend (instead of dnsmasq_backend.py containing dnsmasq_controller), and so on. This rule applies for backends and extensions.
Small other renames have landed too, like ModuleManager having becomed ModulesManager and other minor changes.
