Re: firewall-applet GTK+ -> Qt

2015-07-09 Thread Thomas Woerner



On 07/01/2015 06:18 AM, poma wrote:

On 29.06.2015 14:03, Thomas Woerner wrote:

On 06/17/2015 02:52 PM, poma wrote:

On 16.06.2015 15:11, Thomas Woerner wrote:

On 06/16/2015 01:28 PM, poma wrote:

On 15.06.2015 13:12, Thomas Woerner wrote:

On 06/15/2015 12:53 PM, poma wrote:

# yum install firewall-applet
...

 Package  Arch   Version
  Repository   Size

Installing:
 firewall-applet  noarch 0.3.14.1-1.fc23
  rawhide  96 k
Installing for dependencies:
 kde-filesystem   x86_64 4-51.fc22  
  rawhide  53 k
 libqzeitgeistx86_64 0.8.0-13.fc23  
  rawhide  75 k
 phonon   x86_64 4.8.3-4.fc23   
  rawhide 204 k
 phonon-backend-gstreamer x86_64 2:4.8.2-3.fc23 
  rawhide 147 k
 proj x86_64 4.9.1-2.fc23   
  rawhide 209 k
 python3-PyQt4x86_64 4.11.4-1.fc23  
  rawhide 3.1 M
 python3-sip  x86_64 4.16.8-1.fc23  
  rawhide  99 k
 qt-mobility-common   x86_64 
1.2.2-0.20.20140317git169da60c.fc23  rawhide  39 k
 qt-mobility-location x86_64 
1.2.2-0.20.20140317git169da60c.fc23  rawhide 584 k
 qt-mobility-sensors  x86_64 
1.2.2-0.20.20140317git169da60c.fc23  rawhide 125 k
 qtwebkit x86_64 2.3.4-7.fc23   
  rawhide  10 M

Transaction Summary

Install  1 Package (+11 Dependent packages)

Total download size: 15 M
Installed size: 56 M
Is this ok [y/d/N]:


firewalld-0.3.14
https://lists.fedorahosted.org/pipermail/firewalld-devel/2015-June/000175.html

firewall-applet:
   - new version using Qt4 fixing several issues with the Gtk version


What were the actual issues with the GTK+ version?


There have been several issues with the gtk applet:

1) The gtk statusicon widget is deprecated in gtk3, will be removed
soon. Going back to gtk2 is not a solution.

Xfce CORE is still GTK+ 2 based, therefore -stay- on GTK+ 2 -is- a solution. ;)

The old applet was using gtk3 since 2012. There are issues with gtk2 and
introspection. The use of pygtk was also not an option because of
missing python3 support, it also pulled in gobject, which then
conflicted with dbus.


2) The status icon was sometimes invisible without an error, warning or
any way to find out why, especially in Gnome3.

No problemos within the Xfce, works OK.


Yes, there have not been issues in Xfce for also all the time. But there
have been lots of issues with Gnome3. I had work arounds in the applet,
but those were not working with all Gnome3 versions.


3) The status icon was sometimes not showing the icon without an error,
warning or any way to find out why, especially in Gnome3 and gtk based
desktop environments.

No problemos within the Xfce, works OK.


See above.


4) With KDE5 there is no support for old-style system tray icons
anymore. Only Qt based applets and AppIndicator applets are supported,
but AppIndicator has the same issues with the icons in Gnome3 and other
gtk based desktops.


That's right, the Application Indicators aka "AppIndicator" is the 
Canonical/Ubuntu/Unity technology.


The Qt applet is working in KDE5, Gnome3, Xfce, Mate and others
supporting system tray icons without any issues for me. Therefore this
is the way to go.


There are some issues, at least within the Xfce - "shrivel" systray icon.
See "firewall-applet-Qt4-shrivel-systray-icon.png"

Same crap happens as with the vlc systray icon, again Qt4.


I do not see this in Xfce. Do you have special panel settings?


I've caricatured with the size, but the essence is the same:
http://goo.gl/Gm4ffO
Screencast/teeny-weeny.webm


