fullspectrumdev

Maybe hole punching or similar might be worth examining?

One of the more fun things to note is bad actors don’t need to be a telecoms operator or pay one for access to SS7 - a lot of the software involved for management is horribly insecure and often exposed to the internet by smaller operators.

The biggest barrier to entry for hacking SS7 networks is just gaining the network access. And that gate is often secured with some shoddily written mess of old code.

The underlying Reticulum network this uses is really quite interesting given how many transport media it offers (packet radio, etc).

A lot of these data brokers hold wildly inaccurate information.

Now you gotta tell us more about the meteor scatter trick :)

Spam filtering for SMS is still not particularly broadly implemented by network operators apparently.

I remember during Covid there was a few startups in that space trying to work with MVNO’s to get a foothold in the market, but don’t think any of that went anywhere.

“Launch codes” was a mostly US thing.

In the UK it was famously a cheap lock.

In the USSR, physical control of warheads was supposed to be under the KGB according to some sources.

The ticket splitting thing you refer in the UK to works in other countries also.

> 280 9.0+ vulnerabilities in seventy thousand plugins, the long tail of which have maybe dozens of activations at most.

This actually is a great point. A few years ago when working on a code analysis tool, we mirrored every single WP plugin and let it chew on them for a while.

It used a mixture of static and dynamic analysis, and “kinda worked” to some extent.

It found more issues than we could reasonably handle, and a lot of them were in plugins with maybe two installs ever and that hadn’t been activated in years.

We ran out of beans before implementing a proper triage system that would score the findings based on popularity or “last updated” data.

I may revisit this sometime though, as my ideas on static and dynamic analysis have come a long way since then!

You are doing a great job of simply parroting Russian propaganda points here.

Even the recon drones have a fairly short lifespan due to EW.

This has given me some wonderful ideas for my next attempts at hot sauce.

I wonder if I could get a nice flavour profile from using some smoked/toasted (dried) peppers and some untreated ones in a fermentation? Would there be a nice flavour combination of the Smokey and Tangy aspects that I enjoy?

My last efforts at growing my own chilli’s were going extremely well until I went away for a month, forgot to leave instructions for their care, and they died off beyond recovery.

There’s a lot of work that has been done on address space reduction for IPv6 scanning. It’s not “impossible”, it’s just very very hard :)

Not had time to read through the docs properly, but would this work for CLI apps (Node compiled to an executable?) or similar?

The problems this solves look interesting for a few CLI tools I want to build :)

In my experience the decisions on any non trivial IT system rollout are made by entirely unqualified, non technical execs who are usually swayed by marketing such as clownstrikes Super Bowl advertisement.

Technical people will make a recommendation, knowing it’s going to be ignored and that the decisions already been made.

I have the exact same issue with OpenSSH on an absurdly regular basis, which is why I maintain a set of statically compiled versions and VM’s with old versions - just so I can actually talk to old appliances/hardware.

I noticed also that some of the security scanning tools we use “silent fail” on some old appliances because they can no longer negotiate the appropriate SSH connection due to library updates :)

I was speaking in the more general case with regards OpenSSL - not NPN specific: where changes in OpenSSL have caused stupid devices that I have no control over to become “unmanageable”, hence having to either build static tools or use an ancient VM.

I wish I could replace these old devices, and I recommend to do so, but usually replacing them won’t happen until they physically break.

Think: Industrial IoT devices at client sites and other such security horrors.

Why it’s not removed: backward compatibility I bet.

I have to maintain a few VM’s and statically linked tools specifically for interacting with old network appliances that modern Linux hosts won’t “talk to” without crippling their SSL/TLS configuration or doing other horrendous workarounds like specific OpenSSL/OpenSSH config files for those things.

It’s actually an interesting problem when performing security assessments - some tools for scanning will have false negatives because they can’t “talk to” old shit.

I was always told that CFD is not a substitute for “actually going and testing”.

It will get you a fair amount of the way there, but at some point you have to go and actually do the thing to validate your model.

I’d love to have some solid numbers of “global cancellations due to” - I heard a bunch of varying figures so far.

HAM while playing by the rules is pretty much “not that”, due to ban on encryption and such.

Doesn’t help that the HAM community will more than happily snitch on you if you goof around too much, and licences mean your full dox are publicly searchable (at least in America).

As a mushroom enjoyer, I now know exactly what I’m going to be searching for when I am next in Poland (soon).

A blank will still do a shitload of damage up close. Not as much as a live round, but depending on how you are carrying it’s gonna mess you up.

Many striker (or internal hammer) fired pistols are basically “single action only” and when you have a choice of “condition one” or “condition three”.

For example: Glock. You either are carrying in condition one, or condition three.

I’ve not handled or even seen one of these Sig’s yet, so I can’t really comment on them specifically.

Kind of, you can use the CF CDN to grab an external IP by using any CF site.

Example: https://www.fullspectrum.dev/a-less-suspect-way-to-get-exter...

Most of the countries along that coastline (where you would dock, the other side is like Libya) have rather strict laws about the keeping of firearms, which makes shooting somewhat less likely.

Even if it’s sitting in the background under a spoofed process name, it can be caught with memory dumps.

Memory dumps are obnoxiously useful for detecting stealthy malware, especially if you do the memory dumps from the hypervisor instead of from the VM itself.

The hard part is parsing :)

Endpoint is an incredibly crowded market, difficult to break into unless you really have a solid USP.

In the past I’ve used a blog literally to make small notes on very simple things that I always ended up having to look up, or for notes on the “right way” to do something.

For example: for years I was using Pythons requests library incorrectly. The way I was doing it worked - but it wasn’t correct.

Once I published a short blog on the correct way - the correct way seemed to stick better in my mind!

I’ve had this fear a few times - and when my last workplace started getting a bit weird (layoffs) I largely stopped publishing much of anything. I experimented with publishing under an alternate identity a bit, but it never stuck.

Now I’m working through my backlog of drafts, dumping a load of stuff ASAP, and then trying to commit myself to some form of publishing schedule to force myself to “catch up” on the project backlog.