There was a short-lived conversation on FDN about firejail a few months ago.  I thought it important to remember that truly paranoid users need pay mind to hardware and their kernel.
http://forums.debian.net/viewtopic.php?p=644598#p644598

In terms of Palemoon tips, while I'm using it a lot less these days (solely because of webkit limitations), the biggest asset is researching, trying new plugins, and if they break, research any alternatives.  One of the best plugins is Palemoon Commander, which gives you access to an incredible amount of security and privacy options.  You can also make most of the same tweaks as you could with firefox in about:config.

Unfortunately, don't expect too much, because mainstream Firefox is completely changing, and it's disincentivizing past addons' developers from continuing backward compatibility; uMatrix, which offers script-blocking utilities, no longer works, and I'm getting the sense that noscript compatibility has died as well -- all of which is a shame.  That coupled along with trivial disputes between Moonchild Studios and other distributions, including openbsd, and I'm not sure I see much light at the end of Palemoon's tunnel.  There's another thread here about different browsers, if you'd like to see a comparison: https://dev1galaxy.org/viewtopic.php?id=1697

My guess is you need to remove the duplicate cdrom line, so your sources.list would read something like:

# deb cdrom:[devuan_ascii_2.0.0-rc_amd64_dvd-1]/ ascii main non-free

deb http://mx.deb.devuan.org/merged ascii main non-free contrib
[ ... ]

Then run sudo apt-get update and re-run the other command, with the dependencies, that I mentioned in my first reply.

If that works, it may help with your Input/Output issue.  It might be a problem with your kernel package, so you could try re-installing the kernel, like the person in that link did.  But I suspect that fixing your sources.list and updating will solve a few conundrums.

I usually use chunks of rock salt pasted together with hardened lard and envision bacon.  Cheaper than the store-bought bacon bits and just as good imho.

Can you post the full output of sudo apt-get install -y linux-headers-generic build-essential dkms?

Also, your wifi card model -- sudo lspci -vv | grep -i network -- and a link to your driver might be helpful, too.

I resonate GNUser's idea.

Maybe it's time to make a Trisquel forum account...

The article in the original post?  If so, they also published the paper as well.

Forgive me for finding this weird, because...

So that would seem to be a key component of the attack.

If I'm reading your posts correctly, and I believe you, but I'm concerned that there would be irrelevant misinformation in the paper about this attack.  I'll reach out to them and see if we can get clarification on some of these points.

@figdev - I resonate the sentiment that it's imprudent to assume one will not be exploited at some point on a computer.  It is a little disconcerting, but it's good that there are ways to mitigate it.

@golinux - suffice it to say the result of ignorance of an email infrastructure I was using.

Added a note at the top of the first post, for a list of email clients' vulnerability status.

Glad to hear you got it working I ran into a similar problem the first time I tried compiling a kernel.

Beratna!

Hey leave Pluto alone!  It's trying its hardest!

I completely forgot about this link.  But CTRL+F and "Pluto" gives me hope ^_^

It's "Carol," isn't it?

The article seemed to imply that this factors into the way they categorize, so maybe.

Expanse characters would make for a great distro's release cycle naming schema.

If you're using wicd, make sure your wifi interface is the same wireless interface in its settings.

You can list your network devices with ifconfig -a as root.
You can find your network card with lspci -vv | grep -i Network as root.  For some devices, you may need proprietary/nonfree software.

Glad to hear it.  Hope you enjoy it