I do not have issues with the size of the Qt applet in Xfce. I even
changed the size of the panel on the fly and it was adapting to the
current tray size. But please remember that there is a max size of tray
applets within Xfce. You can simply recognize that no applet gets bigger
than about 32 pixels.

There might be an issue with some of the themes though. Not all themes
in Xfce and gtk are behaving the same. Which theme are you using?


Additionally while doing the recode in Qt I realized that the UI
handling with Qt is much simpler and more predictable. I plan to port
firewall-config also over to Qt for one of the next releases.


Q

Re: firewall-applet GTK+ -> Qt

2015-06-29 Thread Thomas Woerner



On 06/17/2015 02:52 PM, poma wrote:

On 16.06.2015 15:11, Thomas Woerner wrote:

On 06/16/2015 01:28 PM, poma wrote:

On 15.06.2015 13:12, Thomas Woerner wrote:

On 06/15/2015 12:53 PM, poma wrote:

# yum install firewall-applet
...

Package  Arch   Version 
 Repository   Size

Installing:
firewall-applet  noarch 0.3.14.1-1.fc23 
 rawhide  96 k
Installing for dependencies:
kde-filesystem   x86_64 4-51.fc22   
 rawhide  53 k
libqzeitgeistx86_64 0.8.0-13.fc23   
 rawhide  75 k
phonon   x86_64 4.8.3-4.fc23
 rawhide 204 k
phonon-backend-gstreamer x86_64 2:4.8.2-3.fc23  
 rawhide 147 k
proj x86_64 4.9.1-2.fc23
 rawhide 209 k
python3-PyQt4x86_64 4.11.4-1.fc23   
 rawhide 3.1 M
python3-sip  x86_64 4.16.8-1.fc23   
 rawhide  99 k
qt-mobility-common   x86_64 1.2.2-0.20.20140317git169da60c.fc23 
 rawhide  39 k
qt-mobility-location x86_64 1.2.2-0.20.20140317git169da60c.fc23 
 rawhide 584 k
qt-mobility-sensors  x86_64 1.2.2-0.20.20140317git169da60c.fc23 
 rawhide 125 k
qtwebkit x86_64 2.3.4-7.fc23
 rawhide  10 M

Transaction Summary

Install  1 Package (+11 Dependent packages)

Total download size: 15 M
Installed size: 56 M
Is this ok [y/d/N]:


firewalld-0.3.14
https://lists.fedorahosted.org/pipermail/firewalld-devel/2015-June/000175.html

firewall-applet:
  - new version using Qt4 fixing several issues with the Gtk version


What were the actual issues with the GTK+ version?


There have been several issues with the gtk applet:

1) The gtk statusicon widget is deprecated in gtk3, will be removed
soon. Going back to gtk2 is not a solution.

Xfce CORE is still GTK+ 2 based, therefore -stay- on GTK+ 2 -is- a solution. ;)

The old applet was using gtk3 since 2012. There are issues with gtk2 and
introspection. The use of pygtk was also not an option because of
missing python3 support, it also pulled in gobject, which then
conflicted with dbus.


2) The status icon was sometimes invisible without an error, warning or
any way to find out why, especially in Gnome3.

No problemos within the Xfce, works OK.


Yes, there have not been issues in Xfce for also all the time. But there
have been lots of issues with Gnome3. I had work arounds in the applet,
but those were not working with all Gnome3 versions.


3) The status icon was sometimes not showing the icon without an error,
warning or any way to find out why, especially in Gnome3 and gtk based
desktop environments.

No problemos within the Xfce, works OK.


See above.


4) With KDE5 there is no support for old-style system tray icons
anymore. Only Qt based applets and AppIndicator applets are supported,
but AppIndicator has the same issues with the icons in Gnome3 and other
gtk based desktops.


That's right, the Application Indicators aka "AppIndicator" is the 
Canonical/Ubuntu/Unity technology.


The Qt applet is working in KDE5, Gnome3, Xfce, Mate and others
supporting system tray icons without any issues for me. Therefore this
is the way to go.


