I've just read an item on "The Register" about a network connected high
performance oscilloscope... with no security. That's as in Zero, None, Keine.
That might not seem a big deal, except that this sort of kit tends to reside in
research labs, so evilCorp (tm) could snoop on what a competitor is working on,
and pretty quickly work out not only what it is, but how well it's performing.
Said evilCorp could then plant some nasty that casually looks around to see
what other kit is on the network. Presumably this also potentially opens a door
to sabotage.
Anyway, that got me thinking (yes I know)
Has anyone thought of connecting an AD converter to a Raspberry Pi to make a
high resolution, but comparatively low bandwidth oscilloscope for audio work?
Say 16bit 500k. I'm thinking it could possibly be connected via I2C or SPI,
both of which are supported on the Pi...
or even {cough} ethernet {cough}
BTW I'm not talking about connecting to bitscope - that only has 8bit resolution
and the module itself has no gain control and is easily overloaded :(
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
Hey all,
some of you (e.g. users of free.fr [1]) are currently seeing problems
with the LAD/LAU mailing lists. It seems to be triggered by those mail
servers still trying to negotiate handshakes using obsolete and unsafe
SSLv3 ciphers.
Several of you might have received an unsubscription notice from the
mailing list. Please note, that this is not done out of malice, but
because after several connection drops, mailman will automatically kick
subscribers off the list - which is usually good for non-existing
mail hosts or mail addresses.
However, in this particular instance I think it is due to us not
allowing those SSLv3 ciphers anymore (most mail providers actually
don't) and have not done so since the beginning of the year
(configuration-wise nothing has changed significantly in quite some time
either, which is even more pointing in an outwards direction).
The only solution to this - to my opinion - is to fix your mail server
setup (if you operate your own mail server) or ask your mail provider to
fix theirs (if you are using someone else's services).
You can validate the functionality of your TLS setup [2] before and/or
afterwards.
If both are non-viable options for you, I suggest switching to a mail
provider, that has a more well-maintained and configured mail server
setup (as we're able to deliver to other mail providers just fine).
Best,
David
[1] https://ssl-tools.net/mailservers/free.fr
[2] https://ssl-tools.net/mailservers/
--
https://sleepmap.de
Hi all.
On Tuesday the 12th of December it's again the meeting at c-base.
Since I posted on both LAU and LAD, let's have the follow-up discussion
on LAU.
Cheers
/Daniel
