HN user
hn@sn.cm
Warning: The article is an empty shill for Saily. Prominently links to HowToGeek's 'review' of Saily with affiliate code: https://saily.sjv.io/LKDQrL or https://saily.sjv.io/c/156932/2044403/25536?svlink=11737998&... when resolved.
For what it's worth, Morse doesn't actually work via tapping (unless you add scraping as the dash component). Tapping makes no distinction between dots and dashes; what you intend as a dash is technically a dot and a pause.
There's a parallel code specifically for tapping, called "Tap Code" : https://en.wikipedia.org/wiki/Tap_code
Visible on Google maps: https://maps.app.goo.gl/MvPQhHgjkKMJpPws5
Full line boundary on maps: https://www.google.com/maps/d/u/0/viewer?hl=en&ie=UTF8&msa=0...
original NPR article: https://www.npr.org/2019/05/13/721551785/a-fishing-line-enci...
I visited the Burans in 2020. Decided to go in winter; figured the risk profile would be lower (security, extreme weather). It's definitely an effort to get to. Sadly one of the Burans was tagged after our visit. The hangar is just next to Gagarin's launchpad, which was fairly amazing to witness.
Photos for the curious.
Stripe is a payment gateway, not an anti-fraud solution. I'd recommend using services such as wyllo or Signifyd for anti-fraud. They will pre-filter against network intelligence signals, and if they approve the transaction, will guarantee your funds, even if a chargeback is lost, and even if you lose.
Alternatively, if your tropical or marine fish ever suffer from white-spot disease (actually a nasty protozoan), you use methylene blue to kill the parasite.
"Safe enough to swallow" seems like a scary oversimplification for alpha-emitting substances ?
Better alternative : https://github.com/justinribeiro/lite-youtube
And (at least) two in Paris. One mounted on stilts at CDG2, which depending on how you taxi you may or may not see from the plane, and one just outside ORY, which is maintained by an association, and visitable.
We did extensive research on the subject, there is no mystery. iOS will only read MIFARE tags with NDEF formatted data. If you write NDEF data to a formatted MIFARE card, it will be 'compatible' with iOS.
Otherwise, only the UID can be detected. The real mystery is why Apple refuses to open the low-level read commands. (To read NDEF, or determine that the data is _not_ NDEF, you need to read the card.)
Most modern amateur rigs are now SDR based. The big brands (YAESU, ICOM etc) seem to lean into SDR as QOL improvements (large bandwidth real time spectrum analysers to see what's going on across the whole band, Digital Noise Réduction that really works, etc), while preserving the heavily appreciated look and feel of a classic rig.
The Chinese SDR-based rigs have more unique interfaces, and there are many to choose from.
It's worth bearing in mind that most "Classic" desktop rigs output 100W, across 1MHz - 50MHz for HF - this needs to be supported by components that take up place.
Devices that operate at 10W are much smaller (and are typically chained with a larger indépendant amp..)
Adding our recent experience with Klaviyo. Klaviyo charges by "profile". When paired with Shopify, it automatically imports / pulls customer information 5o it's servers even when the customer specifically opted out of marketing.
First month, we were debited 3500EU for opted-out profiles that they had auto-pulled, against the consent of customers and us.
Even with the CEO looped in on emails, we had to threaten chargebacks before they refunded.
They also refused to remove data under our official GDPR request.
Taking into account the distances in Australia, I've never understood why the speed limit is so low.
Australia has an average "top speed" of 100km/h (110km/h in certain states) - whereas many other countries, with varying degrees of better or worse infrastructure, have average "top speed" of 130km/h - and yet have similar traffic fatalities.
Turkey: 130km/h (and fairly poor infrastructure compared to europe): 6.7 fatalities per 100k France: 130km/h (most people drive at ~145 on highways - only 1 point if you hit a radar) - 5 fatalities per 100k Australia: 100km/h - 4.5 fatalities per 100k
It can't just be speed, otherwise other 'similar' countries would be orders of magnitude above Australia.
Since a few updates ago, margins and pages are "limitless", so you can scroll a page (including PDFs) to the side to reveal a parallel page / much larger margin.
İncredible game, matched with an equally amazing soundtrack !
Newly minted HAM here. HamStudy is excellent, but / and works very, very well with these "No Nonsense" guides: https://www.kb6nu.com/study-guides/
They are excellent - they're built around the exam questions, but structured in a way that you understand the mechanics behind everything.
I'd attempted my license before, but never managed. After finding HamStudy + those guides, got my technician, general and extra class within 3 weeks.
73!
When I got French nationality, I spent 6 months growing an impressive old-style moustache just for the ID photo. it's the little things that count.
Check out the RFID Hacking Community discord: https://discord.com/invite/QfPvGFRQxH
Almost everything in the community happens here.
Because it's passively powered, "amplifying" isn't really possible, short of replacing the access control reader.
With that said, if your badge is in tag/fob format, you could clone it onto a card-format. Larger antenna, better coupling.
Closest thing to it is the "MagSpoof" device (originally made by Samy Kamkar) - which "emulates" a MagStripe track (Tracks 1/2/3) wirelessly.
There are a few suppliers building these devices. The bad uses outstrip the good uses.
There are multiple ways to crack MIFARE - depending on the actual chipset version / manufacturer.
For Mifare Classic: - Nested (Uses one known key to crack others) - darkside (Derives a key with no others. Slower, results are typically handed off to the nested attack to calculate remaining keys..)
For newer versions of the Mifare Classic with better PRNGs - "Hardened" cards: HardNested. Needs one known key.
For cards that provide a static nonce (to try to evade cracking, ie FUDAN) - Static Nested.
For the latest generation FUDAN: Static Encrypted HardNested.
Note, for the nested attacks - if you don't have a known key, these can be sniffed from the access control reader, and then cracked (MFKey32/64).
Flipper supports the MFKey32 attacks, and limited nested. You may bump into limits of your Proxmark clone with hardnested cracking - it's memory intensive, and most of the Proxmark Easy clones have reduced RAM.
There's actually an auto_crack LUA script on proxmark ( Use this fork: https://github.com/RfidResearchGroup/proxmark3 ) which will take most of the hassle out of cracking.
Cracking requires very, very precise timing: In a nutshell, you're trying to predict nonces / PRNG values, by sending very precicesly timed requests, and then later cracking those results.
The Flipper has limited CPU power - its main "attack vector" against MIFARE is a very large keylist / dictionary of common MIFARE keys. It's slow and dumb, but it works for most cases. It can also do limited cracking, depending on the type required.
The Proxmark is built around an FPGA, and can crack much, much more efficiently.
CEO of Lab401.com / Flipper Distributor / RFID geek.
One of the best resources is probably the Discord channels. There is the official channel, and the non-official (for non-official firmware). YMMV, but the non-official seems to be more active.
The Flipper is "somewhat underpowered" in terms of hardware for RFID, or specifically 13.56MHz, but makes up for it in a very active development community.
"Access badges" is a fairly vast blanket term. Anything that's not an exhaustive, lengthy breakdown will be inherently over-generalised, but here we go:
125KHz: Low Frequency: _usually_ cards with "just" an ID or very limited memory. _Usually_ much simpler technology. _Usually_ without security, and much easier to copy.
There are multiple encoding and modulation methods in this family, almost all of which are encompassed in a (fairly amazing) tag that can emulate them all - meaning they can be cloned easily : the T5577 chipset.
There's much more penetration of these chipsets in non-EU markets (US, Canada, etc). Key brands and tags: HID Prox, EM4XXX, Hitag, etc.
The FlipperZero handles most / if not all of these very well (read / save / emulate / write).
High-Frequency tags (13.56MHz) : encompasses multiple ISO Standards : 14443-A/B/C (lots of access cards), also ISO15693 (Slightly Longer read range, more industrial tags, ski-passes, etc), and EMV (Payment Cards) among others.
There are many sub-protocols and implementations of these higher level standards. But these can be generalised as : small memory units / computing units on a chip. As such : larger functionality, and various security.
The most well-known family is probably MIFARE (1K/4K Classic..). Chances are, if you've got one somewhere. Encryption is totally broken.
Ultralight / NTAG: Cheaper, no / not much security (password + signatures on some tags, and counters). Typically used for ticketing etc.
These are handled in Flipper.
Other implementations: DESFIRE: Uncracked. iCLASS (Commercial Access Control - iCLASS SE / ELITE / SEOS ..). Can be cloned, or suffer from downgrade attacks. Not handled by Flipper by default.
The Flipper has a fundamental 'flaw' with high-frequency tags: it can't handle emulation on chip, and its clock isn't evenly divisible by 13.56MHz, so emulation and some functions are always going to be limited. With that said, the 13.56MHz stack is always improving - the community has done amazing things.
Likewise, cracking (typically: MIFARE) is CPU / memory intensive. The Flipper can limp through some implementations, and can team up with a PC for others.
However, more specialised devices (Proxmark, iCopy-X) pick up where the Flipper leaves off.
In summary, it's a very useful tool for RFID (LF + HF) - can handle most LF operations, and quite a few HF operations - before you have to reach for much more expensive hardware (Proxmark : ~300 EU).
Some people to check out on YT: https://www.youtube.com/@TalkingSasquach https://www.youtube.com/watch?v=VF3xlAm_tdo
Feel free to reach out for more questions.
I appear to be in the minority where the RM2 is a perfect fit for my needs - but I can confirm that their support is aggressively anti-customer, and also non-compliant with EU consumer laws.
My device broke in warranty (< 1 year). Customer support refused replacements, finally offering a 2nd-hand / refurbished replacement (illegal according to EU law).
Despite my attempts at polite out-reach to individuals at the company, including C-level, everything was ignored until a lawyer friend sent a formal letter - and suddenly everything was magically resolved the next day.
It's such an expensive device, and each press-release makes it more and more cultish - I couldn't recommend buying this - I'll wait for a competitor to do a better job.
The remarkable2 is a highly opinionated device. Like most strongly opinionated people, if your needs / incentives / perspectives align, you'll get on perfectly. If not, you'll have a strong repulsion to the device.
They have an intentionally slow development cycle, which stays very true to Remarklable's interpretation on how to use the device.
I find that I align perfectly with the workflow imposed by the device (note-taking, PDF Markup, casual reading, specifically of magazines / PDFs).
I've tried other "kitchen-sink" android eInk devices (full-colour, etc) - and hated them for their confused approach.
However, the biggest reason to avoid remarkable are their anti-customer / flagrant disrespect for customer rights.
The lower-half of my device's screen began to malfunction, and eventually stopped working altogether. The EU has very clear laws on this situation: within the first year of purchase, the device must be replaced.
Remarkable initially refused to replace the device, eventually capitulated but sent a pen instead of the device, and then refused, once again, to replace the device. Bear in mind that I had sent my device to them.
Contact via the European Consumer Centres Network was ignored. I reached out politely to the CEO via email to ask for his attention to the situation. No reply.
Finally, when I initiated legal action against them, they proposed to replace the device with a "refurbished" device, and only when my lawyers insisted did I receive a new replacement device.
The craziest part is that I had purchased 6 devices for our team.
Our manufacturing (tool design, machining and production) is based in Guangdong, China. We have strong ties (15+ years working relationship) with the factory, which may have some pricing impact.
The tolerances on the high-run part are non-critical (but still need to match the other part for a seamless ultrasonic weld). It's got curved surfaces, and the surface texture was EDM'd on.
Likewise, not at all an expert - but have about 10 injection-moulded products under my belt; I just got back from China pricing out two new projects tooling projects. My email is in my profile if you ever want to reach out!
I'm curious about your pricing ranges - they seem to be vastly different to what I've experienced over the years (in both hard+soft molds for ABS injection).
Our 2-piece "high-run" tool, built out of tool-steel cranked out its 1M iteration a few months ago before we retired it. The tool cost 6k USD to produce.
Our 2-piece "low-run" tool, of a larger physical size cost ~10k USD to produce. ( For the curious - https://i.postimg.cc/MT8RT50P/tool.jpg )
These prices also included the model prep (IE, taking an STP of the final product, inserting the ribs, internal structures, closures, etc required to make a real product) and tool design (Modeling the tool itself gates, etc etc).
Perhaps it's the complexity involved, as injection-molding can scale from small parts to giant parts, but our pricing experience seems vastly different.
There are two different interfaces. One exposes the number + name + expiry over unencrypted ISO 14443 interface. Readable by any compatible reader (IE, every NFC enabled téléphone - https://www.apkmonk.com/app/com.github.devnied.emvnfccard/)
The EMV / payment interface is a different interface and fully encrypted.
The Flipper can read the PAN (card digits + expiry) that are exposed by cards that have "tap to pay".
This is an unencrypted interface supplied by the cards, which means it is readable by any NFC-enabled device (including any android device...)
This interface is different from the EMV (payment) interface, which is encrypted. The Flipper cannot clone EMV cards.
The problem here is that cards transmit their card info to anyone who asks, not that Flipper is a malicious device.
A few years ago, got an Ural motorbike and set off across a frozen lake Baikal to find the cabin of Sylvain Tesson, a French author that spent a full winter in the cabin.
http://travel.ninjito.com/images/2018-03-15-Siberia/qx-baika...
Inspired by the sheer beauty, I went back next year, found another abandoned fisherman's cabin and spent 2 weeks .. existing.
What is definitely true is that your days are very quickly filled with important tasks: skate 5km every other day to get water, trek across the forest to get wood, cut wood, maintain your fire, etc.
Completely astounding experience to be so isolated and independent in nature.