There are some issues, at least within the Xfce - "shrivel" systray icon.
See "firewall-applet-Qt4-shrivel-systray-icon.png"

Same crap happens as with the vlc systray icon, again Qt4.


I do not see this in Xfce. Do you have special panel settings?


I've caricatured with the size, but the essence is the same:
http://goo.gl/Gm4ffO
Screencast/teeny-weeny.webm

I do not have issues with the size of the Qt applet in Xfce. I even 
changed the size of the panel on the fly and it was adapting to the 
current tray size. But please remember that there is a max size of tray 
applets within Xfce. You can simply recognize that no applet gets bigger 
than about 32 pixels.


There might be an issue with some of the themes though. Not all themes 
in Xfce and gtk are behaving the same. Which theme are you using?



Additionally while doing the recode in Qt I realized that the UI
handling with Qt is much simpler and more predictable. I plan to port
firewall-config also over to Qt for one of the next releases.


Qt5 - ready steady?


There is also a Qt5 version, but it behaving strange in KDE5.


Bug r

Re: firewall-applet GTK+ -> Qt

2015-06-16 Thread Thomas Woerner

On 06/16/2015 01:28 PM, poma wrote:

On 15.06.2015 13:12, Thomas Woerner wrote:

On 06/15/2015 12:53 PM, poma wrote:


# yum install firewall-applet
...

   Package  Arch   Version  
Repository   Size

Installing:
   firewall-applet  noarch 0.3.14.1-1.fc23  
rawhide  96 k
Installing for dependencies:
   kde-filesystem   x86_64 4-51.fc22
rawhide  53 k
   libqzeitgeistx86_64 0.8.0-13.fc23
rawhide  75 k
   phonon   x86_64 4.8.3-4.fc23 
rawhide 204 k
   phonon-backend-gstreamer x86_64 2:4.8.2-3.fc23   
rawhide 147 k
   proj x86_64 4.9.1-2.fc23 
rawhide 209 k
   python3-PyQt4x86_64 4.11.4-1.fc23
rawhide 3.1 M
   python3-sip  x86_64 4.16.8-1.fc23
rawhide  99 k
   qt-mobility-common   x86_64 1.2.2-0.20.20140317git169da60c.fc23  
rawhide  39 k
   qt-mobility-location x86_64 1.2.2-0.20.20140317git169da60c.fc23  
rawhide 584 k
   qt-mobility-sensors  x86_64 1.2.2-0.20.20140317git169da60c.fc23  
rawhide 125 k
   qtwebkit x86_64 2.3.4-7.fc23 
rawhide  10 M

Transaction Summary

Install  1 Package (+11 Dependent packages)

Total download size: 15 M
Installed size: 56 M
Is this ok [y/d/N]:


firewalld-0.3.14
https://lists.fedorahosted.org/pipermail/firewalld-devel/2015-June/000175.html

firewall-applet:
 - new version using Qt4 fixing several issues with the Gtk version


What were the actual issues with the GTK+ version?



There have been several issues with the gtk applet:

1) The gtk statusicon widget is deprecated in gtk3, will be removed
soon. Going back to gtk2 is not a solution.


Xfce CORE is still GTK+ 2 based, therefore -stay- on GTK+ 2 -is- a solution. ;)


The old applet was using gtk3 since 2012. There are issues with gtk2 and 
introspection. The use of pygtk was also not an option because of 
missing python3 support, it also pulled in gobject, which then 
conflicted with dbus.





2) The status icon was sometimes invisible without an error, warning or
any way to find out why, especially in Gnome3.


No problemos within the Xfce, works OK.

Yes, there have not been issues in Xfce for also all the time. But there 
have been lots of issues with Gnome3. I had work arounds in the applet, 
but those were not working with all Gnome3 versions.



3) The status icon was sometimes not showing the icon without an error,
warning or any way to find out why, especially in Gnome3 and gtk based
desktop environments.


No problemos within the Xfce, works OK.


See above.


4) With KDE5 there is no support for old-style system tray icons
anymore. Only Qt based applets and AppIndicator applets are supported,
but AppIndicator has the same issues with the icons in Gnome3 and other
gtk based desktops.



