[DNG] Devuan 3.0 Orca Problem

[David Hoff Jr]

I have install Beowulf to a 32 bit Acer netbook using the text

installer with speech. I have speech in the text console but no speech
with Orca in the GUI desktop including the login screen. In the GUI
Desktop terminal I can bring up the Orca preferences with Orca -r -s
and find that in the second tab page there is nothing in the Voice
type, Speech System or Speech synthasizer boxes.


Any suggestions how to fix this. I do have other sounds, just no
speech from Orca.



Sponsored by 
https://www.newser.com/?utm_source=part_medium=uol_campaign=rss_taglines_more

Seattle Goes Deep for Name of New NHL Team
http://thirdpartyoffers.juno.com/TGL3141/5f1a41aab19fe41aa5458st03vuc1
Jacksonville Convention Is Off
http://thirdpartyoffers.juno.com/TGL3141/5f1a41aad27e241aa5458st03vuc2
Ad With Biden, Obama Draws Trump Rebuke
http://thirdpartyoffers.juno.com/TGL3141/5f1a41ab7fa41aa5458st03vuc3___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Upgrade to Beowulf: iptables

[fraser kendall]

On Mon, 20 Jul 2020 21:10:08 -0400
Hendrik Boom  wrote:

> And did iptables work after the whole upgrade was finished?
Yes.  My existing ruleset was replaced with the default (permissive)
ruleset; thus by definition, iptables worked as intended by the
developers. However, as a manual iptables-restore command was
required to restore the previous protective ruleset, my considered
answer is 'no'.
> Did it still work as you intended?
No.  There is a warning that there are two rulesets in place, the
restored set (protective) and a second one, an 'iptables-legacy'
ruleset.  Both rulesets are the same.  Installation of the
iptables-persistent package installs rulesets from empty locations.

# apt-get update && apt-get install iptables-persistent

[...]
The following additional packages will be installed:
  netfilter-persistent
The following NEW packages will be installed:
  iptables-persistent netfilter-persistent
[...]
TUI menu item offering to save existing ruleset but the [Yes] [No]
option has been disabled 
[...]
Loading netfilter rules...run-parts:
executing /usr/share/netfilter-persistent/plugins.d/15-ip4tables start
Warning: skipping IPv4 (no rules to load)
run-parts:
executing /usr/share/netfilter-persistent/plugins.d/25-ip6tables start
Warning: skipping IPv6 (no rules to load)
done.

The debian wiki gives the following 2 commands for setting up
iptables-persistent which I understood to be required for the saved
rules to be loaded at boot

iptables-save > /etc/iptables/rules.v4
ip6tables-save > /etc/iptables/rules.v6

I have no confidence that installing iptables-persistent, will enforce
the protective ruleset on reboot. I have added four lines to the
eth0 entry in /etc/network/interfaces

pre-up iptables-restore < /etc/network/iptables.rules 
pre-up ip6tables-restore < /etc/network/ip6tables.rules 
pre-up iptables -L
pre-up ip6tables -L

Issuing #ifdown eth0 && ifup eth0
confirms that they should be.  However, this is a workaround.

We are offered an option to preserve existing versions of several files
during an upgrade that tries to replace them.  The option is
therefore readily available to avoid replacing an existing
iptables* ruleset. Another option might be to deploy iptables-apply to
rollback any changes to an existing ruleset by default (i.e. in the
absence of confirmation) as part of the upgrade. 

Best wishes

fraser 
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Upgrade to Beowulf: iptables

[fraser kendall]

On Mon, 20 Jul 2020 19:46:16 +0200
Ludovic Bellière  wrote:

> Running processes aren't stopped (restarted) until the new binaries
> are available, so your machine was still behind a firewall if rules
> were applied before the upgrade. iptables, ip6tables, and other
> alternatives serves as interface to the Netfilter packet filtering
> framework found in the kernel, the absence of such commands does not
> make the kernel unsafe.

Thank you for the clarification; it has been both instructive and
helpful.   However, as the replacement of the existing (protective)
ruleset with a default (permissive) ruleset is immediate: the 
dist-upgrade process is effectively issuing the command 
#iptables -P INPUT ACCEPT && iptables -F INPUT. Thus, it is not an
absence of such commands, it is an active issuing of permissive
commands to replace the existing protective ruleset in the
kernel.  The firewall is effectively being disabled with immediate
effect and will remain so until a protective ruleset is applied and
enforced. That is still essentially my concern.

Best wishes

fraser


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng