On Thursday, July 03, 2014 11:51:33 PM Richard Z wrote: > On Thu, Jul 03, 2014 at 07:43:50AM -0500, Anthony Messina wrote: > > > > > > I'm using the following kde-connect service template with great > > success. I have also created a my_internal zone which makes it easy to > > add services to that zone. That way, you don't need to add so many rich > > rules; just create new services and add them to your unique source-based > > zone. > > looks pretty good to me. Still not obvious how to package this so it would > work out of the box with minimal hassle while retaining all the security? As for upstream, I'm not sure. They could at least package the kde-connect service xml template. For me, I maintain a "workstation" RPM package with all these little bits of configuration that are specific to hosts on my network. -- Anthony - http://messinet.com - http://messinet.com/~amessina/gallery 8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E
Attachment:
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ kde mailing list kde@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
