6 ms·
This is why Let's Encrypt is zero cost by the way. I'm certain Hanno knows that, but for everybody else: The purpose of ISRG (the not-for-profit which runs Let
by tialaramex 7y ago
This is why Let's Encrypt is zero cost by the way. I'm certain Hanno knows that, but for everybody else:
The purpose of ISRG (the not-for-profit which runs Let's Encrypt) is to drive automated issuance for Web PKI certificates. Nothing about this directly means they should be free - surely a not-for-profit could deliver this as an at-cost service, so why zero cost when that's not a core goal?
Machines don't have wallets. If they charge even 1¢ for a Let's Encrypt certificate (which would certainly cover costs at current issuance rates) now there needs to be a payment flow, which the machine needs help with because it doesn't have money. At zero cost all of that goes away and leaves you only solving engineering problems to achieve your goal of automated issuance.
- zamfi 7y ago> which the machine needs help with because it doesn't have money How long does it take to mine 1¢ worth of bitcoin? Or, is there anything else a machine can do in a relatively short timeframe that’s worth 1¢ to someone else? t2.micro instances on AWS rent for about 1¢/h...
- jodrellblank 7y agoLike what? If you have anything my computer can do to generate 1c/10seconds with no input from me, that’s $3.60/hour income running twenty four seven; I’ll buy a few and retire right now.
- chillwaves 7y agoComputers have costs associated with running them. electricity, infrastructure for them to run. The cost is not zero.
- sudosysgen 7y agoEven at the height of the crypto boom my computer with a very fast graphics card at the time made like ten bucks a day.
- criddell 7y agoIs it still generating money for you? Still $10 / day?
- sudosysgen 7y agoNope, not making enough to be worth the power drain and the noise anymore.
- rahimnathwani 7y agoLE certificates last 90 days. $3.60/hour is enough to cover renewal for almost a million certificates. The mining doesn't have to be done during the renewal process. You can do the mining gradually between renewals.
- wmf 7y agoThis kind of thing has been proposed but you can easily end up in a situation where the device uses 2c of electricity to mine 1c and then you'd be better off preloading the device with, say, ten years worth of currency instead of mining.
- konschubert 7y agoOn a CPU it’s gonna be dollars or electricity. The whole point of profitable mining is to build asics such that the cost of electricity gets lower than the mining rewards.
- wmf 7y ago21 was pitching IoT ASIC mining and it still looked like a waste of electricity.
- mdasen 7y agoI'm not a bitcoin person, but... I don't think you can mine $0.01 worth of bitcoin. Most of the time, you'll lose the race to find the correct hash collision and so you'll end up with nothing. Other times, you'll win and get the reward for the block which is 12.5 BTC at the moment (IIRC). People do join collectives to pool their mining power, but there isn't predictability to when the collective will end up with a coin. If you're looking to set up a web server, you don't want to be waiting days or weeks or whatever while your collective tries to win a block. Theoretically, you could buy a lot of computing power and always get unlucky. So you can't really get a penny of bitcoin via mining.
- konschubert 7y agoyou can join a mining pool. But mining once cent worth of bitcoin would cost you multiple dollars on a CPU.
- wmf 7y agoRealistically, larger pools mine multiple blocks per day and can pay out daily. 21 even came up with a scheme to front BTC to the device and make it up later, but that's excessively complex IMO.
- tlb 7y agoI wish there were a way of sending $0.01, by sending $10 with probability 0.001. That is, you and I negotiate a random seed (using something like Diffie-Hellman) and then we can generate probabilistic microtransactions and only transfer the $10 in the p=0.001 case. EDIT: fixed arithmetic, thanks skj
- nwienert 7y agoThis is smart! Why not build it?
- paulddraper 7y agoI suspect the probabilistic aspect would not actually be popular.
- tlb 7y agoYes, I think people would hate it for the same reason they love gambling slot machines. People overweight rare and random events. You'd always remember the one time you got dinged $10 for looking at some lame clickbait article.
- nwienert 7y agoYou wouldn’t need to sell it as random to the end user.
- paulddraper 7y agoThat's a good point.
- kfichter 7y agoI've always wondered whether probabilistic micropayments would fly under sharia-compliant finance.
- jonas21 7y ago
- badrabbit 7y agoI like how you said "WEB PKI". This works for the web, but the problem of verifying domain ownership for non-web interner remains. If ever there is a new version of DNS it should assume registrars will provide this CA service for free (or for whatever the domain costs)
- tialaramex 7y agoWeb PKI is just its name‡, like my name is tialaramex, names are not meanings. The Web PKI is a PKI for TLS services with names from the public Internet not just for HTTPS (the web). Names meaning mostly DNS names like news.ycombinator.com but also numeric names such as 1.1.1.1 The Baseline Requirements (the rules Certificate Authorities agreed to obey some years back now) currently provide 13 potential ways to verify domain ownership, but these ways are sometimes called the Ten Blessed Methods dating back to when Gervase Markham was alive and worked on the Web PKI. Although some of the Ten Blessed Methods are specific to the web in practice, such as 3.2.2.4.6 which involves creating a document to be retrieved from a web site, others really aren't such as 3.2.2.4.7 which is just a DNS change. Let's Encrypt offers both these (as challenges http-01 and dns-01 respectively) Method 3.2.2.4.12 is specifically for domain registrars in the sort of relationship you're talking about, and is used by some registrars which also have a CA business (such as Google) today I believe. ‡ It got this name because the Web is why this PKI exists. SSL was invented by the Netscape Corporation, whose Web browser is the ancestor of today's Firefox. Netscape's successor, the Mozilla Foundation and Mozilla Corporation continues to be the most visible and only public oversight for the Web PKI. Perhaps if instead some other group had secured the Network it would be named, say, the Usenet PKI, or the IRC PKI or the NetBSD PKI, but they didn't and it isn't.
- badrabbit 7y agoNames are not meanings but they describe a meaning. Webpki is framework used to verify public key ownership,specitically for TLS like you mentioned. What makes webpki unique (and correct me if I am wrong) is how responsibilities are separated such that domain ownership is established by a 3rd party (like ISRG) as opposed to by the domain registrar. Logically speaking, the party transfering or registering domain ownership (for a fee) would also issue you a certificate at the time of transfer/registration. The different approaches to verify ownership would not be needed if the more sane approach was taken to begin with. As you know, DNS is a protocol sepatate from TLS or other protocols. As such, domain ownership/control validation should be contained within the domain name system (also, why dnssec,dane and other efforts are under way, but they don't address the root cause of the problem). For method 3.2.2.4.12 (and thanks for informing me about this), my comment was that it should be mandatory (not optional) for registrars to issue DV certs. While I appreciate the ISRG, there are cases where using letsencrypt is not practical ,that aside, one org controlling so much of the web goes against the very concept of having TLDs that are independent in purpose/function. It would be more architecturally sane if what the ISRG does now was instead done at least at the TLR level. (E.g.: .com's owners should issue certs that says site.com belongs to whoever has this cert) For the impractical corner cases: let's say I need to run a non-web service like SMTP and I can't spin up a web server to validate the domain. Or let's say I need non-TLS x509 such as ipsec.