KubuntuEasyZeroconf

Differences between revisions 1 and 2
Revision 1 as of 2006-06-09 09:26:18
Size: 893
Editor: t10683
Comment:
Revision 2 as of 2006-06-21 16:07:17
Size: 2896
Editor: ALagny-109-1-10-249
Comment:
Deletions are marked like this. Additions are marked like this.
Line 18: Line 18:
Jack wants to avoid to make any ad hoc configuration to access his network services at home.

Alice is going to several conferences and wants to easily discover the available services or expose services. But, she doesn't want zeroconf to keep running forever for security reasons.
Line 19: Line 23:

Currently avahi is not installed on the system. Users have to locate the relevant package and install it to make "zeroconf" works. To make sure it's not running anymore they have to uninstall it.
Line 22: Line 28:
KDE has already a zeroconf stack able to use avahi in kdelibs, a ioslave allowing to browse services available, and a kcontrol module to configure of the zeroconf stack. We will create the necessary facilities to enable avahi on demand so that it can be installed by default but inactive, this way the system would stay secure by default while not hampering the user experience.
Line 23: Line 31:

 1. Introduce {{{/etc/default/avahi-daemon}}} file holding an {{{ENABLED_ON_BOOT}}} key, the value will be 0 by default. The {{{/etc/init.d/avahi-daemon}}} would start avahi on boot only when {{{ENABLED_ON_BOOT=1}}}.

 1. Patch kdelibs package so that the kde zeroconf stack is disabled by default.

 1. The current kcontrol module for zeroconf support has a checkbox to enable/disable the kde zeroconf stack. This kcontrol module should be patched to also act on the {{{/etc/default/avahi-daemon}}} file to enable/disable avahi starting on boot (using kdesu).

 1. Patch the ioslave and the kdelibs zeroconf support so that when the user access the ioslave, or when an application tries to expose a service while zeroconf is disabled we popup a dialog like the following one:
{{{
--------------------
| Enable Zeroconf? |
| [ ] Forever |
| [Yes] [No] |
--------------------
}}}
If the user answers "yes", avahi is started (using kdesu) and the kde zeroconf stack is activated on success. If the "forever" checkbox is checked, we also put {{{ENABLED_ON_BOOT=1}}} in the {{{/etc/default/avahi-daemon}}} file.

Summary

Provide an easy way to turn on zeroconf in Kubuntu

Rationale

Zeroconf is turned off by default for security reasons, we should provide an easy way to turn it on.

Use cases

Jack wants to avoid to make any ad hoc configuration to access his network services at home.

Alice is going to several conferences and wants to easily discover the available services or expose services. But, she doesn't want zeroconf to keep running forever for security reasons.

Scope

Currently avahi is not installed on the system. Users have to locate the relevant package and install it to make "zeroconf" works. To make sure it's not running anymore they have to uninstall it.

Design

KDE has already a zeroconf stack able to use avahi in kdelibs, a ioslave allowing to browse services available, and a kcontrol module to configure of the zeroconf stack. We will create the necessary facilities to enable avahi on demand so that it can be installed by default but inactive, this way the system would stay secure by default while not hampering the user experience.

Implementation

  1. Introduce /etc/default/avahi-daemon file holding an ENABLED_ON_BOOT key, the value will be 0 by default. The /etc/init.d/avahi-daemon would start avahi on boot only when ENABLED_ON_BOOT=1.

  2. Patch kdelibs package so that the kde zeroconf stack is disabled by default.
  3. The current kcontrol module for zeroconf support has a checkbox to enable/disable the kde zeroconf stack. This kcontrol module should be patched to also act on the /etc/default/avahi-daemon file to enable/disable avahi starting on boot (using kdesu).

  4. Patch the ioslave and the kdelibs zeroconf support so that when the user access the ioslave, or when an application tries to expose a service while zeroconf is disabled we popup a dialog like the following one:

--------------------
| Enable Zeroconf? |
| [ ] Forever      |
|   [Yes] [No]     |
--------------------

If the user answers "yes", avahi is started (using kdesu) and the kde zeroconf stack is activated on success. If the "forever" checkbox is checked, we also put ENABLED_ON_BOOT=1 in the /etc/default/avahi-daemon file.

Code

Data preservation and migration

Outstanding issues

BoF agenda and discussion

Install avahi by default have avahi turned off by default with a variable in /etc/defaults to turn it on tick box to turn it on provide binary to easily query and change /etc/defaults


CategorySpec

KubuntuEasyZeroconf (last edited 2008-09-12 02:07:24 by HSI-KBW-091-089-037-065)