What if it was a binary file and you didn't have a program to read it ๐ฏ
blobjim
joined 5 years ago
How do you know it isn't going through tun0?
How do you know your VPN was "bypassed"? What was the symptom?
That's a pretty unique feature to Go I think. Maybe clang has something similar I guess?
Not that an attack like this is unique or anything.
Do you have "dnf" installed specifically? What layered packages do you have? I ran rpm -qa on my system and didn't find any packages containing "dnf"
Also not sure if it's useful but here's my ostree remote list --show-urls output:
fedora https://ostree.fedoraproject.org/
fedora-compose https://kojipkgs.fedoraproject.org/compose/ostree/repo/
I also always have the same issue trying to use the UI. I had to use rpm-ostree rebase for the upgrade to 41 and 42, but it worked for me with no issues.
Thanks for the additional info.
Just being supported as a protocol doesn't mean everything is done. Chromium probably didn't have it until years after that, and operating systems may not have implemented it umtil more recently.
Screen sharing infrastructure (for Wayland) in Linux was still in development recently. Maybe they just wanted to be able to use newer APIs?
Most of the lowercase abbreviations are just the names of device drivers or platforms. VK is just Vulkan, GL is OpenGL, ARB is "Architecture Review Board" as its sort of a preview or extension feature I think. EXT presumably for extension. KHR is Khronos, the organization that creates the Vulkan and OpenGL standards, and the acronym apparently means it's "Khronos-approved". https://registry.khronos.org/vulkan/specs/1.1-extensions/html/vkspec.html#extensions
I wish there was something nice like that too.
In the server world that would usually involve doing something like sending the journal data to Elasticsearch using an Elasticsearch integration. But that involves setting up an Elasticsearch server and Kibana and so on which is very unwieldy for a desktop computer. It does work pretty well though in terms of filtering. But it also stores the data internally in indexes to speed up search.
Of course journald has a seemingly simple C API but writing code is a lot of work. There are probably API bindings for various languages.
Searching for "tablet PC" or "Windows tablet" instead of just "tablet" will probably help in your search. Most computers with x86_64 CPUs (Intel or AMD) should be able to run Linux distros fine.
But tablets don't seem to be a common form factor for PCs. It seems like the term has really been narrowed down to mean one that runs Android or iOS. Very frustrating.
If you can't find anything that doesn't have an ARM SoC, you can try postmarketOS, but it will require more work and risk than a "PC" that is a tablet. https://wiki.postmarketos.org/wiki/Devices