Nachrichtenagentur Radio Utopie is switching back to time zone MEZ resp. Coordinated Universal Time (UTC) +1 (Berlin time).
Archiv: Technik / Technology / Technics / Technology / World Wide Web / Internet
High Performance Battery: Redefining batteries
Welcome to a new basic technology.
Engineered to store energy in a safer and more sustainable way.
Ready to enter a new era?
The technology: A solar panel that produces hydrogen
Air contains moisture. The water molecules in the air are captured by the panel when the airstream enters the device.
Solhyd technology can be applied in many locations around the globe. Only the most arid places on Earth are expected to be too dry for hydrogen panels to work efficiently.
SmallTechnology Foundation: About
We’re Laura Kalbag and Aral Balkan (and Oskar the huskamute). We live and work in Bray, Ireland.
Since 2014, we’ve been advocating for regulation of surveillance capitalism, investment in ethical alternatives, and carrying out research and development on ethical alternatives.
After leaving the UK and moving to Ireland, we set up the Small Technology Foundation with the mission to evolve the Internet so each one of us can own and control our own place on it.
We strive to follow the principles of Small Technology in our work.
We don’t take money from surveillance capitalists and we exist thanks to the support of individuals like you.
What is the Small Web?
The Small Web is for people (not startups, enterprises, or governments). It is also made by people and small, independent organisations (not startups, enterprises, or governments).
On the Small Web, you (and only you) own and control your own home (or homes).
Small Web applications and sites are single tenant. That means that one server hosts one application that serves just one person: you. On the Small Web, we do not have the concept of “users”. When we refer to people, we call them people.
Another fundamental difference between the Big Web and Small Web is that on the Big Web we trust servers and distrust clients whereas on the Small Web, we distrust servers and trust clients. We treat servers as dumb delivery mechanisms. The client – under the control of the person who owns the site or app – is the only trusted environment.
SSL Report: unmissions.org (85.159.207.65)
TLS 1.3 No
TLS 1.2 Yes
TLS 1.1 Yes
TLS 1.0 Yes
> וודאו שיש לכם TLS 1.3 או TLS 1.2 תחת הסעיף Protocols. עדיף שלא יהיה לכם TLS 1.0\1.1 בכלל. מספר השרתים הפגיעים בישראל: 100,000+ לא פשוט לכתוב אייטם כזה לאנשים לא מקצועיים, אבל הוא חשוב והתפרסם ב @Haaretz
(10 Dec 2019)
אני מודה ל @noamr ו- @GilBahat על ה-peer review
UNBOUND
Unbound is a validating, recursive, caching DNS resolver. It is designed to be fast and lean and incorporates modern features based on open standards.
To help increase online privacy, Unbound supports DNS-over-TLS and DNS-over-HTTPS which allows clients to encrypt their communication. In addition, it supports various modern standards that limit the amount of data exchanged with authoritative servers. These standards do not only improve privacy but also help making the DNS more robust. The most important are Query Name Minimisation, the Aggressive Use of DNSSEC-Validated Cache and support for authority zones, which can be used to load a copy of the root zone.
The History of BIND
The Berkeley Internet Name Domain (BIND) package was originally written in the early 1980s at the University of California at Berkeley as a graduate-student project, under a grant from the US Defense Advanced Research Projects Administration (DARPA).
(…)
BIND 9: 2000 – Today
There have been more than 43 core developers who have contributed significantly to BIND 9 development and maintenance over its 20+ year lifespan.
(…)
In 2014, ISC ended development on BIND 10 and refocused on investing in BIND 9 instead.
DNS over TLS (DoT) auf FritzBox aktivieren
Zu guter Letzt können wir die Einstellungen noch prüfen. Bei der FritzBox sollte unter Internet -> Online-Monitor hinter den genutzten DNS-Servern jetzt (DoT verschlüsselt) stehen.
How to Change DNS Servers on Most Popular Routers
(Updated on March 12, 2022)
Change DNS Server on Linksys
Change DNS Server on a NetGear Router
Change DNS Server on D-Link
Change DNS Server on Asus
Change DNS Server on TP-Link
Change DNS Server on Cisco
Change DNS Server on TRENDnet
Change DNS Server on Belkin
Change DNS Server on Buffalo
Change DNS Server on Google Wifi
How to Change Your DNS on Any Device
(20.01.2024)
A Domain Name System (DNS) matches human-friendly domain names to computer-friendly IP addresses.
When you type in a domain name like cyberghost.com, for example, your web browser sends the request to your ISP via your router. Your ISP refers the request to its default DNS server. The DNS server then supplies the relevant IP address so your browser can load the appropriate page.
A DNS also saves a local copy or cache of sites you’ve recently visited on your device for quick and easy reference.
It seems like a streamlined service; what could go wrong? Check the following reasons why you should change your DNS.
Known DNS Providers
Here we suggest a list of trusted DNS providers.
Was ist DNS over TLS?
Bei DNS over TLS (DoT) handelt es sich um ein Protokoll zur verschlüsselten Übertragung von DNS-Anfragen (Domain Name System). Üblicherweise wird die Namensauflösung im Internet unverschlüsselt über UDP übertragen. Bei DoT erfolgt hingegen die Zuordnung von Domains und den dazugehörigen IP-Adressen verschlüsselt über das Transport-Layer-Security-Protokoll (TLS). Hierdurch ist die Übertragung vor Abhörversuchen, Manipulationen und Man-in-the-Middle-Angriffen geschützt.
The birth of the Web
On 30 April 1993, CERN put the World Wide Web software in the public domain. Later, CERN made a release available with an open licence, a more sure way to maximise its dissemination. These actions allowed the web to flourish.
The OpenDNSSEC project
OpenDNSSEC is a policy-based zone signer that automates the process of keeping track of DNSSEC keys and the signing of zones. The goal of the project is to make DNSSEC easy to deploy. The project is Open Source and intends to drive adoption of Domain Name System Security Extensions (DNSSEC) to further enhance Internet security.
DNSSEC History Project
DNS Security Prehistory
Few technologies are more critical to the operation of the Internet than the Domain Name System (DNS). The initial design of DNS did not take security into consideration, which was not unusual for protocols designed in the early 1980s. At the time of its development, and for many years there after, DNS had functioned without many formal security mechanisms, thereby making it vulnerable to DNS spoofing and other malicious attacks.
Determining the Need for DNSSEC
[What drove the work? Big picture issues. Surely this includes the demonstrations of cache poisoning by Steve Bellovin and Tsutomu Shimomura in the early 1990s and the similar work by Dan Kaminsky in 2008, but it may include much other activity.]
(…)
Cache Poisoning
The earliest known security problem with DNS was DNS cache poisoning, also sometimes called DNS spoofing. DNS cache poisoning happens when a DNS server downstream from the authoritative one returns incorrect data to queries for names or IP addresses. This occurs because an attacker has ‘poisoned’ the cache of the downstream DNS server to return the malicious response. DNS cache poisoning is a subset of a group of problems computer scientists often classify as cache invalidation.
This problem, known to the Computer Science Research Group(CSRG) at U.C. Berkeley since 1989, was finally described in a paper by Steve Bellovin in 1993. Bellovin initially put off publishing the paper out of fear the information would be exploited.
(…)
Concern over DNS cache poisoning, specifically that the leak would become publicly known, existed from 1989 to 1995.
Brief History of the Domain Name System
Jan. 7, 1958 – President Eisenhower requested funds to start ARPA.
(…)
– Early 1967 – Meeting of ARPA’s principal investigators in Ann Arbor, Michigan. Roberts (the director of the IPTO) put forward the idea of a computer network. Wes Clark introduced the idea of a subnetwork: small, identical computers all interconnected – “interface message processors (IMPs).” Engelbert volunteered to the Network Information Center (NIC).
– 1967 – Roberts published paper on ARPANET.
– End of 1967 – The Association for Computing Machinery’s computer conference in Gatliburg, Tennessee. Roberts presented his first paper on ARPANET and heard of work done by Donald Davies’ team at NPL and Paul Baran at RAND.
(…)
Summer 1975 – The Defense Communications Agency (DCA) took over the management of ARPANET.
(…)
– November 1983 – The rapid growth of the internet caused massive problems in bookkeeping. To deal with this problem a group including Jon Postel, Paul Mockapetris and Craig Partrige published RFC 882 which created the domain name system (DNS) to make Internet navigation easier. With DNS, users can type host names such as “USC-ISIF” instead of “10.2.0.52.” Every Address would have information from specific to general.
dnscheck.tools – inspect your dns resolvers
(…)
DNS: Was ist das Domain Name System?
(July 3, 2021)
Deswegen wurde 1983 der Informatiker Paul Mockapetris damit beauftragt, eine Lösung zu finden. Mockapetris verwarf alle bisherigen Ansätze und entwickelte sein eigenes System, das er auf den Namen “DNS” taufte. Auch wenn sich das Domain Name System seitdem deutlich verändert hat, funktioniert es in seinen Grundzügen immer noch so wie vor knapp vierzig Jahren.
inactive for 42 hours, work resumed.
Democracy first, technics last.
Whatever.
Privacy RSS Feed Readers
Privacy-focused RSS feed readers to help you stay up-to-date while preserving your privacy. Get the latest news and stories without compromising your personal information.
About: OpenDNSSEC was created as an open-source turn-key solution for DNSSEC. It secures zone data just before it is published in an authoritative name server.
Why DNSSEC?
Many internet protocol hinge on DNS, but the data in DNS caches has become so vulnerable to attack that it cannot be relied upon anymore. The added authenticity in DNSSEC makes sure that such attacks have no effect.
That is, if
– Zones are verified. Easy-to-deploy software for DNSSEC-aware name resolving (and caching) exists, for example Unbound or properly configured Bind9.
– Zones are secured. Easy-to-deploy solutions for DNSSEC did not yet exist, at least not in open source. Hence the OpenDNSSEC project.
More on the problems with DNS and about deploying DNSSEC can be found in this white paper.
UNBOUND
Unbound is a validating, recursive, caching DNS resolver. It is designed to be fast and lean and incorporates modern features based on open standards.
To help increase online privacy, Unbound supports DNS-over-TLS and DNS-over-HTTPS which allows clients to encrypt their communication. In addition, it supports various modern standards that limit the amount of data exchanged with authoritative servers. These standards do not only improve privacy but also help making the DNS more robust. The most important are Query Name Minimisation, the Aggressive Use of DNSSEC-Validated Cache and support for authority zones, which can be used to load a copy of the root zone.
Neuer Open-Source-DNS-Server: Unbound soll BIND Konkurrenz machen
(21 Mai 2008)
Eine Gruppe von Experten hat eine quelloffene Alternative zum DNS-Server (Domain Name System) „BIND“ vorgestellt, die leistungsfähiger und sicherer sein soll.
Der neue DNS-Server heißt “Unbound“, steht unter einer BSD-Lizenz und liegt jetzt in Version 1.0.0 vor. Die C-Implementierung wird von der nicht gewinnorientierten niederländischen Firma NL Labs gepflegt.
The History of BIND
The Berkeley Internet Name Domain (BIND) package was originally written in the early 1980s at the University of California at Berkeley as a graduate-student project, under a grant from the US Defense Advanced Research Projects Administration (DARPA).
(…)
BIND 9: 2000 – Today
There have been more than 43 core developers who have contributed significantly to BIND 9 development and maintenance over its 20+ year lifespan.
(…)
In 2014, ISC ended development on BIND 10 and refocused on investing in BIND 9 instead.
40 maps that explain the internet
(June 2, 2014)
The internet increasingly pervades our lives, delivering information to us no matter where we are. It takes a complex system of cables, servers, towers, and other infrastructure, developed over decades, to allow us to stay in touch with our friends and family so effortlessly. Here are 40 maps that will help you better understand the internet — where it came from, how it works, and how it‘s used by people around the world.
DNS over TLS (DoT) auf FritzBox aktivieren
Zu guter Letzt können wir die Einstellungen noch prüfen. Bei der FritzBox sollte unter Internet -> Online-Monitor hinter den genutzten DNS-Servern jetzt (DoT verschlüsselt) stehen.
How to Change DNS Servers on Most Popular Routers
(Updated on March 12, 2022)
Change DNS Server on Linksys
Change DNS Server on a NetGear Router
Change DNS Server on D-Link
Change DNS Server on Asus
Change DNS Server on TP-Link
Change DNS Server on Cisco
Change DNS Server on TRENDnet
Change DNS Server on Belkin
Change DNS Server on Buffalo
Change DNS Server on Google Wifi
Known DNS Providers
Here we suggest a list of trusted DNS providers.
Was ist DNS over TLS?
Bei DNS over TLS (DoT) handelt es sich um ein Protokoll zur verschlüsselten Übertragung von DNS-Anfragen (Domain Name System). Üblicherweise wird die Namensauflösung im Internet unverschlüsselt über UDP übertragen. Bei DoT erfolgt hingegen die Zuordnung von Domains und den dazugehörigen IP-Adressen verschlüsselt über das Transport-Layer-Security-Protokoll (TLS). Hierdurch ist die Übertragung vor Abhörversuchen, Manipulationen und Man-in-the-Middle-Angriffen geschützt.
How to Change Your DNS on Any Device
(20.01.2024)
A Domain Name System (DNS) matches human-friendly domain names to computer-friendly IP addresses.
When you type in a domain name like cyberghost.com, for example, your web browser sends the request to your ISP via your router. Your ISP refers the request to its default DNS server. The DNS server then supplies the relevant IP address so your browser can load the appropriate page.
A DNS also saves a local copy or cache of sites you’ve recently visited on your device for quick and easy reference.
It seems like a streamlined service; what could go wrong? Check the following reasons why you should change your DNS.
Public DNS Servers by country
Download valid nameservers as CSV | Plaintext
Download all nameservers as CSV | Plaintext
dnscheck.tools – inspect your dns resolvers
(…)
The birth of the Web
On 30 April 1993, CERN put the World Wide Web software in the public domain. Later, CERN made a release available with an open licence, a more sure way to maximise its dissemination. These actions allowed the web to flourish.
DNSSEC History Project
DNS Security Prehistory
Few technologies are more critical to the operation of the Internet than the Domain Name System (DNS). The initial design of DNS did not take security into consideration, which was not unusual for protocols designed in the early 1980s. At the time of its development, and for many years there after, DNS had functioned without many formal security mechanisms, thereby making it vulnerable to DNS spoofing and other malicious attacks.
Determining the Need for DNSSEC
[What drove the work? Big picture issues. Surely this includes the demonstrations of cache poisoning by Steve Bellovin and Tsutomu Shimomura in the early 1990s and the similar work by Dan Kaminsky in 2008, but it may include much other activity.]
(…)
Cache Poisoning
The earliest known security problem with DNS was DNS cache poisoning, also sometimes called DNS spoofing. DNS cache poisoning happens when a DNS server downstream from the authoritative one returns incorrect data to queries for names or IP addresses. This occurs because an attacker has ‘poisoned’ the cache of the downstream DNS server to return the malicious response. DNS cache poisoning is a subset of a group of problems computer scientists often classify as cache invalidation.
This problem, known to the Computer Science Research Group(CSRG) at U.C. Berkeley since 1989, was finally described in a paper by Steve Bellovin in 1993. Bellovin initially put off publishing the paper out of fear the information would be exploited.
(…)
Concern over DNS cache poisoning, specifically that the leak would become publicly known, existed from 1989 to 1995.
Brief History of the Domain Name System
Jan. 7, 1958 – President Eisenhower requested funds to start ARPA.
(…)
– Early 1967 – Meeting of ARPA’s principal investigators in Ann Arbor, Michigan. Roberts (the director of the IPTO) put forward the idea of a computer network. Wes Clark introduced the idea of a subnetwork: small, identical computers all interconnected – “interface message processors (IMPs).” Engelbert volunteered to the Network Information Center (NIC).
– 1967 – Roberts published paper on ARPANET.
– End of 1967 – The Association for Computing Machinery’s computer conference in Gatliburg, Tennessee. Roberts presented his first paper on ARPANET and heard of work done by Donald Davies’ team at NPL and Paul Baran at RAND.
(…)
Summer 1975 – The Defense Communications Agency (DCA) took over the management of ARPANET.
(…)
– November 1983 – The rapid growth of the internet caused massive problems in bookkeeping. To deal with this problem a group including Jon Postel, Paul Mockapetris and Craig Partrige published RFC 882 which created the domain name system (DNS) to make Internet navigation easier. With DNS, users can type host names such as “USC-ISIF” instead of “10.2.0.52.” Every Address would have information from specific to general.
DNS: Was ist das Domain Name System?
(July 3, 2021)
Deswegen wurde 1983 der Informatiker Paul Mockapetris damit beauftragt, eine Lösung zu finden. Mockapetris verwarf alle bisherigen Ansätze und entwickelte sein eigenes System, das er auf den Namen “DNS” taufte. Auch wenn sich das Domain Name System seitdem deutlich verändert hat, funktioniert es in seinen Grundzügen immer noch so wie vor knapp vierzig Jahren.
SSL Report: unifil.unmissions.org (85.159.200.174)
Protocols
TLS 1.3 No
TLS 1.2 Yes
TLS 1.1 Yes
TLS 1.0 Yes
(…)
Forward Secrecy With some browsers (more info)
(…)
Strict Transport Security (HSTS) Invalid Server provided more than one HSTS header
24 h pause for technical reasons, work resumed
Nachrichtenagentur Radio Utopie is active again.
Catching up with current events…
SSL Report: unmissions.org (85.159.207.65)
TLS 1.3 No
TLS 1.2 Yes
TLS 1.1 Yes
TLS 1.0 Yes
technical issue – problem fixed.
Due to the litte usual stuff (german tech) there was some kind of stop in our news update system.
The problem is fixed and the news agency is working.
SSL Report: unmissions.org (85.159.207.65)
TLS 1.3 No
TLS 1.2 Yes
TLS 1.1 Yes
TLS 1.0 Yes
www.wafa.ps
Verifying you are human. This may take a few seconds………………………………………..