sation. This means that # the standard Auth/DBMAuth methods can be used for access control. The # user name is the `one line' version of the client's X.509 certificate. # Note that no password is obtained from the user. Every entry in the user # file needs this password: `xxj31ZMTZzkVA'. # o ExportCertData: # This exports two additional environment variables: SSL_CLIENT_CERT and # SSL_SERVER_CERT. These contain the PEM-encoded certificates of the # server (always existing) and the client (only existing when client # authentication is used). This can be used to import the certificates # into CGI scripts. # o StdEnvVars: # This exports the standard SSL/TLS related `SSL_*' environment variables. # Per default this exportation is switched off for performance reasons, # because the extraction step is an expensive operation and is usually # useless for serving static content. So one usually enables the # exportation for CGI and SSI requests only. # o OptRenegotiate: # This enables optimized SSL connection renegotiation handling when SSL # directives are used in per-directory context. #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire SSLOptions +StdEnvVars SSLOptions +StdEnvVars # SSL Protocol Adjustments: # The safe and default but still SSL/TLS standard compliant shutdown # approach is that mod_ssl sends the close notify alert but doesn't wait for # the close notify alert from client. When you need a different shutdown # approach you can use one of the following variables: # o ssl-unclean-shutdown: # This forces an unclean shutdown when the connection is closed, i.e. no # SSL close notify alert is send or allowed to received. This violates # the SSL/TLS standard but is needed for some brain-dead browsers. Use # this when you receive I/O errors because of the standard approach where # mod_ssl sends the close notify alert. # o ssl-accurate-shutdown: # This forces an accurate shutdown when the connection is closed, i.e. a # SSL close notify alert is send and mod_ssl waits for the close notify # alert of the client. This is 100% SSL/TLS standard compliant, but in # practice often causes hanging connections with brain-dead browsers. Use # this only for browsers where you know that their SSL implementation # works correctly. # Notice: Most problems of broken clients are also related to the HTTP # keep-alive facility, so you usually additionally want to disable # keep-alive for those clients, too. Use variable "nokeepalive" for this. # Similarly, one has to force some clients to use HTTP/1.0 to workaround # their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and # "force-response-1.0" for this. # BrowserMatch "MSIE [2-6]" \ # nokeepalive ssl-unclean-shutdown \ # downgrade-1.0 force-response-1.0 Include /etc/letsencrypt/options-ssl-apache.conf SSLCertificateFile /etc/letsencrypt/live/odcspace.com/fullchain.pem SSLCertificateKeyFile /etc/letsencrypt/live/odcspace.com/privkey.pem # Mod_security SecRuleEngine DetectionOnly # vim: syntax=apache ts=4 sw=4 sts=4 sr noet # NameVirtualHost *:80 ServerName www.odcspace.com ServerName www.odcspace.com ServerAlias odcspace.com Redirect permanent / https://www.odcspace.com/ # Mod_security AllowOverride All ServerAdmin webmaster@localhost ServerName www.odcspace.com ServerAlias odcspace.com Protocols h2 http/1.1 DocumentRoot /var/www/html # Setup some redirects from the time being Redirect 307 /contact / Redirect 307 /services / Redirect 307 /data-handling / Redirect 307 /operations / Redirect 307 /communications / # Available loglevels: trace8, ..., trace1, debug, info, notice, warn, # error, crit, alert, emerg. # It is also possible to configure the loglevel for particul About Us – ODC Space

ABOUT US

OUR

Mission

Improve software development and operations performance using concepts leading to automation and opportunity-based planning, increase data analysis productivity and leverage resources by removing unnecessary repetitive tasks.

OUR

Vision

Creativity requires time and human interactions, and in most cases, these aspects are limited due to the excessive amount of repetitive tasks that need to be carried out by developers and operators. We believe that automation is key to improve performance and advance in science and technology.

OUR

History

ODC Space is small company founded in 2015 with the goal of providing consulting services for NAIF’s SPICE toolkit users and other SMEs requiring know-how on Space Payload Operations and Ground Systems. Over time, we have also moved into automatic software conversion and web development, always focusing on SPICE and Space Systems Engineering.

Our Team

Jorge Diaz del Rio

CEO and Lead Senior Engineer