Unfortunately, a technical problem, currently not to be verified, has cost us three days.
Welcome to electronic colonialism.
Archiv: Technik / Techniker / Programmierer / technicians / technics / programmers
UncensoredDNS: About
UncensoredDNS was started in November 2009. At the time I was working at an ISP where one of my (reluctant) responsibilities was to administer the censored DNS servers that all Danish ISPs have to run for their customers. I have never been a fan of the Danish DNS censorship system, and working with it first hand didn‘t exactly help….
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.
SSL Report: pressenza.com (65.108.40.92)
Protocols
TLS 1.3 No
TLS 1.2 Yes
TLS 1.1 No
TLS 1.0 No
SSL Report: amerika21.de (193.96.188.217)
TLS 1.3 No
TLS 1.2 Yes*
TLS 1.1 No
TLS 1.0 No
SSL Report: telesurenglish.net (179.63.248.14)
Protocols
TLS 1.3 No
TLS 1.2 Yes*
TLS 1.1 Yes
TLS 1.0 Yes*
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.
SmallTechnology Foundation
Hello!
We’re a tiny and independent two-person not-for-profit based in Ireland.
We are building the Small Web.
No, it’s not web3, it’s web0.
Learn more about us.
> וודאו שיש לכם TLS 1.3 או TLS 1.2 תחת הסעיף Protocols. עדיף שלא יהיה לכם TLS 1.0\1.1 בכלל. מספר השרתים הפגיעים בישראל: 100,000+ לא פשוט לכתוב אייטם כזה לאנשים לא מקצועיים, אבל הוא חשוב והתפרסם ב @Haaretz
(10 Dec 2019)
אני מודה ל @noamr ו- @GilBahat על ה-peer review
The number of people with Top Secret clearance will shock you
(August 16, 2022)
The Director of National Intelligence publishes what is described as an annual report, “Security Clearance Determinations,” although the most recent one I could find was from 2017.
In it, more than 2.8 million people are described as having security clearance as of October 2017 – more than 1.6 million have access to either Confidential or Secret information and nearly 1.2 million are described as having access to Top Secret information.
Pentagon investigator admits to faking dozens of Top Secret security clearance background checks
(June 11, 2025)
Of 39 allegedly fraudulent investigations Nousheen Qureshi carried out over the course of more than a year for the Defense Counterintelligence Security Agency, at least a half-dozen included fabricated “interviews” with people who later said they had never even heard from her at all, according to a plea agreement obtained first by The Independent.
Trump administration plans to limit classified info it shares with Congress on Iran attack
The administration is planning to limit classified information it shares on CAPNET, the classified information sharing system used by both the House and Senate, the sources said.
It was not immediately clear how much information the administration plans to limit moving forward.
Will AI become God? That’s the wrong question.
(April 7. 2025)
I really want to emphasize, from a metaphysical point of view, I can’t prove, and neither can anyone else, that a computer is alive or not, or conscious or not, or whatever. All that stuff is always going to be a matter of faith. That’s just the way it is. But what I can say is that this emphasis on trying to make the models seem like they’re freestanding new entities does blind us to some ways we could make them better.
So does all the anxiety, including from serious people in the world of AI, about human extinction feel like religious hysteria to you?
What drives me crazy about this is that this is my world. I talk to the people who believe that stuff all the time, and increasingly, a lot of them believe that it would be good to wipe out people and that the AI future would be a better one, and that we should wear a disposable temporary container for the birth of AI. I hear that opinion quite a lot.
Wait, that’s a real opinion held by real people?
Many, many people. Just the other day I was at a lunch in Palo Alto and there were some young AI scientists there who were saying that they would never have a “bio baby” because as soon as you have a “bio baby,” you get the “mind virus” of the [biological] world.
Millions of Email Servers Exposed Due to Missing TLS Encryption
(January 8, 2025)
Top Affected Regions: The U.S. has nearly 900,000 exposed servers, followed by Germany (500,000+) and Poland (380,000+), highlighting the global scope of the issue.
Vulnerability Details: POP3 and IMAP protocols, commonly used for email access, are at risk when not secured with TLS, enabling eavesdropping and dictionary attacks.
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.
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.
Note to our readers: crawl limit active
For technical and security reasons, every reader resp. IP adress on our website is limited to 10 requests per minute. If this is exceeded, the IP address is blocked for one hour.
Drohnenprogramm-Whistleblowerin: „Wie ein Internet der höllischen Dinge“
Die Entscheidung wurde wahrscheinlich mit Hilfe von Daten getroffen, von denen einige aus sozialen Netzwerken und dem Internet stammen oder die von Datenmaklern verkauft wurden. Offensichtlich spiegeln viele der gesammelten Daten Vorurteile wieder.
Max Freitag: OpenAI, das Unternehmen hinter ChatGPT, arbeitet jetzt mit dem Militärdienstleister Anduril zusammen, um „defensive“ Drohnentechnologie zu entwickeln. Könnte es sein, dass ich eines Tages einen Chat-Bot nutze und meine Daten dazu verwendet werden, Algorithmen zu trainieren, die dann zum Töten von Menschen eingesetzt werden?
Lisa Ling: Sicherlich ist es möglich, sogar wahrscheinlich, dass alles, was von einem vernetzten Gerät an die Cloud gesendet wird, sei es eine Kredittransaktion oder eine Uber-Fahrt, letztendlich als Waffe eingesetzt werden könnte.
WELCOME TO NOSTR
To join Nostr you need a profile, but it is not the usual one that a company generates and manages for you. You create it yourself, no permissions are required.
Nostr is a different experience from the beginning: because there is no central authority taking care of who is who, each user is identified by a cryptographic keypair; don’t worry about the tech slang, it is just a strong password that you will have to keep safe.
This wizard is one of the many ways to bootstrap a Nostr profile that you can later use in other apps. We help you to create your keypair and safely manage it in a few steps. Are you ready?
What is Nostr? ELI5
The aim of ELI5 (explain me like I‘m 5) is to explain difficult things simply. This is urgently needed in our high-tech world, because only by understanding the technologies can we use them properly and develop them further.
I‘m starting my series with Nostr, a relatively new internet protocol.
Was ist Nostr? ELI5
Schwierige Dinge einfach zu erklären ist der Anspruch von ELI5 (explain me like I‘m 5). Das ist in unserer hoch technisierten Welt dringend erforderlich, denn nur mit dem Verständnis der Technologien können wir sie richtig einsetzen und weiter entwickeln.
Ich starte meine Serie mit Nostr, einem relativ neuen Internet-Protokoll.
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
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.
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.
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.
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
SSL Report: unmissions.org (85.159.207.65)
TLS 1.3 No
TLS 1.2 Yes
TLS 1.1 Yes
TLS 1.0 Yes