That's right, the Application Indicators aka "AppIndicator" is the 
Canonical/Ubuntu/Unity technology.


The Qt applet is working in KDE5, Gnome3, Xfce, Mate and others
supporting system tray icons without any issues for me. Therefore this
is the way to go.



There are some issues, at least within the Xfce - "shrivel" systray icon.
See "firewall-applet-Qt4-shrivel-systray-icon.png"

Same crap happens as with the vlc systray icon, again Qt4.


I do not see this in Xfce. Do you have special panel settings?


Additionally while doing the recode in Qt I realized that the UI
handling with Qt is much simpler and more predictable. I plan to port
firewall-config also over to Qt for one of the next releases.



Qt5 - ready steady?


There is also a Qt5 version, but it behaving strange in KDE5.


"Qt 4.8.7 Released - Marks The End Of Qt4"
http://www.phoronix.com/scan.php?page=news_item&px=qt-4.8.7-qt4-update-released


https://github.com/t-woerner/firewalld/commit/2625806
New firewall-applet version using Qt
- Dropped shields up/down mechanism, was not optimal.

Please explain what was -not optimal-, related to "Shields" functionality.

Shields-up/-down was settings the default zone in firewalld. There is no 
runtime only setting for the default zone, therefore it was setting it 
for the whole system in a persistent way.


If there is a request, I will add it to the new applet.



$ rpm -q firewall-applet
firewa

Re: firewall-applet GTK+ -> Qt

2015-06-15 Thread Thomas Woerner

On 06/15/2015 12:53 PM, poma wrote:


# yum install firewall-applet
...

  Package  Arch   Version   
   Repository   Size

Installing:
  firewall-applet  noarch 0.3.14.1-1.fc23   
   rawhide  96 k
Installing for dependencies:
  kde-filesystem   x86_64 4-51.fc22 
   rawhide  53 k
  libqzeitgeistx86_64 0.8.0-13.fc23 
   rawhide  75 k
  phonon   x86_64 4.8.3-4.fc23  
   rawhide 204 k
  phonon-backend-gstreamer x86_64 2:4.8.2-3.fc23
   rawhide 147 k
  proj x86_64 4.9.1-2.fc23  
   rawhide 209 k
  python3-PyQt4x86_64 4.11.4-1.fc23 
   rawhide 3.1 M
  python3-sip  x86_64 4.16.8-1.fc23 
   rawhide  99 k
  qt-mobility-common   x86_64 1.2.2-0.20.20140317git169da60c.fc23   
   rawhide  39 k
  qt-mobility-location x86_64 1.2.2-0.20.20140317git169da60c.fc23   
   rawhide 584 k
  qt-mobility-sensors  x86_64 1.2.2-0.20.20140317git169da60c.fc23   
   rawhide 125 k
  qtwebkit x86_64 2.3.4-7.fc23  
   rawhide  10 M

Transaction Summary

Install  1 Package (+11 Dependent packages)

Total download size: 15 M
Installed size: 56 M
Is this ok [y/d/N]:


firewalld-0.3.14
https://lists.fedorahosted.org/pipermail/firewalld-devel/2015-June/000175.html

firewall-applet:
- new version using Qt4 fixing several issues with the Gtk version


What were the actual issues with the GTK+ version?



There have been several issues with the gtk applet:

1) The gtk statusicon widget is deprecated in gtk3, will be removed 
soon. Going back to gtk2 is not a solution.
2) The status icon was sometimes invisible without an error, warning or 
any way to find out why, especially in Gnome3.
3) The status icon was sometimes not showing the icon without an error, 
warning or any way to find out why, especially in Gnome3 and gtk based 
desktop environments.
4) With KDE5 there is no support for old-style system tray icons 
anymore. Only Qt based applets and AppIndicator applets are supported, 
but AppIndicator has the same issues with the icons in Gnome3 and other 
gtk based desktops.


The Qt applet is working in KDE5, Gnome3, Xfce, Mate and others 
supporting system tray icons without any issues for me. Therefore this 
is the way to go.


