WebSVN – oidplus – /trunk/res/OIDplus/privacy_documentation.html

<!DOCTYPE html>
<html lang="en">
<head>
<title>Procedural documentation related to privacy</title>
</head>
<body>
<style>
h2 {
font-size:large !important;
}
h3 {
font-size:medium !important;
}
</style>
<h1>Procedural documentation related to privacy</h1>
Revision: 20 August 2020
Important: This document is written by ViaThinkSoft (the developer of the software “OIDplus”) and gives general information on how OIDplus works regarding privacy-related topics. Since OIDplus is a web-software that can be downloaded, installed, and operated by anyone on their server systems, this document DOES NOT describe how the owners/administrators of this particular installation of OIDplus are handling your data. Therefore, the owner of this system should provide an additional/individual privacy statement.
<a name="terminology"></a><h2>Parties / Terminology</h2>
ViaThinkSoft is the developer of the software solution “OIDplus”.
OIDplus is a software solution to organize, manage and publish information about Object Identifiers (hereinafter referred to as OIDs) and their owners
(hereinafter referred to as Registration Authority or RA).
It can be downloaded and installed on any server. A particular installation of OIDplus is called OIDplus instance or OIDplus system.
Operators of OIDplus instances are usually software developers, workgroups, companies, or other organizations, hereinafter referred to as system owner.
A system administrator is a person who manages and maintains the OIDplus software and is usually also the same person who manages the server’s hardware and software.
Object Identifiers are organized in a hierarchical structure where RAs are delegating OIDs underneath the OIDs they are managing, to other RAs. In the context of a specific RA and OID, the “Superior RA” is the RA that has delegated the root OID of a specific RA. However, the statements about “Superior RAs” in this document do only apply if the Superior RA is using OIDplus to delegate the OID.
<a name="server_client_side"></a><h2>Definition of server-side and client-side</h2>
OIDplus is a web application written in the programming languages PHP (running on server-side) and HTML/JavaScript (running on the client-side).
<h3>Server-side</h3>
The PHP scripts of OIDplus are processed through a PHP script interpreter running on top of a web server software (“HTTP web server”), for example, “Apache” or “Nginx”. The actual data of OIDplus (OIDs, RAs, …) is stored in a DBMS (Database Management Software) e.g. “MySQL”, “MariaDB” or “PostgreSQL”. The DBMS is usually installed on the same server machine where PHP/Apache is installed, but it can be installed on any machine by the server administrator.
<h3>Client-side</h3>
While the user browses OIDplus, the server-side serves HTML and JavaScript contents to the client computer. Using a web browser software (like “Chrome” or “Firefox”), these contents are processed and displayed on the screen. Various JavaScript scripts are either required to run OIDplus or are improving the user experience, e.g. by reloading OID descriptions without reloading the whole page while the user browses OIDplus. There might be a few external JavaScripts included (Polyfill and ReCaptcha), which are described at the end of the document.
<a name="scope"></a><h2>Scope of this document</h2>
This document contains information about the OIDplus software only. It is independent of the behavior of the client-side software (web browser, Operating system, firewalls, …), independent from the behavior of hardware (network routers or firewalls, …), independent from the behavior of the server-side software (Apache, PHP, MySQL/MariaDB/PostgreSQL/..., Operating system, etc.) and the practices how the system administrator is operating the server software, stores log files, manages firewalls, etc.
<a name="oid_information"></a><h2>OID information</h2>
The main purpose of OIDplus is to show and manage information on OID information.
Some attributes of Object Identifiers (like ASN.1 identifiers) can only be changed by the Superior RA and not by the RA of that OID. On the other hand, some other information (like the title and description) can only be changed by the RA owning the OID and not by the Superior RA. The system administrator can edit all information.
<h3>Hidden OID information</h3>
A superior RA can set the “hidden” flag to an OID they delegate. This means the OID and all its subsequent OIDs are invisible to the public. However, the public can see the existence of hidden OIDs by a notice “XX OIDs are hidden. Log in to see them”.
The system administrator can see all OIDs, even if they are hidden.
An owner of an OID can see all OIDs which are directing to his root OID, even if some of them are hidden.
If you are an owner of an OID and want to make your OID hidden from the public, please contact your superior RA (preferential) or the system administrator and ask them to mark your OID as hidden. Please note that this will also hide all OIDs that you delegate to yourself or other RAs.
<h3>Overview: Managed information about OIDs:</h3>
<table border="1">
<tbody>
<tr>
<td width="111">
Attribute:
</td>
<td width="196">
Can only be changed by:
</td>
<td width="154">
If not marked “hidden“, visible to:
</td>
<td width="154">
If marked “hidden“, visible to:
</td>
</tr>
<tr>
<td width="111">
Numeric Identifier
</td>
<td width="196">
Superior RA System administrator (can only be defined during creation and never be updated!)
</td>
<td width="154">
Public RA Superior RA System administrator
</td>
<td width="154">
Superior RA System administrator
</td>
</tr>
<tr>
<td width="111">
Alphanumeric identifier (for ASN.1 notation)
</td>
<td width="196">
Superior RA System administrator
</td>
<td width="154">
Public RA Superior RA System administrator
</td>
<td width="154">
Superior RA System administrator
</td>
</tr>
<tr>
<td width="111">
Unicode label
(for IRI notation)
</td>
<td width="196">
Superior RA System administrator
</td>
<td width="154">
Public RA Superior RA System administrator
</td>
<td width="154">
Superior RA System administrator
</td>
</tr>
<tr>
<td width="111">
RA
</td>
<td width="196">
Superior RA System administrator
</td>
<td width="154">
Public RA Superior RA System administrator
</td>
<td width="154">
Superior RA System administrator
</td>
</tr>
<tr>
<td width="111">
Comment
</td>
<td width="196">
Superior RA System administrator
</td>
<td width="154">
Public RA Superior RA System administrator
</td>
<td width="154">
Superior RA System administrator
</td>
</tr>
<tr>
<td width="111">
“Hidden” flag
</td>
<td width="196">
Superior RA System administrator
</td>
<td width="154">
Public RA Superior RA System administrator
</td>
<td width="154">
Superior RA System administrator
</td>
</tr>
<tr>
<td width="111">
Title
</td>
<td width="196">
RA System administrator
</td>
<td width="154">
Public RA Superior RA System administrator
</td>
<td width="154">
Superior RA System administrator
</td>
</tr>
<tr>
<td width="111">
Description
</td>
<td width="196">
RA System administrator
</td>
<td width="154">
Public RA Superior RA System administrator
</td>
<td width="154">
Superior RA System administrator
</td>
</tr>
</tbody>
</table>
<a name="ra_information"></a><h2>RA information</h2>
The information about RAs owning OIDs can be seen publicly. A RA can manage their contact data in the OIDplus system (login-area) and mark their information as “private” to limit the information visible to the public.
Following RA information is always displayed (even if marked “private”):
<h3>Overview: Managed information about RAs:</h3>
<table border="1">
<tbody>
<tr>
<td width="111">
Attribute:
</td>
<td width="196">
Can only be changed by:
</td>
<td width="154">
If not marked “private“, visible to:
</td>
<td width="154">
If marked “private“, visible to:
</td>
</tr>
<tr>
<td width="111">
Email-Address
</td>
<td width="196">
RA
</td>
<td width="154">
Public Superior RA RA System administrator
</td>
<td width="154">
Public Superior RA RA System administrator
</td>
</tr>
<tr>
<td width="111">
Name
</td>
<td width="196">
RA
</td>
<td width="154">
Public Superior RA RA System administrator
</td>
<td width="154">
Public Superior RA RA System administrator
</td>
</tr>
<tr>
<td width="111">
Organization
</td>
<td width="196">
RA
</td>
<td width="154">
Public Superior RA RA System administrator
</td>
<td width="154">
Public Superior RA RA System administrator
</td>
</tr>
<tr>
<td width="111">
Office
</td>
<td width="196">
RA
</td>
<td width="154">
Public Superior RA RA System administrator
</td>
<td width="154">
Public Superior RA RA System administrator
</td>
</tr>
<tr>
<td width="111">
Personal name
</td>
<td width="196">
RA
</td>
<td width="154">
Public Superior RA RA System administrator
</td>
<td width="154">
Public Superior RA RA System administrator
</td>
</tr>
<tr>
<td width="111">
Privacy flag
</td>
<td width="196">
RA
</td>
<td width="154">
RA
System administrator
</td>
<td width="154">
RA
System administrator
</td>
</tr>
<tr>
<td width="111">
Street
</td>
<td width="196">
RA
</td>
<td width="154">
Public Superior RA RA System administrator
</td>
<td width="154">
RA
System administrator
</td>
</tr>
<tr>
<td width="111">
ZIP/Town
</td>
<td width="196">
RA
</td>
<td width="154">
Public Superior RA RA System administrator
</td>
<td width="154">
RA
System administrator
</td>
</tr>
<tr>
<td width="111">
Country
</td>
<td width="196">
RA
</td>
<td width="154">
Public Superior RA RA System administrator
</td>
<td width="154">
RA
System administrator
</td>
</tr>
<tr>
<td width="111">
Phone
</td>
<td width="196">
RA
</td>
<td width="154">
Public Superior RA RA System administrator
</td>
<td width="154">
RA
System administrator
</td>
</tr>
<tr>
<td width="111">
Mobile
</td>
<td width="196">
RA
</td>
<td width="154">
Public Superior RA RA System administrator
</td>
<td width="154">
RA
System administrator
</td>
</tr>
<tr>
<td width="111">
Fax
</td>
<td width="196">
RA
</td>
<td width="154">
Public Superior RA RA System administrator
</td>
<td width="154">
RA
System administrator
</td>
</tr>
</tbody>
</table>
<a name="ra_invitation"></a><h2>Invitation of RAs</h2>
When an OID is created by a RA or by the system administrator, the owner of the OID will be defined by an email address (which will be shown publicly). Therefore, it is possible to own an OID, even if you are not registered in the OIDplus system.
When the OID is created and the RA with such an email address does not exist, the creator will be asked if they want to send an invitation. If they agree, an email will be sent to this email address, allowing them to click a link to register to the OIDplus system, so that they can add more contact data as well as be able to delegate and edit OID information.
Currently, a RA cannot register themselves. They need an invitation by the system administrator or their superior RA to be able to register to the OIDplus system. (Note: To resend an invitation, the system administrator or superior RA needs to click “Update” at the OID delegation table, so that they are asked again to send the invitation).
In addition to the invitation system, the system administrator can create RA accounts without email address verification.
<a name="oidinfo_publishing"></a><h2>Publishing RAs/OIDs to oid-info.com</h2>
oid-info.com is a web page that collects and displays information about OIDs, like a Wiki. OIDplus contains features to submit data of its database to oid-info.com
There are two possibilities:
<ol>
<li>Manual transfer: The system administrator can create an XML file that contains OID and RA information (only the parts which can be seen by the public anyway) and can upload this XML file to oid-info.com</li>
<li>If the OIDplus system is registered to ViaThinkSoft and the OID-info.com transfer is enabled (see below), ViaThinkSoft will automatically fetch the XML data from the OIDplus system using an encrypted interface and submits the data to the oid-info.com administrator.</li>
</ol>
<a name="systemid"></a><h2>Unique system ID</h2>
During the initial setup, a public/private-key-pair will be created which can be used for various purposes, e.g. to encrypt data between OIDplus and ViaThinkSoft if the “system registration” service is used (see below) or to sign OID-over-WHOIS responses.
From this public key, a unique system ID will be derivated. The unique system ID and the public key can be seen in the setup screen.
<a name="system_registration"></a><h2>System registration and automatic publishing to oid-info.com</h2>
During initial setup, the system administrator can choose between the following options:
0       Register to directory service and automatically publish RA/OID data at oid-info.com 1       Only register to directory service 2       Hide system
This setting can always be changed in the administrator login/control panel.
<h3>Registering the system to the directory service (option 0 and 1)</h3>
The registration of your OIDplus system has various advantages:
<ul>
<li>The public key of your system will be published so that users can check the integrity of your data (e.g. signed OID-over-WHOIS requests).</li>
<li>Since the 31-bit System ID can have hash conflicts, ViaThinkSoft will make sure that the System ID is only used by your system (it will force other OIDplus systems with the same system ID to change their IDs).</li>
<li>ViaThinkSoft can acknowledge the system name, administrator email, and OID root arcs. Therefore, your system can be found using referral WHOIS.</li>
<li>You can optionally enable the automatic publishing of your public OID information to the repository oid-info.com.</li>
<li>Your OIDplus version will be reported to ViaThinkSoft. If a severe bug or security vulnerability is affecting your system, ViaThinkSoft can warn you via email.</li>
<li>The directory service will automatically create an X.509 security certificate for you (NOT an SSL certificate!) which can be used for various verifications.</li>
</ul>
If privacy level option 0 or 1 was chosen, the OIDplus system will regularly contact the ViaThinkSoft server through a secure connection and send the following information:
<ul>
<li>Privacy level (0, 1 or 2)</li>
<li>System ID</li>
<li>Public Key</li>
<li>Current URL</li>
<li>Administrator email address</li>
<li>System title</li>
<li>List of OID roots that this system is sending</li>
<li>The version of your system (SVN revision)</li>
<li>Installation type (ZIPed SVN snapshot or SVN working copy)</li>
</ul>
ViaThinkSoft will store this data internally and publish parts into the public directory service located at <a href="https://oidplus.viathinksoft.com/oidplus/?goto=oid%3A1.3.6.1.4.1.37476.30.9">https://oidplus.viathinksoft.com/oidplus/?goto=oid%3A1.3.6.1.4.1.37476.30.9</a> :
The public record contains:
<ul>
<li>System ID</li>
<li>Public key</li>
<li>Current URL</li>
</ul>
The other information will stay on the ViaThinkSoft internal database and will not be shared with other parties.
If the system administrator enabled this option and want to revoke the permission, the system administrator has to change the privacy level in the administrator login/control panel. The system will automatically contact the ViaThinkSoft server again and performs the deletion of all data.
Please note that the deletion of the record in the directory service does not delete OID/RA information which is already submitted at oid-info.com (if option 0 was chosen). To delete this data, the system administrator needs to contact the OID Repository Webmaster at <a href="mailto:admin@oid-info.com">admin@oid-info.com</a>
<h3>Publish RA/OID data at oid-info.com (option 0)</h3>
If privacy level option 0 is chosen, the system regularly contacts the ViaThinkSoft server through a secure connection and sends the public RA/OID data. ViaThinkSoft will store this data and redirect it to the OID Repository Webmaster who will review the data and eventually submit it to the public repository www.oid-info.com
If the system administrator enabled this option and want to revoke the permission, the system administrator has to change the privacy level in the administrator login/control panel to option 1 or 2 (to avoid that data is sent again). To remove already submitted OIDs, the system administrator needs to contact the OID Repository Webmaster at <a href="mailto:admin@oid-info.com">admin@oid-info.com</a>
<h3>Hide system (option 2)</h3>
If privacy level option 2 was chosen, the system will neither contact ViaThinkSoft, nor oid-info.com.
<a name="logfiles"></a><h2>Log files</h2>
<h3>Logs by OIDplus</h3>
OIDplus manages log entries for specific events like logins, OID/RA modifications, creating and deletion of OIDs, etc.
These log messages are stored in the DBMS only.
All log events are visible to the system administrator.
Some events are visible to the RA and/or the Superior RA.
Log events may show the IP addresses of the computer that was connected to the OIDplus system and the email address if the RA was logged in using their credentials.
OIDplus does not provide a function to delete log events. A deletion must be done in the database directly, e.g. using a database client like phpMyAdmin.
<h3>Logs by host software, firewalls, etc.</h3>
Besides logs created by OIDplus, other client-side or server-side software involved in processing the web requests (like the HTTP web server, the PHP script interpreter, the database server, the Operating System, the web browser, or various firewalls) might log traffic and queries in various ways. These logs are independent of OIDplus and need to be managed by the system administrator and/or network administrators.
If you are concerned about the contents of the log files, please contact the system administrator.
<a name="cookies"></a><h2>Cookies</h2>
OIDplus does only use cookies for the following purposes:
<table border="1">
<tbody>
<tr>
<td width="122">
Cookie
</td>
<td width="114">
Category
</td>
<td width="139">
Usage
</td>
<td width="118">
Will be created:
</td>
<td width="126">
Will be deleted:
</td>
</tr>
<tr>
<td width="122">
Login-Cookie
</td>
<td width="114">
Essential
</td>
<td width="139">
Contains a session key that is used to determine the user’s log-in-state and the permissions.
</td>
<td width="118">
During the login of a user or administrator using their password.
</td>
<td width="126">
When the user is logged out, and/or the browser session closed.
</td>
</tr>
<tr>
<td width="122">
SSL-Detect-Cookie
</td>
<td width="114">
Essential
</td>
<td width="139">
If the option “automatic SSL detection” is enabled by the system administrator, this cookie will check if the SSL port is open, to allow automatic redirection of HTTP to HTTPS.
</td>
<td width="118">
During the first page visit
</td>
<td width="126">
When the browser session is closed.
</td>
</tr>
<tr>
<td width="122">
Language Cookie
</td>
<td width="114">
Essential
</td>
<td width="139">
The language cookie contains the desired language.
</td>
<td width="118">
As soon as a flag is clicked, or if an URL was opened that has a <code>lang=...</code> argument
</td>
<td width="126">
When the browser session is closed.
</td>
</tr>
</tbody>
</table>
<a name="external_javascripts"></a><h2>External JavaScripts</h2>
During the loading of the web page, various JavaScripts are included to improve the user experience and add essential functionalities. The basic scripts are the JavaScript files of OIDplus itself, which are stored on the server of the particular OIDplus installation.
There are two JavaScripts which are loaded from an external source/server:
<h3>Polyfill (only if Internet Explorer is used)</h3>
To make OIDplus compatible with the web browser “Internet Explorer”, OIDplus will include a JavaScript script from “polyfill.io” which is a service by Financial Times.
Please see their <a href="https://polyfill.io/v3/privacy-policy/">Privacy Policy</a> and <a href="https://polyfill.io/v3/terms/">Terms of service</a> for more information.
The Polyfill JavaScript is only included if OIDplus detects that the web browser is Internet Explorer.
To disable the Polyfill feature, the system administrator needs to add the following line into the configuration file “userdata/baseconfig/config.inc.php” in the folder of the OIDplus installation.
<code>OIDplus::baseConfig()->setValue('DISABLE_MSIE_COMPAT', true);</code>
The adding of this line on server-side and/or the blocking of the JavaScript on the client-side will result in the page not working on “Internet Explorer” web browser.
<h3>ReCAPTCHA (only if “ReCAPTCHA” is enabled)</h3>
To protect sensitive functions of OIDplus (e.g. the login form) from hackers, the system administrator can enable “ReCAPTCHA” which is a service of Google. Before enabling ReCAPTCHA in the OIDplus setup/settings, the system administrator has to request an API key from Google. The usage of ReCAPTCHA will probably introduce additional cookies that are out of the control of OIDplus.
Please see <a href="https://policies.google.com/privacy">Google’s Privacy Policy</a> and <a href="https://policies.google.com/terms">Terms of service</a> for more information.
If the system administrator has not enabled the ReCAPTCHA feature, no external script will be included at all.
If the feature is enabled, blocking the ReCAPTCHA JavaScript on the client-side will result in various functionalities (like the login form) not working.
<a name="additional_security"></a><h2>Additional security / access controls</h2>
System administrators can choose other methods to disable access from the public, e.g. by using firewalls (so that clients cannot access the server at all) or by setting up password protection at the level of the HTTP web server software (e.g. “Basic Auth” on Apache, so that the clients cannot access the directory where OIDplus is installed in).
<a name="encrypted_connections"></a><h2>Encrypted network connections</h2>
The server administrator is responsible for securing the network connections using “HTTPS”. This is done at the HTTP web server level (i.e. an Apache module/setting) and independent from OIDplus.
</body>
</html>

Subversion Repositories oidplus

oidplus/trunk/res/OIDplus/privacy_documentation.html – Rev 360