The Rabbit R1 uses a few custom APIs to talk to The Cloud™. Almost nothing happens on-device, and all the AI magic happens on servers.
Consequently, you don't really need the physical device.
In lieu of an authentication scheme, Rabbit's servers attempt to verify device authenticity by checking the TLS client's JA3 fingerprint, presumably enforced by AWS WAF.
If your TLS client doesn't match an expected fingerprint, you'll get HTTP 403 errors. This fingerprint works:
| XZ Backdoor symbol deobfuscation. Updated as i make progress |
WinMerge's Compare As > Disassemble IL Code and Disassemble Native Code options appear to be almost completely undocumented, so when I came across the error message Visual Studio not installed I wasn't able to find any relevant information online. I'm hoping this document will help anyone who runs into the same problem in the future.
If you don't care about the explanation, you should be able to solve the problem by opening the Visual Studio "Developer Command Prompt" and running this:
mkdir "%APPDATA%\WinMerge\Commands\ildasm" "%APPDATA%\WinMerge\Commands\dumpbin"
where.exe ildasm.exe >"%APPDATA%\WinMerge\Commands\ildasm\ildasm.txt"
where.exe dumpbin.exe >"%APPDATA%\WinMerge\Commands\dumpbin\dumpbinpath.txt"
This is a note on how I fixed a relatively minor issue with Microsoft SQL Server Express LocalDB. The solution was a bit difficult to find. Therefore I'm writing this in the hope that it will be found by other people who have the same problem and Google the error message text. This is based on a StackOverflow answer by Yennefer. I've added a bit more detail and an alternative way to delete the triggers. I'm leaving out most of my mistakes, several dead ends, etc.
I'm certainly no expert on anything in this document. I'm just sharing what worked for me.
When I opened Microsoft's Volume Activation Management Tool (VAMT) and tried to connect to my LocalDB instance as usual, I got this error:
There is a vulnerability/backdoor in webOS 5+ that allows you to easily run arbitrary commands as root during the boot process. The easiest way to exploit it simply involves putting a file on a USB drive and having it connected to your TV while it boots. There are two other methods that are more complex and require additional exploits.
| #!/bin/sh | |
| # by throwaway96 | |
| # licensed under AGPLv3+ | |
| # https://gist.github.com/throwaway96/bb31a17562eec4d8325020dee8c7e6b5 | |
| cert=/home/root/something.crt | |
| name=lol_hax | |
| file="${name}.pem" | |
| tmp="/tmp/tempcert.pem.${$}" |
This is a collection of a few of my smaller webOS scripts.
License: AGPL v3 or later
| #!/bin/sh | |
| # Directory to store overlays in (one directory structure is created per overlay configured down below) | |
| OVERLAY_BASE=/var/lib/webosbrew/customca | |
| overlay() { | |
| set -e | |
| overlay_id="$(echo $1 | sed 's;/;__;g')" | |
| unset TARGET SOURCE FSTYPE OPTIONS | |
| eval $(findmnt -P $1) |
| diff --git a/ext/ffi/ffi.c b/ext/ffi/ffi.c | |
| index 9be5ac3405..81ac091750 100644 | |
| --- a/ext/ffi/ffi.c | |
| +++ b/ext/ffi/ffi.c | |
| @@ -922,9 +922,11 @@ static void zend_ffi_callback_hash_dtor(zval *zv) /* {{{ */ | |
| } | |
| /* }}} */ | |
| -static void zend_ffi_callback_trampoline(ffi_cif* cif, void* ret, void** args, void* data) /* {{{ */ | |
| -{ |
The Host Diagnostics (HostDiag) screen shows various system information. It has been present on LG TVs since long before webOS. While it generally isn't very useful, it could come in handy in certain situations.
In general, to open HostDiag you must highlight "Channel Tuning" in the menu and press the "1" button 5 times. The menu can be opened with the menu button on the remote, but the steps after that vary a bit across webOS versions. Note that