Additionally while doing the recode in Qt I realized that the UI 
handling with Qt is much simpler and more predictable. I plan to port 
firewall-config also over to Qt for one of the next releases.

--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Interaction: firewall-applet's icon & firewalld

2015-05-05 Thread Thomas Woerner

On 05/04/2015 09:05 PM, poma wrote:

…

Moreover, it is worthwhile to implement them as is "Applet shows notifications"
i.e. "notifications",
so they can be enabled also in the applet with the checkbox in the right mouse 
menu.



I've tested it and concluded:
when the control of appearance of the applet is in the applet itself,
when the applet is in "none-show-inactive" mode,
therefore, does not show its icon in the systray,
dconf mechanism must be used to show it again.

For this reason alone the use of this feature is not homogeneous,
so I withdraw this part of the proposal.



firewall-applet behaves in absence of the daemon like other applets do 
also, for example the NetworkManager applet. If the daemon is not 
running the applet is not shown.


To show the applet in this case has pros and also cons. If for example 
someone has deactivated firewalld, the applet will be visible all the 
time without providing any useful functionality.


There has been no change in the behavior of the applet since 2 releases.

I am thinking about an additional check if the firewalld service is 
enabled with systemd in this case.

--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Server issues

2014-11-18 Thread Thomas Woerner

On 11/18/2014 03:21 PM, Thomas Woerner wrote:

On 11/17/2014 06:54 PM, Ralf Corsepius wrote:

On 11/16/2014 07:06 PM, Ralf Corsepius wrote:

On 11/17/2014 06:19 PM, Mike Chambers wrote:

Have a few issues that are now having, but think they are all related..

Had a desktop (using as mini server) that was running Fedora 20.  I
used
yum to upgrade to latest on F21, both main and testing repos, and
upgraded without a hitch (no errors that I saw).

Now, I can't mount my nfs partitions, email client can't connect, no
ftp, no http.  I can connect to the server via ssh but that's it.  I
can
ping out to the internet from the server with no issues.


I am struggling with similar issues - manually nfs mounting works, but
autofs mounting nfs doesn't ;)


I believe to have found the cause:
* autofs in F21 defaults to using nfs3, while the server/client default
to nfs4.
* Also,  seemingly nfs-support in firewalld only seems to supports nfs4.


The ports for nfs3 are dynamic.

Please have a look at
http://docs.fedoraproject.org/en-US/Fedora/17/html/Security_Guide/sect-Security_Guide-Securing_NFS-NFS_Firewall_Configuration.html


