It's switching components every 8 seconds, like a carousel. It's a bit unfair to judge Rails UI by that, but I agree, it's not a good first impression.
635 karma · joined March 23, 2015
Use cases: Signal processing applications with strict latency requirements Audience: RAN system engineers, signal processing specialists, AI researchers Built with: DOCA, DPDK, TensorRT, Python, JAX, PyTorch, C++, CUDA, and more
So it‘s not part of what Tailscale brings, it just adds another layer of indirection between the SSO / IdP you have already and the app, plus requires some custom library integration work, further enhancing lock-in.
This is due to flaws in its design as shown here:
From a quick glance it looks like it‘s using static NodeIDs derived from the Bluetooth MAC address in the always unencrypted Packet Header.
So not only can you sniff these messages from far away at greatly simplified complexity when comparing to cellular communication, but also tie it to the hardware that you carry with you.
Mesh networks sure have its uses, but I‘d be wary of their offered privacy in the presence of adversaries you could be facing at protests!
Still, what‘s also possible is to use PTP as backup (e.g., over eCPRI) and use the fiber / microwave backhaul to some master clock with, say, a ribidium time source as a backup, so I think it‘s not entirely unreasonable to assume that cell phone signals will remain available in the presence of a GPS outage.
> On a spectrum of model architectures, it achieves higher compression efficiency at the cost of model complexity. Indeed, the full LivePortrait model has 130m parameters compared to DCVC’s 20 million. While that’s tiny compared to LLMs, it currently requires an Nvidia RTX 4090 to run it in real time (in addition to parameters, a large culprit is using expensive warping operations). That means deploying to edge runtimes such as Apple Neural Engine is still quite a ways ahead.
It’s very cool that this is possible, but the compression use case is indeed .. a bit far fetched. A insanely large model requiring the most expensive consumer GPU to run on both ends and at the same time being limited in bandwidth so much (22kbps) is a _very_ limited scenario.
> The problem is, there were no empty seats on the flight. So when he emerged from the lavatory and the plane began taxiing, flight attendants realized something was wrong, and the plane returned to the gate.
Maybe this would suit you?
https://www.jetbrains.com/help/idea/code-inspection.html#acc...
In my research, I developed a technique to attack a phone with low power from km away, without being able to be detected at all with traditional tools like SeaGlass or Crocodile Hunter. It‘s published here and works against production LTE networks, no downgrade attacks whatsoever necessary:
Check this thing out, it‘s a programmable audio DSP:
It‘s a misleading title for sure.
Do you have those numbers as well?
https://ohwr.org/projects/white-rabbit/wiki/switch
There's also commercial vendors of those exact switches: https://creotech.pl/product/white-rabbit-switch-wrs/
Isn‘t automatically checking out and opening a repository after clicking a link quite a risky affair? Does it bypass the „do you trust this repo“ screen put up by VSCode?
In fact, this is in practice the only range limitation of the system - wherever the downlink could be decoded, the attack worked.
In the paper you can see that the attack over 3.8km worked with an omnidirectional antenna and required only very little output power.
We use overshadowing, in particular on the uplink, to create a new set of attacks that turn a legitimate base station into an attacker’s asset.
With AdaptOver, an attacker doesn’t use a fake base station. This marks a new attack paradigm that has to be taken into account when developing and evaluating countermeasures or new protocols.
Happy to answer any questions!
When writing for group projects, we use Overleaf [2]. Its Git feature also makes it possible to write locally in TeXstudio and then push the changes to Overleaf.
Is there a technical protocol description somewhere? I‘d be interested in reading this.
I‘d like to be able to choose one of the servers in the rack to access and not buy & manage one of these devices for every server.
I‘m interested to see if Radio Sentinel could/will detect the new improved version! Would you be willing to provide us with a test version/device?
Would the approach be able to detect an AdaptOver/LTrack style attack?