DominoTree

I'm not particularly interested in this one but I have to say that my DM42 is brilliant in basically every respect and I really hope they continue innovating and making these.

He's saying that it doesn't make your SSH configuration or SSH itself any more secure.

But none of that would require anything near USB3 bandwidth, let alone across twenty ports.

One use case might be flight simulators with a bunch of different switch/indicator panels and controllers and things

Nothing here beyond wardialing for fax machines and sending them spam for a firm. I'd call it hacking if it involved identifying forward-facing management ports on the same printers.

Clever "abuse" of signal lines!

Seen people doing this exact thing for many years, the only difference each time is the content printed.

It's not pretty or nearly as useful, but towards the "end" of its life, the ST had native Ethernet and TCP/IP

Here's a picture of a native session running (on sdf.org)

https://pbs.twimg.com/media/DG0_h-eU0AEFy_7?format=jpg&name=...

I just found this on Wikipedia where he raised his bug bounty and at the same time cited these "unexploitable" bugs

https://en.wikipedia.org/wiki/Qmail#Security_reward_and_Geor...

Link to the GitHub repo:

https://github.com/nhorman/dropwatch

Would something similar be achievable using eBPF?

Serious question: Was there a legitimate reason they didn't patch this stuff when it was first discovered?

Hey everyone, please stop naming things Mir for a while. Thanks!

The solution is clearly to restore a full system backup from a time that it had fewer SQLite backups :P

KiCad's native autorouter was deprecated a while back (unless someone added it again in a recent point release)

I've had very good luck with this build of FreeRouting alongside KiCad https://freerouting.mihosoft.eu

I do a lot of small-batch hobbyist stuff and I've had really good results from PCBWay and JLCPCB - boards usually show up in about a week via DHL.

Never seen my IP show up anywhere but it's generally not very interesting to begin with :P

The intent is that you'll host their software somewhere on your network as a service, rather than running it from your laptop. They have cloud-based offerings or dedicated management hardware you can also use if you don't have a system to run UniFi on.

These are managed devices and you can't really approach them as you'd approach a traditional standalone AP or router.

I'd just like to interject for a moment...

Probably because they're both based on OpenSolaris

What's interesting to me is that if you use one of these fonts in an editor with Rust or another language they'll usually look quite like any other regular font without any fancy cursive or whatnot.

My assumption is that it's the editor's implementation, but I found it interesting that the use of these fonts (or at least, proper implementation thereof) seems to lean heavily towards Javascript.

Or am I missing something here?

(FWIW I'm a fan of italics for comments - here's what my setup looks like https://imgur.com/a/jTXHIo2)

I have well over 2,000 publicly-available cybersecurity talks on my Plex and I'm currently watching one right now.

I also have piracy.

I self-host a fairly big Plex and several personal websites along with a NextCloud instance to sync calendars/reminders/etc across devices. Pretty much everything forward-facing is behind CloudFlare.

On the front end I have two 1Gbit circuits (AT&T and Google) going into an OPNSense instance doing load-balancing and IPS running on a Dell R320 with a 12-thread Xeon and 24GB of RAM

Services are hosted on a Dell R520 with 48GB RAM and two 12-thread Xeons running Ubuntu and an up-to-date ZFS on Linux build.

Media storage handled by two Dell PowerVault 1200 SAS arrays.

Back-end is handled by a Cisco 5548UP and my whole apartment is plumbed for 10Gbit.

Couple things -

It's worth pointing out that AWS Elasticsearch is not simply the open distro - and a lot of things you see in the open distro are not currently available on AWS Elasticsearch. Beyond that, many features are simply forcibly disabled in Amazon's offering, just as many cluster settings and APIs are untouchable in the AWS service (even read-only ones that would be super helpful).

I still can't touch any of the rebalancing settings on my clusters and everything looks forcibly disabled. If rebalancing worked as expected, the whole blue-green thing shouldn't be necessary, and over time, I wouldn't generally end up with a single full data node while every other node in the cluster has 300GB free. Am I missing something?

None of the CloudWatch alarms you linked to have much relevance to the issues in the article (Other than the ClusterIndexWritesBlocked alarm which will only start firing after everything breaks). As of the last time I looked, you cannot monitor disk space on individual nodes in CloudWatch, only the cluster as a whole. Alerting on a single node starting to fill up is basically the one alert that would let me know things are about to be in a bad state.

Their service seems to work well for small implementations that use EBS-backed storage, and I bet that's what most of their customers are using, but I'm running 60+ node clusters and the problems only seem to be worse as capacity goes up.

Someone in the comments here mentioned they destroy and rebuild their cluster weekly just to keep the shards balanced. How ridiculous is it for that to be the best option offered?

Our experience was that the more data you store, the more IOPS you need to search through it at a reasonable pace, and with a large dataset things can really start to crawl.

That said, it's worth pointing out that EBS is the default data store in AWS Elasticsearch, and for people without a ton of data it might actually end up working "as intended"

Can I ask how large your clusters are and how many records you’re reindexing? I haven’t been able to scale this to a cluster taking in several TB a day

It exists in mainline Elasticsearch as well as the open fork and appears to exist in AWS's offering as well - AWS appears to have forcibly disabled it across the board for unknown reasons. I think it's probably an issue with the overall back-end architecture/implementation of their managed service.

Literally the reason AWK was created

Some support other varieties of RegEx, and some have interesting features or different interfaces

And let's not forget that there are non-standard "syslog" implementations that were being used for decades before RFC3164 happened. Cisco devices and AIX are the first two big ones that come to mind.

It's also worth mentioning that newlines are significant in TCP syslog (for batching log messages) but not in UDP syslog (because of frame size limits)