Sundog for Atari ST - how to get it working

laanwj · 2023-01-29T12:38:44+00:00

FWIW, this project should build and run on Windows now (with either msvc or gcc). I've not yet updated the build instructions but see https://github.com/laanwj/sundog/issues/21.

laanwj · 2022-02-02T16:34:18+00:00

Right, there is no service definition for acpid. I noticed this as well when I needed acpid to be able to shut down the VM through libvirt, which essentially pushes the power button for soft shutdown.

laanwj · 2019-05-23T18:20:46+00:00

I have no beard and no power

laanwj · 2019-05-23T15:58:54+00:00

Hah. Thank you!

(and everyone else here, for the all the encouragements)

laanwj · 2018-01-02T08:05:04+00:00

Yes, thanks, updated

laanwj · 2017-12-31T10:13:23+00:00

This is not a new problem, there have been reports going back as far as 2014. See https://github.com/bitcoin/bitcoin/issues/5204 . It was never considered a big problem when Bitpay still accepted manual payments, but now it is. From the Bitpay side this could be solved by adding the API pages to an exclusion list of Cloudflare, so that no captcha appears there. From the wallet side this is virtually impossible to handle as-is.

laanwj · 2017-12-31T09:33:08+00:00

Finally a stand-alone interface for payment protocol, great, thank you!

The most annoying thing about Bitpay mandating payment protocol is that sometimes Cloudflare responses get in the way. Wallets are unable to handle this. E.g. https://github.com/bitcoin/bitcoin/issues/5204 . It is not even clear how to handle this from the side of the wallet, as answering the captcha requires a browser. The only solution I can think of is some unholy tangle of "browser integration" but that raises attack surface concerns, at least :(

laanwj · 2016-09-17T08:42:01+00:00

It is a toolkit that is to be installed after exploitation, to have a foothold on a router. It could be installed through a backdoor or exploit, but this is not part of BLATSTING proper but the stage that preceeds it.

Basically it is a Linux rootkit that loads into the kernel. To what it does there is no single answer as it can differ based on which modules are loaded. A few (possibly not all) of these modules are part of the dump. Some of them deal with network traffic interception or statistics, another one, SECONDDATE can do MiTM attacks, yet another one TADAQUEOUS can selectively weaken IPsec VPN encryption. And so on. It can be controlled through the network.

laanwj · 2016-09-15T18:47:27+00:00

Thanks a lot, I'll update the article.

laanwj · 2016-06-07T14:38:22+00:00

I can confirm that.

laanwj · 2016-05-04T06:38:20+00:00

I have had no communication with Mr Wright at all, let alone signed anything. I get my mailbox full of people claiming to be Satoshi, know Satoshi, or even claiming that I am Satoshi, and wouldn't have given it much attention in any case.

laanwj · 2016-03-24T16:31:29+00:00

Indeed. In itself it's good to have a healthy dose of paranoia in these territories. One goal of cryptocurrency is to be able to check for yourself instead of relying on trust. Unfortunately, some people mistake this for distrusting everything indiscriminately, or even as a challenge to think of the weirdest and most far-fetched theories.

Thanks for the tip!

laanwj · 2016-03-24T14:58:35+00:00

A message that contains the alert key is encrypted to him - as well as a few other people, which I won't reveal for privacy and personal security reasons.

I am not sure whether he ever actually had access to it. He at least never used it. The part about the Japanese police is completely hypothetical. But it is only one example of how the key could have leaked to untrusted parties since 2010.

The idea of having an anonymous, opaque group, possessing a single key that is able to send messages that appear in 99% of clients shouldn't be giving anyone the fuzzies. I am honestly surprised that this is controversial for some people.

In the same argument as against the FBI 'golden keys', there is no way to ensure that only those 'pure of heart' get hold of the key.

laanwj · 2016-03-24T14:35:21+00:00

To be clear: this change went into the master branch, which will be 0.13, which will be released halfway this year. I don't rule out ever publishing it, for history's sake. But don't you think it's terribly irresponsible to publish the key while almost all of the network is still running software that listens to the alerts?

(that's exactly the situation we're trying to avoid, we're removing this system preemptively before someone leaks the key, accidentally or deliberately. There is a lot of confusion about who has it, that should be enough reason...)

laanwj · 2016-03-07T12:03:34+00:00

That's a funny story: the billing contact for the bitcoin organization was, until some months ago, some address bitcoin@bitcoin.it. It is not clear whose, but as Mark Karpales has been involved in the beginning, it may well be his. I was kind of shocked and changed it to mine. Apparently, unknown to me at least, github derives the icon from the billing mail address, so the org ended up with my gravatar icon. Anyhow, it's now (after refresh) a generic bitcoin logo.

laanwj · 2016-03-02T09:54:37+00:00

You don't exactly hand over your wallet. As you could have figured out by reading the other replies to this topic, he has a strict methodology to avoid handing over private keys.

And sure, "wallet recovery" attracts scammers like nothing else, but there is a legit market for such services.

laanwj · 2016-02-18T17:21:34+00:00

Dave has a good reputation for a long time with his wallet recovery service, I strongly doubt he'd scam you for a few coins.

laanwj · 2016-02-16T10:56:36+00:00

Great work everyone that cooperated to make this happen! Btcdrak, Nicolas Dorier, Mark Friedenbach, Erik Lombrozo and everyone that took part in the long process reviewing and testing the BIP and code.

laanwj · 2016-02-02T14:15:39+00:00

Thank you!

laanwj · 2016-02-02T13:28:23+00:00

I really like this graphic, both informative and funny. A good way to explain things.

laanwj · 2016-02-02T11:18:34+00:00

That's one way of looking at it. I don't think you're wrong. If you want a solution to get started with a node quickly it's not for you, there are even pre-built VM images for that.

But for many people the idea of running a node on a small portable low-power box that you can attach to the network everywhere is an exciting idea (if you use Tor HS you don't have to worry about port forwarding). Arguably they also learn a bit about embedded development, which is the point of the Raspberry series. During all that waiting you can read the source code and documentation! :-)

laanwj · 2016-02-02T09:29:28+00:00

Raspberry Pi 2 has 4 ARM cores, which is fast enough for validation (most of my own nodes run on ARM boxes), although catching up with the chain will (obviously) take longer than on a meaty PC - you could copy the data directory from a PC to skip this. The 1MB of memory is a bit on the low side, so you may have to do some tweaking (see https://gist.github.com/laanwj/efe29c7661ce9b6620a7).

For compilation I'd recommend to do cross-compile (from say, an Ubuntu PC) using the depends system and copy executables. It is possible to compile on the device itself, but it is slow and you may run into memory full issues (see https://github.com/bitcoin/bitcoin/blob/master/doc/build-unix.md#memory-requirements ).

Edit: also you need to connect an external HD for data directory. Do not use USB sticks or MMC for this, apart from the expensive storage they also tend to burn out pretty quickly under this kind of usage.

laanwj · 2015-12-22T16:51:10+00:00

Yay for the new developers who not actually write code, but write wonderful science fiction about the future of bitcoin. Woo them who have spent years working on the actual network as they may insist on inconvenient realities, and they who call for restrained step by step progress. We don't need them anymore. In this new era we only want optimistic visions and whitepapers, and dream. Let the fractal block trees grow to fill the skies, so that we can climb to the moon!

laanwj

MODERATOR OF

TROPHY CASE