> With web browsers deprecating cleartext HTTP in favor of HTTPS, how long will this remain relevant?
Web browsers should and shall prefer HTTPS over HTTP. Have in mind that you don't know if the content served via HTTPS is secure or not. The protection that we get from HTTPS is that (hopefully) no one is listening to our communication between ourself and the server.
If you would like to have HTTPS for TOECDN you will be required to distribute our private key to every single person on this planet! And that is just for one web site. And if you are re-newing your certificate, distribute that once more to everybody. The reason for this is that every house hold around the world is allowed to run their own http cache server. That's why you can't use HTTPS with TOECDN.
If the web browsers had the capability to load for example a image file from a external host with the known checksum of that file, you can load that file from a HTTP host (read; over TOECDN) and you will know if the content match or not. If it does, well, treat it like you would if the content was served via HTTPS.
> The only reason I can think of is they don't want to lose control of distributing the application, which can be a big deal if you get a bad actor between you and the proxy or god forbid he takes over the proxy.
You can use this argument for Unix distribution which are using voluntary mirrors around the world. I do believe they work around this with the help of checksums, which they sign with a signature know to them within their software for updating the operating system.
> it's a "concept", which sounds like "not runnable software".
It is a concept! The required software to be able to run TOECDN is a authority dns server and a http cache server. My examples are with apache traffic server, which require no modification to their source code to be able to cache content with TOECDN.
For the authority dns server, my own fDns (https://github.com/fredan/fDns) has been developed with TOECDN in mind. Having sad that, other authority dns server(s) could be modified to be able to provide the required TOECDN functionality at dns level.
The Open Edge Content Distribution Network, TOECDN, has been developed for exactly this.
The whole purpose of TOECDN is that you, as a end user, can setup a cache server at your home, to be able to cache software updates like this. And its not just for software updates. Its for all static content.
That term is getting thrown around so much lately that it is obscuring the actual "someone just made this up without any regard to the facts, not because of errors, bad sources, or flawed methodologies but because of deliberately trying to pass off fiction as fact" fake news.
sought asylum in Russia in June 2013 after leaking volumes of information on American intelligence and surveillance operations to the media.
No he didn't seek asylum in Russia after he leaked volumes of information to media. He did seek asylum due to the fact that the US canceled he's passport.
Slashdot Mirror
slashdot needs to fix their html code for displaying polls. https://imgur.com/a/HnX1CYV
use mcedit from midnight commander instead.
> With web browsers deprecating cleartext HTTP in favor of HTTPS, how long will this remain relevant?
Web browsers should and shall prefer HTTPS over HTTP. Have in mind that you don't know if the content served via HTTPS is secure or not. The protection that we get from HTTPS is that (hopefully) no one is listening to our communication between ourself and the server.
If you would like to have HTTPS for TOECDN you will be required to distribute our private key to every single person on this planet! And that is just for one web site. And if you are re-newing your certificate, distribute that once more to everybody. The reason for this is that every house hold around the world is allowed to run their own http cache server. That's why you can't use HTTPS with TOECDN.
If the web browsers had the capability to load for example a image file from a external host with the known checksum of that file, you
can load that file from a HTTP host (read; over TOECDN) and you will know if the content match or not. If it does, well, treat it like you would if the content was served via HTTPS.
> The only reason I can think of is they don't want to lose control of distributing the application, which can be a big deal if you get a bad actor between you and the proxy or god forbid he takes over the proxy.
You can use this argument for Unix distribution which are using voluntary mirrors around the world. I do believe they work around this with the help of checksums, which they sign with a signature know to them within their software for updating the operating system.
> it's a "concept", which sounds like "not runnable software".
It is a concept! The required software to be able to run TOECDN is a authority dns server and a http cache server. My examples are with apache traffic server, which require no modification to their source code to be able to cache content with TOECDN.
For the authority dns server, my own fDns (https://github.com/fredan/fDns) has been developed with TOECDN in mind. Having sad that, other authority dns server(s) could be modified to be able to provide the required TOECDN functionality at dns level.
> Are you the dev? Also what happened to the toecdn.org site?
Yes I am. The site hasn't been updated since I've got no feedback for TOECDN. You can access the site at https://www.toecdn.org/
There is no site at http://www.toecdn.org/ if that was you were trying to use.
Right now I'm currently rewriting my authority dns server from scratch, which has the required functionality for TOECDN as Lua scripts.
These script can be found at https://github.com/fredan/fDns under lua/toecdn directory. However, I have not been updated that for almost a year now.
> why are their no unix/proxy/gateway solutions ?
The Open Edge Content Distribution Network, TOECDN, has been developed for exactly this.
The whole purpose of TOECDN is that you, as a end user, can setup a cache server at your home, to be able to cache software updates like this. And its not just for software updates. Its for all static content.
The thing is, nobody care about this solution.
Here's the link: http://www.oreilly.com/programming/free/files/open-source-in-brazil.pdf or http://www.oreilly.com/programming/free/files/open-source-in-brazil.mobi or http://www.oreilly.com/programming/free/files/open-source-in-brazil.epub
Source: https://gist.github.com/dotevo/66a3320598ac38a64072ec56f9633e8e
what the fuck has the inauguration to do with this?
All of them.
You usually call this Fox News.
none of what you provide in your reply to me is true.
No he didn't seek asylum in Russia after he leaked volumes of information to media. He did seek asylum due to the fact that the US canceled he's passport.
No we don't.
dear slashdot editors.
please don't link to apples site about iphone 7.
since I'm using 5G, bitches!
put your mail server on a aaaa record only and you will see so little spam that you can filter it manually.
My authority DNS server which I will release next week.
TOECDN would have fixed this shit already. We don't want less quality, we want more!
int passwordCompare(char* enteredPassword, size_t enteredPassword_len, char* validPassword, size_t* validPassword_len) {
if (enteredPassword_len != validPassword_len) {
return 0;
}
if (timeingsafe_memcmp(enteredPassword, validPassword, validPassword_len) == 0) {
return -1;
}
return 0;
}
I'm using C with LMDB. Think of it as Tinydns on steroids. With Lua.
That's why I'm writing my own. Nope, I'm not kidding. It's called fDns and will probably be the fastest authority DNS server there is.
Exhibit 1: https://s3.amazonaws.com/s3.documentcloud.org/documents/2179098/ag-mpaa-emails.pdf
TOECDN was made for this.
so how do I run my linux system with TAI instead of UTC?
'nough sad.