lightning node information Show more
i've had to shut down all channels to my old lightning node due to a database inconsistency, if you want, you can connect to the new one:
Wow the FOSDEM room lineup looks pretty great this year: https://fosdem.org/2019/news/2018-10-14-accepted-developer-rooms/
Decentralized Internet and Privacy?
Microkernels and Component-based OS?
CAD and Open Hardware?
That's my kind of jam right there
Most modern search engines will not even /consider/ the possibility that I want what I asked for. Surely I misspoke. Surely those characters can't belong that that order, those words in the grammar, those ideas in that query. Wouldn't I like a nice cup of tea?
ASCII art to SVG, in an interactive editor. This is delightful. https://ivanceras.github.io/svgbob-editor/
although there are some instructions to get values into registers, and some to make jumps, that leaves no way
- to do a system call directly—needs 0x73 and 0x00
- to write a 'ecall' instruction on the stack to jump to
approaches that might work, are:
- if an existing offset of an ecall instruction is known it can jump there!
- in a similar way, if it knows the offset of a memory write+ret, it could use that
this goes into ROP territory, this means that it can never be self-contained :)
did anyone have a go yet at alphanumeric shellcode for #riscv?
it doesn't look very promising (no memory store instructions !):
TIL the hard way that the "char" type in the RISC-V C ABI is unsigned, like ARM, and not signed, like on Intel
so i spent today writing a piece laying out how to write terminal apps without ncurses (and, more importantly, how to write the library that will kill ncurses for good)
this is the result of years of experience delving into dark corners of ANSI specifications, terminfo files, and hoary manpages. this is knowledge that i’ve never seen collected in one place before. please use it, i beg you.
(though, in practice this is avoided by doing a relative load instead of using immediate encoding)
li a0, 0xcafebabe
gets assembled as
for a total of 16 bytes
one thing that slightly grates me about RISC-V is how it encodes intermediates and addresses split over multiple instructions
I understand why it is—simplicity of hardware implementation—but say,
ld t3,1888(t3) # 1d400 <strlen@GLIBC_2.27>
to jump to a (far) address takes some getting used to, and means relocations need to fix up at two locations
this is what I ended up with:
with these rules, udev will create symlinks under /dev/serial named after the device and the specific port when plugging it in
BUT it's quite difficult to even distinguish some devices, sometimes this can be done based on either product name or serial number, if the vendor was so helpful to set them
@orionwl yes, that is probably the best. We have the SYMLINK option in Trezor udev file exactly for this reason: https://github.com/trezor/trezor-common/blob/master/udev/51-trezor.rules
I suppose the most elegant way to handle this is to make udev aliases (using rules based on vendorID etc) instead of using /dev/ttyUSBx directly
PSA: yesterday, binaries were released for Bitcoin Core 0.14.3 and 0.15.2. These are backport releases that fix the CVE-2018-17144 consensus vulnerability. If you're running a vulnerable version but are not ready yet to upgrade to 0.16.3, these can be useful.
(from the recently open-sourced MS-DOS v2.0 source code)
the DOS programmers clearly didn't like some of the INT 21h system calls, AH=1Bh "Get allocation table information" they named SleazeFunc
just noticed how similar the RISC-V and Europol logos are
what kind of conspiracy is this 😂
TFW you type "git apply"—which waits for input—instead "git stash apply" and wonder, 5 minutes later, why it's taking so long to apply the changes
"Take me to your leader," the alien said.
"I have none," said the cat.
"Are you the leader?"
"Nah. Go bother some humans instead."
"But your kind is a higher life form than them!"
"So what makes you think you have the right to impose on me?" the cat said, and sauntered off.
#MicroFiction #TootFic #SmallStories
A private instance for discussion of:
(instance image by мøтħer ¢røω)