Linux ip-172-26-7-228 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64
Apache
: 172.26.7.228 | : 18.220.227.250
Cant Read [ /etc/named.conf ]
5.6.40-24+ubuntu18.04.1+deb.sury.org+1
www-data
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
HASH IDENTIFIER
README
+ Create Folder
+ Create File
/
etc /
apache2 /
sites-enabled /
[ HOME SHELL ]
Name
Size
Permission
Action
000-default.conf
1.49
KB
-rw-r--r--
admissions.rrinstitutions.com
6.55
KB
-rw-r--r--
admissions.rrinstitutions.com....
6.55
KB
-rw-r--r--
admissions.trustinfinie.com.ss...
6.57
KB
-rw-r--r--
admissions2.trustinfinie.com.s...
6.59
KB
-rw-r--r--
bkmh.org.conf
580
B
-rw-r--r--
bkmh.org.ssl.conf
6.55
KB
-rw-r--r--
college.logisys.org.conf
561
B
-rw-r--r--
college.universitysolutions.in...
6.76
KB
-rw-r--r--
collegeportal.universitysoluti...
6.77
KB
-rw-r--r--
default-ssl.conf
6.55
KB
-rw-r--r--
egov.universitysolutions.in.co...
720
B
-rw-r--r--
egov.universitysolutions.in.ss...
6.76
KB
-rw-r--r--
fms.universitysolutions.in.ssl...
6.55
KB
-rw-r--r--
gcak.conf
567
B
-rw-r--r--
gfgcg.conf
570
B
-rw-r--r--
logisys.org.conf
563
B
-rw-r--r--
logisys.org.ssl.conf
6.54
KB
-rw-r--r--
nrupathungauniversityblr.conf
589
B
-rw-r--r--
oasis.logisys.org.conf
558
B
-rw-r--r--
oasis.logisys.org.ssl.conf
6.51
KB
-rw-r--r--
orms.universitysolutions.in.ss...
6.76
KB
-rw-r--r--
qpms.universitysolutions.in.ss...
6.76
KB
-rw-r--r--
qptran.universitysolutions.in....
6.56
KB
-rw-r--r--
results.logisys.org.conf
573
B
-rw-r--r--
results.logisys.org.ssl.conf
6.52
KB
-rw-r--r--
rur.ac.in.conf
741
B
-rw-r--r--
rur.ac.in.ssl.conf
6.77
KB
-rw-r--r--
school.universitysolutions.in....
6.76
KB
-rw-r--r--
student.logisys.org.conf
576
B
-rw-r--r--
student.logisys.org.ssl.conf
6.52
KB
-rw-r--r--
studentapp.universitysolutions...
6.77
KB
-rw-r--r--
tdvsapp.universitysolutions.in...
6.77
KB
-rw-r--r--
test.universitysolutions.in.ss...
6.76
KB
-rw-r--r--
universitysolutions.in.ssl.con...
6.55
KB
-rw-r--r--
www.gcak.conf
571
B
-rw-r--r--
www.gfgcg.conf
574
B
-rw-r--r--
www.logisys.org.conf
567
B
-rw-r--r--
www.nrupathungauniversityblr.c...
593
B
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : collegeportal.universitysolutions.in.ssl.conf
<IfModule mod_ssl.c> <VirtualHost _default_:443> ServerAdmin webmaster@localhost ServerName collegeportal.universitysolutions.in Header always set Strict-Transport-Security "max-age=15552000; includeSubDomains" Header set X-Frame-Options SAMEORIGIN Header set X-XSS-Protection "1; mode=block" Header set X-Content-Type-Options nosniff DocumentRoot /var/www/college <Directory /var/www/college> Options Indexes FollowSymLinks AllowOverride All Order Deny,Allow Allow from All DirectoryIndex index.html index.php </Directory> # Available loglevels: trace8, ..., trace1, debug, info, notice, warn, # error, crit, alert, emerg. # It is also possible to configure the loglevel for particular # modules, e.g. #LogLevel info ssl:warn ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_LOG_DIR}/access.log combined # For most configuration files from conf-available/, which are # enabled or disabled at a global level, it is possible to # include a line for only one particular virtual host. For example the # following line enables the CGI configuration for this host only # after it has been globally disabled with "a2disconf". #Include conf-available/serve-cgi-bin.conf # 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/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/letsencrypt/live/universitysolutions.in-0001/fullchain.pem SSLCertificateKeyFile /etc/letsencrypt/live/universitysolutions.in-0001/privkey.pem # 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/sites-available/ca_bundle.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 # 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 OptRenegotiate: # This enables optimized SSL connection renegotiation handling when SSL # directives are used in per-directory context. #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire <FilesMatch "\.(cgi|shtml|phtml|php)$"> SSLOptions +StdEnvVars </FilesMatch> <Directory /usr/lib/cgi-bin> SSLOptions +StdEnvVars </Directory> # 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 </VirtualHost> </IfModule> # vim: syntax=apache ts=4 sw=4 sts=4 sr noet
Close