Leading News

The leading news section is an important area of information on this website. It represents one of the two building blocks of information in conjunction with the latest news section. Available articles are listed below.
Wednesday, 15 June 2016
A previous version of this article initially appeared on »House of Hackers« in June 2008, posted by seconded agent A. Denton of directorate I: intelligence (ICT). Some aspects of it long remained significant for the organization's sectret day-to-day operations. On these grounds the article could not be declassified and published before.

In 2008 ED Denton used to work as an apprentice in the field of web engineering and security, when she was asked to assist GD Hollstein in an NGO web portal security audit. A subsequent report, which included a CoA along with a security and QA statement, had to be composed in due time. Step 1: System Lookup+Scans: The team first gathered target information, i.e. ISP and location, DNS records, OS and web/app server details. Further everything about the ISP's infrastructure itself, as well as information for later social engineering, was ascertained. To accomplish that, unixoid OSs and programs, i.e the 2007 BackTrack 3 GNU/Linux, next to publicly available database records from several authorities were employed. Of course every such software also required basic knowledge about ISO models, protocols, RFCs, networks and OSs to avoid potential hazards. Eventually the team discovered the targets were Gentoo GNU/Linux systems with kernel v2.4.22, hardened with grsecurity.
Last Updated (Wednesday, 15 March 2017)
Friday, 01 May 2015
The QUANTUM project was one of the most top-secret ventures of the NSA. During the last months several news agencies reported on that specific technology. Since ✛ΔO considers the project as one of NSA's most eminent threats to society until this day, the organization therefore published the present assessment along with an evaluation of countermeasures.

As Bruce Schneier wrote in his book »Data and Goliath«, the clandestine QUANTUM project was meant to be kept as secret as possible. In the meantime though various reports indicated that this project was not the only one of its kind, but that the Chinese government is in possession of a very capable »Great Firewall of China«, for a longer period of time already. Quite often authors confused that one with the »Great Cannon of China« which is a different system indeed. The article »Don’t Be Fodder for China’s ‘Great Cannon’« roughly outlined the inner workings of the »Great Firewall« and the »Great Cannon«. It showed that the firewall only prevents access to sites by either blocking or redirecting requests, while the cannon does more and actually injects packets into the stream. That is because to call forth a more complex desired behavior on the machine, where the initial request originated from. Therefore that cannon is more comparable to NSA projects like FOXACID.
Last Updated (Friday, 01 May 2015)
Thursday, 15 May 2014
In early April 2014 two independent IT security specialists from Codenomicon and Google Security discovered a flaw introduced into OpenSSL in December 2011. This article does not cover the happening itself, but focuses on common misunderstandings and wrong interpretations with regards to the catastrophe.

One common misinterpretation was that "Heartbleed", which is the way the flaw/bug was prematurely called, would only affect current versions of OpenSSL. However the truth is that older versions were affected as well – number 1.01 and 1.02 to be more precise. OpenSSL is a piece of software to encrypt traffic of connections on transport layer, which mostly affects TCP connections. The TCP/IP-stack is the dominant protocol-stack on the internet consisting of about 500+ different protocols. Since a lot of higher-level protocols, such as HTTP partially rely on encryption, TLS/SSL is employed on a regular basis to satisfy this constraint. For a disambiguation between TLS/SSL and SSH we suggest the article on Snailbook for reference. Basically OpenSSH is a protocol with several sub-protocols. (e.g. for multiplexing, password-based authentication, terminal management, etc.) which implements non-PKI authentication from S (session) to A (application) layer of the ISO:OSI model.
Last Updated (Wednesday, 01 April 2015)
Friday, 15 March 2013
After two years in the making, the organization released its new offline Web Content Management System, named »LXCMS«. That system is part of the organization's recent strategy to improve its overall system security, in the wake of increased world-wide threats to cyber as well as information security.

The new system is set to improve the situation in the area of content delivery, though Joomla! SE was our trusted wCMS software in operation for a long time. However the underlying Joomla! was always developed for the masses to fit their unspecific needs. Additionally Joomla! was always licensed under the GNU/GPL, unlike our new LXCMS which was put under our much simpler LTDL 2010. With Joomla! SE we could not have done the same thing for obvious legal reasons. Also Joomla may have been easy to install and upgrade, but was time-consuming to administer in later stages of use. The Joomla core itself was reliable indeed and so was the core of our wCMS Joomla! SE. Further developments though required our systems engineers to acquire a deeper knowledge of the software's code base. Unfortunately development was never optional but explicitly mandatory, since new features and security enhancements had to be ported back to our advantage and our security.
Last Updated (Wednesday, 01 April 2015)
Wednesday, 01 February 2012
During the last years Google's WebKit-based browser Chrome from the Chromium software project has become increasingly popular. This article focuses on the inherent security design of the user agent and its interaction with the underlying OS.

The Linux kernel used in (most unixoid operating systems) every single GNU/Linux distribution, including Chrome OS, inherits the traditional UNIX semantics which consists of two basic levels for process execution, file system object permissions and thus access restriction, namely "root" and "non-root". Thereby root processes are allowed to do nearly everything on the system, whereas non-root processes are limited in their executional behavior. Without architectural concepts like MAC (Mandatory Access Control) this is the way one has to run software on such an RBAC (Role Based Access Control) based system. That seems to be a simple solution to most use-cases regarding process execution and object access restriction, but it also means that any given program which requires a high level of privileges (root privileges) must be made root. That can ether be achieved by direct execution with root privileges or e.g. by execution as a different user using Dennis Ritchie's SUID mechanism.
Last Updated (Wednesday, 01 February 2012)
 
 
FreeBSD
 

DOCUMENT TIME

  2017-11-20  ☀  16:00 UTC

CYBER THREATCON

  ✛ΔO CYBER THREATCON: Level BETA

SECURITY MODULE

  ᐅ REQUESTOR / YOU
  ᐊ 1&1 INTR. AG  CDN

POLL / VOTE

Should ✛ΔO engage more in counter-intelligence?
⚫ Yes, there is a need for such operations.
⚫ No, because it may be very dangerous.

BOOKMARK

Press Cmd or Ctrl + D
Press Cmd or Ctrl + D

STATISTICS

  Visitors: 642.250+ ℮

CAMPAIGNS

  25 Years of Linux

TECHNOLOGY BASE

COAT OF ARMS

  Code Of Arms: Frankfurt

OPERATING STATUS

  Facility: open and operating
 
©  2003 - 2017   TRON-DELTA.ORG  (NGO)   –   Nongovernmental  Intelligence  Organization
Portal v5.05.143 R 2 on ✛ΔO LXCMS v1.1