Somewhat OT: Sound won't work at all on Firefox
by Sergio Belkin
Hi!
Suddenly I have not any sound in Firefox, whatever be the site: youtube,
netflix, vimeo, etc. Until yesterday everything worked like a charm.
And whatever be the version of Firefox, upgraded to 81, Firefox in "safe
mode", even Firefox ESR.
Besides that, Chrome, Chromium, Falkon, all of them play audio fine.
Any there with this issue?
(Running Fedora 32 with Plasma)
Thanks in advance
--
--
Sergio Belkin
LPIC-2 Certified - http://www.lpi.org
3 years, 6 months
Fedora 33 - ssh clients - drop of PubkeyAcceptedKeyTypes=ssh-rsa
by Pavel Raiskup
After upgrade of one of my servers to F33, I noticed that I can not ssh to
one of my other servers running Debian 9 system (relatively freshly EOLed,
I need to do something about it). On F33 I always need to:
$ ssh -oPubkeyAcceptedKeyTypes=+ssh-rsa user@debian-9-host
The changes in Fedora packages led me to:
https://gitlab.com/redhat-crypto/fedora-crypto-policies/-/commit/b298a9e1
Which led me to:
https://fedoraproject.org/wiki/Changes/StrongCryptoSettings2
I'm curious about the effects of the change. It claims that RSA 2048 >= should
stay accepted by DEFAULT, and from what I can tell the host server key seems to
be RSA 2048 (at least that's what is generated by default on Debian 9):
$ ssh-keygen -l -f ssh_host_rsa_key.pub
2048 SHA256:<...> root@debian-9-host (RSA)
Can anyone translate to me if this is really expected or a bug? Effect is that
Fedora 33 clients can not ssh to Debian 9 hosts by default (I'm not sure about
the supported Debian 10, and the key quality there).
Pavel
3 years, 6 months
systematically comparing stacks across platforms
by Daniel Pocock
In my adventures with ppc64el (Talos II, POWER9), I've come across some
issues in things that just don't quite work.
When I'm looking at code I know, such as reSIProcate, it is quite easy
to look at the stack, find the point where things went wrong, fix it and
craft a unit test to catch it in future on any platform.
When I'm in a stack trace from code I'm looking at for the first time,
it isn't always obvious what to look at. The first step is trying
to capture the relevant data and forward it to the developer who knows
that code.
This got me thinking: could there be a way for any user to:
a) automatically take a stack trace and
b) automatically recreate the same stack on x86 with the same packages,
input files, etc
c) identify relevant differences in the stack, objects in memory, etc
For (b), it might involve using qemu to recreate whatever they were
doing or it could leverage a nearby x86 host.
If something like this already exists, I would be interested in testing it.
Regards,
Daniel
3 years, 6 months