Jak hluboce vyčistit svůj PS4 Slim

Byl jsem na tom testován bitvou a nepodařilo se mi dosáhnout mého cíle, kterým je odepřít veškerý přístup do všech adresářů kromě veřejného adresáře a povolit přístup pouze do všech ostatních adresářů se specifickými adresami IP.

Chcete-li nainstalovat Railo + Apache + Tomcat, docela jsem se řídil tímto skriptem: https://github.com/talltroym/Railo-Ubuntu-Installer-Script poté ověřil nastavení pomocí tohoto tutoriálu: http://blog.nictunney.com/2012 /03/railo-tomcat-and-apache-on-amazon-ec2.html

Z instalačního skriptu jsou povoleny tyto mody:

sudo a2enmod ssl sudo a2enmod proxy sudo a2enmod proxy_http sudo a2enmod rewrite sudo a2ensite default-ssl 

Mimo skript jsem zkopíroval weby - k dispozici webům - a poté znovu načetl Apache.

Mám adresář vytvořený pro Railo cmfl umístěný na / var / www / Railo / Navigace v prohlížeči na http: // Server_IP_Address / Railo vynutí ssl a přemístí se na https: // Server_IP_Address / Railo, který ukazuje index.cfm. Neposkytování index.cfm a vynechání https znamená, že direktiva DirectoryIndex a RewriteCond of Apache zřejmě fungují pro VirtualHost s povoleným webem.

Problém, se kterým se setkávám, je, že nemohu odepřít přístup ke všem adresářům kromě Public. Moje adresářová struktura je poměrně jednoduchá a vypadá takto:

  • Railo
    • chyba
    • Veřejnost
    • Neveřejné
    • Pískoviště

Toto jsou moje konfigurace podporující weby:

 ServerAdmin [email protected] DocumentRoot /var/www #Default Deny All to prevent walking backwards in file system Alias /Railo/ '/var/www/Railo/'  Order Deny,Allow Deny from All  ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/  AllowOverride None Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch Order allow,deny Allow from all  ErrorLog ${APACHE_LOG_DIR}/error.log # Possible values include: debug, info, notice, warn, error, crit, # alert, emerg. LogLevel warn CustomLog ${APACHE_LOG_DIR}/access.log combined Alias /doc/ '/usr/share/doc/'  Options Indexes MultiViews FollowSymLinks AllowOverride None Order deny,allow Deny from all Allow from 127.0.0.0/255.0.0.0 ::1/128  DirectoryIndex index.cfm index.cfml default.cfm default.cfml index.htm index.html index.cfc RewriteEngine on RewriteCond %{SERVER_PORT} !^443$ RewriteRule ^.*$ https://%{SERVER_NAME}%{REQUEST_URI} [L,R]  

