fullspectrumdev

This puts an awful lot of stock in the robustness of eBPF.

Which is odd, given there’s been a bunch of kernel privesc bugs using eBPF…

I come across them every so often! Usually stuff that just hasn’t been replaced yet because “it works fine” like most other legacy kit :)

This isn’t Britain or Wales. RoI is not part of the UK.

Just wait til you hear about the rules for gold prospecting in Ireland.

TL;DR finds of over 2 grams have to be given to the state (you might get it back).

Shooting is more popular than you would think in Ireland, but people tend to keep quiet about it.

Because this kids writing code a lot better than many professional programmers.

I’ve still not seen any actual proper evidence of Andruils tech being fielded in Ukraine, and I’m in touch with a rather large number of people on drone and EW teams over there.

It’s become kind of a joke of sorts - we see slick promo stuff for Luckeys shit in the press, but we never see the goods.

The countries allowing CC are - unfortunately - in the minority in Europe.

Among the ones that do allow CC, most of them that’s a special permit that seems to have an exception to the storage requirements for personal protection.

Personally I wish more of Europe would emulate the Czech Republic in this matter…

In most European countries you have to store the firearm in a locked safe, often with the bolt removed or the weapon disassembled and - quite often - with the ammunition stored separately in another locked container/safe.

It’s a lot more “steps to take” to commit suicide than “take the weapon from your nightstand and shoot yourself”, given you have to unlock usually more than one safe/lockbox.

RFPolicy was well intentioned but in no way was ever a standard the community at large adhered to in my experience.

> Standard practice is to inform the vendor early and work with them as you write the article

This isn’t even remotely standard practice.

A fair number of people and companies will give the vendor a chance by doing coordinated disclosures this way - but it’s in no way standard practice.

Also when a company has a history of being openly hostile to disclosure attempts and downplaying stuff, the only way to force improvement tends to be “short warning, or even full disclosure”.

I’ve done everything from coordinated to “no warning” disclosures in my career, and at this point I tend to lean more towards “no warning” in situations where a vendor has a history of dismissing concerns or openly being hostile to external researchers.

You can apply for a permit - you usually only will get one for a specific area if you are an archaeologist associated with a university or a museum or something apparently.

The law is intended specifically to prevent random people digging up stuff and causing damage to historic sites.

So using them for searching for cables/pipes or lost items is “allowed, sort of” - you can readily buy metal detectors in Ireland for these purposes.

Prospecting for gold, on the other hand, is a legally thorny subject in Ireland. Finds above a couple of grams have to be reported and handed in.

If you happen to “stumble across” historical artefacts on your land you are meant to stop doing whatever caused you to find them (eg construction), report it, and then wait forever while archaeologists eventually show up and spend ages poring over the find to ensure you don’t destroy anything of historic value.

It was oddly popular where I lived during the 1990’s/2000’s for a while - largely due to a lot of marketing pushing it as healthier than butter.

I’m not sure exactly when that “turned back around”, but I think it was the 2010’s - now butter is the default and margarine is seen as rubbish.

This is the method that I’ve found works best for me - each project has a repo, and when I’m working on a specific “thing” I open an issue.

There’s usually a lot more issue comments than commits as I just add a comment to the issue while I “work it out”.

New problem? New issue.

New insight on that problem? Comment.

And so on…

The economics of bug bounties from a “bug hunters” perspective are quite interesting! I’m going to give the short version.

There are public (such as the one being discussed here) and private programs.

To gain access to private programs you have to be invited to participate - you get an invite usually based on reputation for providing good reports on public programs.

Platforms like H1 and BugCrowd act as intermediaries for this, with reputation scores, etc.

It should also be noted here that if you rediscover a bug someone else reported, you don’t usually get paid.

With public BBP/VRP, you are competing against everyone in the space against a relatively limited subset of targets. The way to “win” is to either “go deep” against high payout targets, expending a lot of effort in the hopes of avoiding a duplicate finding, or to invest heavily in automation, or some combination of the above.

With private programs you are competing against many less people and have a higher probability of payout for time/effort expended.

The guys who tend to make a shitload of money off BBP/VRP either are focused solely on a handful of high payout targets, or have invested heavily in automation to grind public programs, gain invites to private ones, and repeat.

A lot of the better offerings in the “continuous vuln scanning” or “attack surface monitoring” market are from people who have been “full time” bounty hunters for a while, built out significant automation platforms, and pivoted to offering it as SaaS products to enterprise for detection of issues.

There’s a lot more to it, but it’s probably worth a blog post at some point tbh.

In my own experience, as someone who has participated in bug bounties and vuln disclosure programmes in my free time for about a decade now, I usually land a couple of nice payouts per year and a lot of issues reported without payment.

I know of a few people whose relatively high traffic sites domains expired for whatever reason, and the sites reappeared under new owners with some of the content recreated from archive but now with a shitload of ads.

I’m curious why there’s no mention in the article of Joe Barnard’s efforts at bps.space which are “prior art” in this problem domain (landing a model rocket using TVC).

Usually: it’s left open to unfuck DNS.

Some of them will try force you to use their local resolver, but often UDP will be left open (or left open on port 53) because it is easier.

When they force a local resolver you can often tunnel over DNS requests, though this only works sometimes :)

Years ago I ran a “public” iodine service - anyone could connect, outbound traffic from the server went over Tor (to protect me from abuse requests).

I kept a log of all train/hotel/airport/etc networks that it worked on, and also offered some other tunneling protocols.

Was a fun project for a while. Wish I’d kept the thing running.

These days DNS tunnelling is a bit harder to do due to some DNS servers (notably Google) randomising the case in DNS requests which breaks certain encodings horribly.

I got a very similar word salad response from another data broker type company ages back.

I should try again.

Usually refers to “evading bot detection”.

Detecting when blocked and switching proxy/“browser fingerprint”.

> Somewhere in the HP hierarchy reality is removed.

This has been the case for well over a decade at least by now, unfortunately :(

Even without kittens, house cats will often take a captured small animal inside (still alive) and dump it near their caretaker and expect them to finish the job.

Our cat has only access to a confined (extremely high walls) garden (largely left to grow wild for environmental reasons) due to proximity to a road where people drive extremely badly, and still manages to occasionally succeed at bringing something in, usually dumping it at someone’s feet and going “ok you do it”.

I ended up switching to Fastmail after it being recommended here ages back, and it’s been fantastic.

I’ve also used Google Workspace, O365 or whatever MS calls it this week, and Proton as well as self hosting mail in the past.

While I’d love to agree: many people these days simply don’t want to use IRC.

Age limit is unchanged. You can only serve between ages of 18 and 60.

There’s a few anomalies where old dudes are sticking around voluntarily.

Also worth noting that a lot of the videos posted claiming to be “people being drafted” are actually videos of the police just arresting criminals…

Modern combat helmets don’t leave a “gap” between head and helmet, the “gap” is filled with padding to absorb impact/shock and improve comfort.

I’ve written a few toy port knocking implementations, and doing it right is hard.

If your connections crap and there’s packet loss, some of the sequence may be lost.

Avoiding replay attacks is another whole problem - you want the sequence to change based on a shared secret and time or something similar (eg: TOTP to agree the sequence).

Then you have to consider things like NAT…

There’s a Rust library that implements most of the protocol, but I’ve not found a “drop in replacement” using said library yet.

Might actually make for a fun side project to build a SSH server using that library and see how well it performs.