Wątek przeniesiony 2023-12-20 09:21 z PHP przez Riddle.

Jak poprawnie skonfigurować darmowe SSL?

1

Mam taki problem dopiero zaczynam z ssl postanowiłem uruchomić ssl na moim serwerze więc stworzyłem za pomocą narzędzia openssl darmowy klucz ssl i serwer działą na ssl tylko, że słyszałem, że w momencie kiedy jest darmowy klucz to prawie wszystkie przeglądarki rozpoznają połączenie jako niebezpieczne ?

Druga sprawa to jest taka, że jak już jest ssl na moim serwerze to nie da się weejśc za pomoca zwykłego http jest taki błąd.

Bad Request
Your browser sent a request that this server could not understand.
Reason: You're speaking plain HTTP to an SSL-enabled server port.
Instead use the HTTPS scheme to access this URL, please.

Mój system to centos 8 na vps ovh

2

Pokaż config. Odpaliłeś zapewne listener protokołu SSL na porcie 80, co zresztą masz w komunikacie. Musi być na 443.

0 
#
# This is the main Apache HTTP server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.4/> for detailed information.
# In particular, see 
# <URL:http://httpd.apache.org/docs/2.4/mod/directives.html>
# for a discussion of each configuration directive.
#
# See the httpd.conf(5) man page for more information on this configuration,
# and httpd.service(8) on using and configuring the httpd service.
#
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned.  
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path.  If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so 'log/access_log'
# with ServerRoot set to '/www' will be interpreted by the
# server as '/www/log/access_log', where as '/log/access_log' will be
# interpreted as '/log/access_log'.

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# Do not add a slash at the end of the directory path.  If you point
# ServerRoot at a non-local disk, be sure to specify a local disk on the
# Mutex directive, if file-based mutexes are used.  If you wish to share the
# same ServerRoot for multiple httpd daemons, you will need to change at
# least PidFile.
#
ServerRoot "/etc/httpd"
#DocumentRoot "/var/www/html/dziennik/nastroj_2020/public"
#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to 
# prevent Apache from glomming onto all bound IP addresses.
#
#Listen 12.34.56.78:80
Listen 80
LimitRequestLine 100000000
LimitRequestFieldSize 100000000
#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
#
Include conf.modules.d/*.conf
#LimitRequestLine 100000000
#LimitRequestFieldSize 100000000
#
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.  
#
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
#
User apache
Group apache

# 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition.  These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#

#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed.  This address appears on some server-generated pages, such
# as error documents.  e.g. [email protected]
#
ServerAdmin root@localhost

#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
#
#ServerName www.example.com:80

#
# Deny access to the entirety of your server's filesystem. You must
# explicitly permit access to web content directories in other 
# <Directory> blocks below.
#
<Directory />
    AllowOverride none
    Require all denied
</Directory>

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#

#
# Relax access to content within /var/www.
#
<Directory "/var/www">
    AllowOverride None
    # Allow open access:
    Require all granted
</Directory>

# Further relax access to the default document root:
<Directory "/var/www/html">
    #
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    #
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    #
    # The Options directive is both complicated and important.  Please see
    # http://httpd.apache.org/docs/2.4/mod/core.html#options
    # for more information.
    #
    Options Indexes FollowSymLinks

    #
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    #   Options FileInfo AuthConfig Limit
    #
    AllowOverride None

    #
    # Controls who can get stuff from this server.
    #
    Require all granted
</Directory>
LoadModule ssl_module modules/mod_ssl.so
#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
    DirectoryIndex index.html index.php
</IfModule>

#
# The following lines prevent .htaccess and .htpasswd files from being 
# viewed by Web clients. 
#
<Files ".ht*">
    Require all denied
</Files>

#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog "logs/error_log"

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

<IfModule log_config_module>
    #
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    #
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common

    <IfModule logio_module>
      # You need to enable mod_logio.c to use %I and %O
      LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
    </IfModule>

    #
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here.  Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    #
    #CustomLog "logs/access_log" common

    #
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #
    CustomLog "logs/access_log" combined
</IfModule>

<IfModule alias_module>
    #
    # Redirect: Allows you to tell clients about documents that used to 
    # exist in your server's namespace, but do not anymore. The client 
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo http://www.example.com/bar

    #
    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    #
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL.  You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.

    #
    # ScriptAlias: This controls which directories contain server scripts. 
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client.  The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    #
    ScriptAlias /cgi-bin/ "/var/www/cgi-bin/"

</IfModule>

#
# "/var/www/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "/var/www/cgi-bin">
    AllowOverride None
    Options None
    Require all granted
</Directory>

<IfModule mime_module>
    #
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    #
    TypesConfig /etc/mime.types

    #
    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #
    #AddType application/x-gzip .tgz
    #
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    #
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    #
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz

    #
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    #
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #
    #AddHandler cgi-script .cgi

    # For type maps (negotiated resources):
    #AddHandler type-map var

    #
    # Filters allow you to process content before it is sent to the client.
    #
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #
    AddType text/html .shtml
    AddOutputFilter INCLUDES .shtml
</IfModule>

#
# Specify a default charset for all content served; this enables
# interpretation of all content as UTF-8 by default.  To use the 
# default browser choice (ISO-8859-1), or to allow the META tags
# in HTML content to override this choice, comment out this
# directive:
#
AddDefaultCharset UTF-8

<IfModule mime_magic_module>
    #
    # The mod_mime_magic module allows the server to use various hints from the
    # contents of the file itself to determine its type.  The MIMEMagicFile
    # directive tells the module where the hint definitions are located.
    #
    MIMEMagicFile conf/magic
</IfModule>

#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
#

#
# EnableMMAP and EnableSendfile: On systems that support it, 
# memory-mapping or the sendfile syscall may be used to deliver
# files.  This usually improves server performance, but must
# be turned off when serving from networked-mounted 
# filesystems or if support for these functions is otherwise
# broken on your system.
# Defaults if commented: EnableMMAP On, EnableSendfile Off
#
#EnableMMAP off
EnableSendfile on
#DirectoryIndex index.php
DirectoryIndexRedirect on
# Supplemental configuration
#
# Load config files in the "/etc/httpd/conf.d" directory, if any.
IncludeOptional conf.d/*.conf
SSLProtocol all -SSLv2 -SSLv3 -TLSv1 -TLSv1.1
SSLCipherSuite ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384
ServerTokens Prod
ServerSignature Off
#LogLevel ssl:trace8
TraceEnable Off
<VirtualHost testing.xxxx.xxx>
    DocumentRoot /var/www/html/dziennik/dziennik_testing/nastroj_2021_testing/public
    <Directory /var/www/html/dziennik/dziennik_testing/nastroj_2021_testing/public>
        allow from all
        Options None
        Require all granted
    </Directory>
    ServerName testing.xxxx.xxxx
</VirtualHost>
SSLEngine on

SSLCertificateKeyFile /etc/httpd/conf/localhost.key
 SSLCertificateFile /etc/httpd/conf/localhost.cert
DocumentRoot /var/www/html
<Directory "/var/www/html/dziennik/nastroj_2020/public">
</Directory>
<Directory "/var/www/html/dziennik/nastroj_2020/public">
</Directory>

<VirtualHost xxxx.xxx>
    DocumentRoot /var/www/html/dziennik/nastroj_2020/public
    <Directory "/var/www/html/dziennik/nastroj_2020/public">
        allow from all
        Options None

        Require all granted

    </Directory>
    <Directory "/var/www/html/dziennik/nastroj_2020/public">
        allow from all
        Options None
        Require all granted
    </Directory>
    SSLEngine on
    ServerName xxx.xxx
</VirtualHost>
<VirtualHost www.xxx.xxx>
    DocumentRoot /var/www/html/dziennik/nastroj_2020/public
    <Directory "/var/www/html/dziennik/nastroj_2020/public">
        allow from all
        Options None
        
        Require all granted
    </Directory>
    <Directory "/var/www/html/dziennik/nastroj_2020/public">
        allow from all
        Options None
        Require all granted
    </Directory>
    <Directory "/var/www/html/dziennik/nastroj_2020/public">
        allow from all
        Options None
        Require all granted
    </Directory>
</VirtualHost>
<VirtualHost portfolio.xxxx.xxxxx>
    DocumentRoot /var/www/html/portfolio/logo
    <Directory "/var/www/html/portfolio/logo">
        allow from all
        Options None
        Require all granted
    </Directory>
</VirtualHost>
<VirtualHost testing.xxxx.xxxx>
    DocumentRoot /var/www/html/dziennik/dziennik_testing/nastroj_2021_testing/public
    <Directory "/var/www/html/dziennik/dziennik_testing/nastroj_2021_testing/public">
        allow from all
        Options None
        Require all granted
    </Directory>
</VirtualHost>
<VirtualHost xxx.xxx>
    DocumentRoot "/var/www/html/dziennik/nastroj_2020/public"
    <Directory "/var/www/html/dziennik/nastroj_2020/public">
        allow from all
        Options None
        Require all granted
    </Directory>
</VirtualHost>
<VirtualHost www.xxxx.xxx>
    DocumentRoot "/var/www/html/dziennik/nastroj_2020/public"
    <Directory "/var/www/html/dziennik/nastroj_2020/public">
        allow from all
        Options None
        Require all granted
    </Directory>
</VirtualHost>
<VirtualHost portfolio.xxxx.xxxx>
    DocumentRoot "/var/www/html/portfolio/logo"
    <Directory "/var/www/html/portfolio/logo">
        allow from all
        Options None
        Require all granted
    </Directory>
</VirtualHost>
0

@tomixtomi0001

  1. ja tam widzę 80 zamiast 443, widzę tam także localhost (z pobieżnego przejrzenia)
  2. wykasuj szybko ten plik konfiguracyjny, nie przeglądałem go jeszcze dokładnie, ale chyba udostępniłeś jakiś klucz publicznie
0

Da się w ogóle zrobić darmowy SSL publicznie? Czy tylko jakaś rzeźba ze swoim certyfikatem i importowaniem tego?

5

Da się, np. przez LetsEncrypt – https://letsencrypt.org/. Przy okazji dostajesz narzędzie certbot które potrafi samo ustawić konfigurację Apache czy nginx. Certyfikaty te trzeba dość często odnawiać, ale jest to też zgrabnie zautomatyzowane.

2

Jak ktoś się nie zna — ja, na przykład, się nie znam — to silnie polecam Caddy. Ile on mi czasu i nerwów zaoszczędził, to chyba żaden inny program nie…

0

@Ktos @Althorion
Ale domenę musisz mieć, IP wirtualki nie wystarczy...?

4

Domenę musisz mieć, certyfikat Let's Encrypt jest dla domeny (lub wielu domen), nie dla IP.

0
Ktos napisał(a):

Domenę musisz mieć, certyfikat Let's Encrypt jest dla domeny (lub wielu domen), nie dla IP.

Domena jest na razie wydaje się proste tylko nie mogę znaleźć narzędzie konfiguracyjnego dla pliku .conf

1

Caddy https://caddyserver.com/ sam automatycznie issue'uje certyfikaty Let's Encrypt, polecam spróbować zamiast Apache.

0
tomixtomi0001 napisał(a):

Domena jest na razie wydaje się proste tylko nie mogę znaleźć narzędzie konfiguracyjnego dla pliku .conf

Zainstaluj sobie certbot, ogarnie ci to automatycznie: https://certbot.eff.org/instructions

0

Nie tyle darmowy jest uznawany za niebezpieczny.

Za niebezpieczny jest uznawany taki którego root certificate authority (sorewicz ale nie wiem jak to po polsku mówimy) jest niezaufany (c.f. https://www.ssl.com/faqs/what-is-a-certificate-authority/amp/).

root certificate authority (CA) serves as the trust anchor

Jeśli sam sobie wygenerowała certyfikat dla domeny to jesteś sam swoim root CA - I nie jesteś zaufany.

Niektórzy za przywilej posiadania certyfikatu którego root CA jest powszechnie uznawany za zaufany

  • płacą (nie mam pojęcia dlaczego, pewnie względy historyczne, zanim powstało Let's Encrypt),
  • a niektórzy biorą darmowy od np. Let's Encrypt.
0

Skonfigurowałem sobie to i pod firefoxem wyświetla mi się jako bezpieczne pod operą niebezpieczne pod google-chrome niebezpieczne a pod edge na początku było jako bezpieczne a potem znowu niebezpieczne.

0

Mam coś takiego.

The web site does not use SSL, but shares an IP address with some other site that does.
The web site no longer exists, yet the domain name still points to the old IP address, where some other site is now hosted.
The web site uses a content delivery network (CDN) that does not support SSL.
The domain name is an alias for a web site whose main name is different, but the alias was not included in the certificate by mistake.
0

Co ciekawe jak wchodzę przez www.ssss.sss to jest certyfikat a bez www nie ma

1

Musisz mieć certyfikat zarówno dla example.com, jak i dla www.example.com (bo zasadniczo www. to tylko subdomena) – jak masz tlyko dla tego drugiego, to nie zadziała na pierwszym. I oczywiście dla obydwu domen skonfigurować TLS, żeby był aktywny.

1

Ewentualnie przekierować wszystko na jeden adres.

0
Roman Mokrzan napisał(a):

nie wiem jak to po polsku mówimy

Certificate Authority = Urząd Certyfikacji.

1 użytkowników online, w tym zalogowanych: 0, gości: 1