a

  ServerAdmin [email protected] DocumentRoot /var/www Alias /Railo/ '/var/www/Railo/'  Order Deny,Allow Deny from All  ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/  AllowOverride None Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch Order allow,deny Allow from all  ErrorLog ${APACHE_LOG_DIR}/error.log # Possible values include: debug, info, notice, warn, error, crit, # alert, emerg. LogLevel warn CustomLog ${APACHE_LOG_DIR}/ssl_access.log combined Alias /doc/ '/usr/share/doc/'  Options Indexes MultiViews FollowSymLinks AllowOverride None Order deny,allow Deny from all Allow from 127.0.0.0/255.0.0.0 ::1/128  # SSL Engine Switch: # Enable/Disable SSL for this virtual host. SSLEngine on # A self-signed (snakeoil) certificate can be created by installing # the ssl-cert package. See # /usr/share/doc/apache2.2-common/README.Debian.gz for more info. # If both key and certificate are stored in the same file, only the # SSLCertificateFile directive is needed. SSLCertificateFile /etc/ssl/certs/ssl-cert-snakeoil.pem SSLCertificateKeyFile /etc/ssl/private/ssl-cert-snakeoil.key # Server Certificate Chain: # Point SSLCertificateChainFile at a file containing the # concatenation of PEM encoded CA certificates which form the # certificate chain for the server certificate. Alternatively # the referenced file can be the same as SSLCertificateFile # when the CA certificates are directly appended to the server # certificate for convinience. #SSLCertificateChainFile /etc/apache2/ssl.crt/server-ca.crt # Certificate Authority (CA): # Set the CA certificate verification path where to find CA # certificates for client authentication or alternatively one # huge file containing all of them (file must be PEM encoded) # Note: Inside SSLCACertificatePath you need hash symlinks # to point to the certificate files. Use the provided # Makefile to update the hash symlinks after changes. #SSLCACertificatePath /etc/ssl/certs/ #SSLCACertificateFile /etc/apache2/ssl.crt/ca-bundle.crt # Certificate Revocation Lists (CRL): # Set the CA revocation path where to find CA CRLs for client # authentication or alternatively one huge file containing all # of them (file must be PEM encoded) # Note: Inside SSLCARevocationPath you need hash symlinks # to point to the certificate files. Use the provided # Makefile to update the hash symlinks after changes. #SSLCARevocationPath /etc/apache2/ssl.crl/ #SSLCARevocationFile /etc/apache2/ssl.crl/ca-bundle.crl # Client Authentication (Type): # Client certificate verification type and depth. Types are # none, optional, require and optional_no_ca. Depth is a # number which specifies how deeply to verify the certificate # issuer chain before deciding the certificate is not valid. #SSLVerifyClient require #SSLVerifyDepth 10 # Access Control: # With SSLRequire you can do per-directory access control based # on arbitrary complex boolean expressions containing server # variable checks and other lookup directives. The syntax is a # mixture between C and Perl. See the mod_ssl documentation # for more details. # #SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \ # and %{SSL_CLIENT_S_DN_O} eq 'Snake Oil, Ltd.' \ # and %{SSL_CLIENT_S_DN_OU} in {'Staff', 'CA', 'Dev'} \ # and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \ # and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20 ) \ # or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/ # # SSL Engine Options: # Set various options for the SSL engine. # o FakeBasicAuth: # Translate the client X.509 into a Basic Authorisation. 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 StrictRequire: # This denies access when 'SSLRequireSSL' or 'SSLRequire' applied even # under a 'Satisfy any' situation, i.e. when it applies access is denied # and no other module can change it. # 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 # MSIE 7 and newer should be able to use keepalive BrowserMatch 'MSIE [17-9]' ssl-unclean-shutdown DirectoryIndex index.cfm index.cfml default.cfm default.cfml index.htm index.html #Proxy .cfm and cfc requests to Railo ProxyPassMatch ^/(.+.cf[cm])(/.*)?$ http://127.0.0.1:8888/$1 ProxyPassReverse / http://127.0.0.1:8888/ #Deny access to admin except for local clients  Order deny,allow Deny from all # Allow from  # Allow from  Allow from 127.0.0.1    

Apache2.conf obsahuje následující:

 # Include the virtual host configurations: Include sites-enabled/  LoadModule jk_module /usr/lib/apache2/modules/mod_jk.so   JkMount /*.cfm ajp13 JkMount /*.cfc ajp13 JkMount /*.do ajp13 JkMount /*.jsp ajp13 JkMount /*.cfchart ajp13 JkMount /*.cfm/* ajp13 JkMount /*.cfml/* ajp13 # Flex Gateway Mappings # JkMount /flex2gateway/* ajp13 # JkMount /flashservices/gateway/* ajp13 # JkMount /messagebroker/* ajp13 JkMountCopy all JkLogFile /var/log/apache2/mod_jk.log  

Věřím, že většinu z toho chápu kromě zahrnutí jk_module, které jsem si všiml, má chybu, která se objeví v protokolech, které nemohu vyřešit:

[varovat] V souboru httpd.conf není definován žádný soubor JkShmFile. Používá se výchozí / etc / apache2 / logs / jk-runtime-status

Zkontroloval jsem svůj regulární výraz proti cestám adresářů pomocí RegexBuddy, abych se ujistil, že nemám pravdu. Zdá se, že problém nesouvisí s Regexem, i když ve směrnici Directory mohu mít něco nesprávného. Zdá se, že direktiva Location funguje správně pro blokování přístupu na stránky Railo admin.

  • Jsem hrozný s jasností. Myslím, že to, co se snažím vyřešit, je důvod, proč direktiva Directory, , selže, ale směrnice o umístění, , funguje. Pokud nahradím s Získávám výsledky, které hledám.

Chybová zpráva je stížnost od konektoru mod_jk, která chce soubor, který může použít pro účely sdílené paměti. Nejčastější důvod, proč vlastně potřeba tento soubor slouží k vyrovnávání zátěže, což nevypadá, že to děláte. Druhým důvodem jsou statusoví pracovníci, kteří se používají jen zřídka.

Pokud chcete, můžete chybu vyřešit pomocí řádku podobného následujícímu v konfiguraci apache: JkShmFile /var/log/apache2/mod_jk.shm

Neublíží vám však jednoduše ignorovat chybu.

Zde je podrobný popis toho, k čemu je soubor jkshmfile: http://tomcat.apache.org/connectors-doc/reference/apache.html

Snad to pomůže.

  • Uvidím, jestli mohu pomocí těchto informací ztišit chybu JkShmFile.

Pracoval pro vás: Charles Robertson | Chcete nás kontaktovat?