It seems that you can not set any nfs options at the moment in F-21 in
/etc/sysconfig/nfs because all nfs services seem to use
EnvironmentFile=-/run/sysconfig/nfs-utils which does not exist
(RHBZ#1165187)

If nfs-config.service is active, the file will be generated from 
/etc/sysconfig/nfs - closed the bug again.



Ralf


Thomas



--
Thomas Woerner
Senior Software Engineer Phone: +49-711-96437-310
Red Hat GmbH Fax  : +49-711-96437-111
Wankelstrasse 5      Email: Thomas Woerner 
70563 Stuttgart  Web  : http://www.redhat.de/
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Server issues

2014-11-18 Thread Thomas Woerner

On 11/17/2014 06:54 PM, Ralf Corsepius wrote:

On 11/16/2014 07:06 PM, Ralf Corsepius wrote:

On 11/17/2014 06:19 PM, Mike Chambers wrote:

Have a few issues that are now having, but think they are all related..

Had a desktop (using as mini server) that was running Fedora 20.  I used
yum to upgrade to latest on F21, both main and testing repos, and
upgraded without a hitch (no errors that I saw).

Now, I can't mount my nfs partitions, email client can't connect, no
ftp, no http.  I can connect to the server via ssh but that's it.  I can
ping out to the internet from the server with no issues.


I am struggling with similar issues - manually nfs mounting works, but
autofs mounting nfs doesn't ;)


I believe to have found the cause:
* autofs in F21 defaults to using nfs3, while the server/client default
to nfs4.
* Also,  seemingly nfs-support in firewalld only seems to supports nfs4.


The ports for nfs3 are dynamic.

Please have a look at 
http://docs.fedoraproject.org/en-US/Fedora/17/html/Security_Guide/sect-Security_Guide-Securing_NFS-NFS_Firewall_Configuration.html


It seems that you can not set any nfs options at the moment in F-21 in 
/etc/sysconfig/nfs because all nfs services seem to use 
EnvironmentFile=-/run/sysconfig/nfs-utils which does not exist 
(RHBZ#1165187)



Ralf


Thomas

--
Thomas Woerner
Senior Software Engineer Phone: +49-711-96437-310
Red Hat GmbH Fax  : +49-711-96437-111
Wankelstrasse 5      Email: Thomas Woerner 
70563 Stuttgart  Web  : http://www.redhat.de/
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Cryptically zoned out Firewall

2012-11-06 Thread Thomas Woerner

On 11/06/2012 04:26 PM, Thomas Woerner wrote:

On 11/06/2012 01:07 AM, Chuck Forsberg WA7KGX N2469R wrote:

The new firewall replaces the old "trusted interface" with
multiple "zones" .  This would be fine if one could easily
tell which zone each network interface was in and
make changes.


firewalld is not selecting the zone for an interface related to a
connection. NetworkManager does this. The zone is set in the ifcfg
config file, if it is not the default zone.


The only to change an interface's zone is with an arcane
firewall-cmd incantation.


There is a patch for the gtk nm-connection-editor to add a very simple
selection menu for connections. The NM connection editor in KDE is
providing support for this already.

This has been integrated into network-manager-applet upstream and should 
hit Fedora soon. Within nm-connection-editor the zone for interfaces 
related to a connection can be changed.



Given the new concepts of persistence and zones, the
admin>firewall applet needs to present these concepts
to the user in a clearly intuitive, easy to change way.


Ok, the firewall-applet should provide information on how to do change
zones for connections, I agree.


The current view should be radio buttons.
Each interface should have a selector for which zone
it should be in.  Finally, do we need so many zones?
A default of two zones should suffice and be more
understandable.  At least don't show zones that aren't used.


There are the base zones: block, drop, public, work and trusted. The
other zones have been added on request. You can also add own zones
according to your needs.

Thomas


--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Cryptically zoned out Firewall

2012-11-06 Thread Thomas Woerner

On 11/06/2012 01:07 AM, Chuck Forsberg WA7KGX N2469R wrote:

The new firewall replaces the old "trusted interface" with
multiple "zones" .  This would be fine if one could easily
tell which zone each network interface was in and
make changes.

firewalld is not selecting the zone for an interface related to a 
connection. NetworkManager does this. The zone is set in the ifcfg 
config file, if it is not the default zone.



The only to change an interface's zone is with an arcane
firewall-cmd incantation.

There is a patch for the gtk nm-connection-editor to add a very simple 
selection menu for connections. The NM connection editor in KDE is 
providing support for this already.



Given the new concepts of persistence and zones, the
admin>firewall applet needs to present these concepts
to the user in a clearly intuitive, easy to change way.

Ok, the firewall-applet should provide information on how to do change 
zones for connections, I agree.



The current view should be radio buttons.
Each interface should have a selector for which zone
it should be in.  Finally, do we need so many zones?
A default of two zones should suffice and be more
understandable.  At least don't show zones that aren't used.

There are the base zones: block, drop, public, work and trusted. The 
other zones have been added on request. You can also add own zones 
according to your needs.


Thomas
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[Test-Announce] Test Day: firewalld

2012-03-19 Thread Thomas Woerner

Hello,

today is firewalld test day.

https://fedoraproject.org/wiki/Test_Day:2012-03-19_firewalld

For testing please use a fully updated Fedora 17 installation (all 
testing packages applied). For test cases and more information please 
have a look at the test page.


If you need assistance or if you have quesitions about firewalld, feel 
free to ask us on #fedora-test-day.


Thanks,
Thomas
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test