-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 13 Jan 2015 21:02:09 +0100
Reindl Harald wrote:
>
> Am 13.01.2015 um 20:56 schrieb William B:
> > Unbound creates more flakiness than it solves. Unbound caches "no
> > answer" as a negative cache entry. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> To install a local DNS resolver trusted for the DNSSEC validation
> running on 127.0.0.1:53. This must be the only name server entry
> in /etc/resolv.conf.
snip ...
> People use Fedora on portable/mobile devices which are connected to
> divers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>
> If by opening up some ports that would have hampered the user, rather
> than protect them[1], we avoid the users disabling the firewall, and
> exposing security critical services (such as exposing rpcbind, or
> ntpd, or any other root service), th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 09 Dec 2014 10:08:06 +0100
Nikos Mavrogiannopoulos wrote:
> On Tue, 2014-12-09 at 17:29 +1030, William B wrote:
> > > > I just happened to look at the firewalld default settings, and I
> > > > was not amused when I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> > I just happened to look at the firewalld default settings, and I
> > was not amused when I noticed this:
> > http://pkgs.fedoraproject.org/cgit/firewalld.git/tree/FedoraWorkstation.xml
> > >
> > >
> > This "firewall" is a joke! ALL higher ports
