如何获取在本地Laravel Homestead站点上运行的https证书 [英] How to get https certificate working on local Laravel Homestead site

问题描述

我遇到了这个问题：

我在Windows 10 Chrome版本65.0.3325.181（官方版本）（64位）中看到的错误是：

你的连接不是私密的

攻击者可能试图从（（mysite））窃取你的
信息（例如，密码，
消息，或信用卡）。了解更多NET :: ERR_CERT_AUTHORITY_INVALID

此页面不安全（HTTPS损坏）。

证书 - 缺失

此
网站缺少有效的可信证书
（net :: ERR_CERT_AUTHORITY_INVALID）。

Firefox Quantum 59.0.2（64位）说：

您的连接不安全

（（mysite））的所有者已将其网站配置为
不当。为了防止您的信息被盗，Firefox有
没有连接到这个网站。

连接不安全

无法验证此证书，因为
发行人未知。

我已经尝试过：：本地计算机和当前用户证书存储。没有必要使用本地机器证书存储，因为我们只为我们当前的用户工作。然后，有子库。其中最受关注的是两个预定义的：受信任的根证书颁发机构和中间证书颁发机构商店。通常在命令行中称为 root和CA 。

您可以按照chrome：// settings /？search = Manage％20certificates，然后点击Manage certificates进入Chrome的证书管理器。最感兴趣的是受信任的根证书颁发机构和中间证书颁发机构选项卡。

管理员证书的一种方法是通过命令行：

 > rem列表当前用户>受信任的根证书颁发机构存储
> certutil.exe -store -user root 
 
> rem list Local Machine>中级证书颁发机构存储
> certutil.exe -store -enterprise CA 
 
> rem GUI版本-store命令
> certutil.exe -viewstore -user CA 
 
> rem将证书添加到当前用户>受信任的根证书颁发机构存储
> certutil.exe -addstore -user root path \to \ file.crt 
 
> rem从当前用户删除证书>受信任的根证书颁发机构按序列号存储
> certutil.exe -delstore -user root 03259fa1 
 
> rem -delstore命令的GUI版本
> certutil.exe  - viewdelstore -user CA 
  

结果如下（对于本地计算机和当前用户证书存储）：

  root 
 homestead.test.crt 
 error 
 ca.homestead.homestead.crt 
出现在受信任的根证书颁发机构选项卡中
 CA 
 homestead.test.crt 
不起作用，显示在其他人选项卡中
 ca.homestead.homestead.crt 
不起作用，显示在中级证书颁发机构标签中
  

其他选项将是双倍的 - 在资源管理器中单击证书，从Chrome的证书管理器导入证书，使用证书MMC管理单元（运行 certmgr.msc ），或使用 CertMgr.exe 。

对于那些安装了 grep 的人，以下是如何快速查看证书的位置：

 > certutil.exe -store -user root | grephomestead\ | ^ root \ | ^ CA^ 
& certutil.exe -store -user CA | grephomestead\ | ^ root \ | ^ CA^ 
& certutil.exe -store -enterprise root | grephomestead\ | ^ root \ | ^ CA^ 
& certutil.exe -store -enterprise CA | grephomestead \ | ^ root \ | ^ CA
  

因此，将CA证书安装到Current用户>受信任的根证书颁发机构存储似乎是最佳选择。 确保不要忘记重启你的浏览器。

更深入地解释其工作原理

In Vagrantfile 它需要 scripts / homestead.rb ，然后运行 Homestead.configure 。这是方法，配置 vagrant 进行所有必要的准备工作。

我们可以见：

 如果settings.include？ 'sites'
设置[sites]。每个都做| site | 
 
＃创建SSL证书
 config.vm.provisionshelldo | s | 
 s.name =创建证书：+ site [map] 
 s.path = scriptDir +/ create-certificate.sh
 s.args = [site [ map]] 
 end 
 
 ... 
 
 config.vm.provisionshelldo | s | 
 ... 
 s.path = scriptDir +/serve-#{type}.sh
 ... 
 end 
 
 .. 。
结束
结束
  

所以，这些文件分别创建证书和 nginx config。 / p>

进一步阅读

如何使浏览器信任localhost SSL证书？

I'm getting this problem:

The error that I'm seeing in Windows 10 Chrome Version 65.0.3325.181 (Official Build) (64-bit) is:

Your connection is not private

Attackers might be trying to steal your information from ((mysite)) (for example, passwords, messages, or credit cards). Learn more NET::ERR_CERT_AUTHORITY_INVALID

This page is not secure (broken HTTPS).

Certificate - missing

This site is missing a valid, trusted certificate (net::ERR_CERT_AUTHORITY_INVALID).

Firefox Quantum 59.0.2 (64-bit) says:

Your connection is not secure

The owner of ((mysite)) has configured their website improperly. To protect your information from being stolen, Firefox has not connected to this website.

Connection is Not Secure

Could not verify this certificate because the issuer is unknown.

I have already tried: https://stackoverflow.com/a/47755133/470749

vboxmanage --version
5.2.6r120293

vagrant -v
Vagrant 2.0.2

git branch
* (HEAD detached at v7.3.0)

vagrant box list
laravel/homestead (virtualbox, 5.2.0)

vagrant box update
==> vboxHomestead: Checking for updates to 'laravel/homestead'
    vboxHomestead: Latest installed version: 5.2.0
    vboxHomestead: Version constraints: >= 5.2.0
    vboxHomestead: Provider: virtualbox
==> vboxHomestead: Box 'laravel/homestead' (v5.2.0) is running the latest version.

I wonder if this means that I'm not yet using release 7.1.0 (which has in its changelog "sign SSL certificates with a custom root certificate"), and I wonder if that's why I have this SSL HTTPS problem.

What are the next steps I should try now to get the certificate working?

解决方案

Unfortunately, I don't have an easy way of checking it on Windows, so I'm going to use VirtualBox running on Linux here. Install vagrant, then:

$ vagrant box add laravel/homestead
$ git clone https://github.com/laravel/homestead.git
$ cd homestead
$ git checkout v7.3.0
$ bash init.sh

I've simplified Homestead.yaml a bit (you might prefer to stick with the defaults):

---
ip: "192.168.10.10"
provider: virtualbox
folders:
    - map: /home/yuri/_/la1
      to: /home/vagrant/code
sites:
    - map: homestead.test
      to: /home/vagrant/code/public

Then:

$ mkdir -p ~/_/la1/public
$ echo '<?php echo "it works";' > ~/_/la1/public/index.php

$ vagrant up

$ vagrant ssh -c 'ls /etc/nginx/sites-enabled'
homestead.test

$ vagrant ssh -c 'cat /etc/nginx/sites-enabled/homestead.test'
server {
    listen 80;
    listen 443 ssl http2;
    server_name .homestead.test;
    root "/home/vagrant/code/public";
    ...
    ssl_certificate     /etc/nginx/ssl/homestead.test.crt;
    ssl_certificate_key /etc/nginx/ssl/homestead.test.key;
}

As we can see it has the certificates in /etc/nginx/ssl:

$ vagrant ssh -c 'ls -1 /etc/nginx/ssl'
ca.homestead.homestead.cnf
ca.homestead.homestead.crt
ca.homestead.homestead.key
ca.srl
homestead.test.cnf
homestead.test.crt
homestead.test.csr
homestead.test.key

I tried to trust server certificate systemwide, but it didn't work out. It appeared on Servers tab in Firefox' Certificate Manager, but that didn't make Firefox trust it. I could probably have added an exception, but trusting CA certificates looks like a better option. Trusting CA certificate makes browser trust any certificate they issue (new sites running under Homestead). So we're going to go with CA certificate here:

$ vagrant ssh -c 'cat /etc/nginx/ssl/ca.homestead.homestead.crt' > ca.homestead.homestead.crt

$ sudo trust anchor ca.homestead.homestead.crt

$ trust list | head -n 5
pkcs11:id=%4c%f9%25%11%e5%8d%ad%5c%2a%f3%63%b6%9e%53%c4%70%fa%90%4d%77;type=cert
    type: certificate
    label: Homestead homestead Root CA
    trust: anchor
    category: authority

Then, I've added 192.168.10.10 homestead.test to /etc/hosts, restarted Chromium, and it worked:

P.S. I'm running Chromium 65.0.3325.162, and Firefox 59.0.

Windows

Apparently, Windows doesn't have trust utility. Under Windows one has two stores: Local Machine and Current User Certificate stores. No point in using Local Machine Certificate Store, since we're making it work just for our current user. Then, there are substores. With two predefined of them being of most interest: Trusted Root Certification Authorities and Intermediate Certification Authorities Stores. Commonly referred in command line as root and CA.

You can access Chrome's Certificate Manager by following chrome://settings/?search=Manage%20certificates, then clicking Manage certificates. Of most interest are Trusted Root Certification Authorities and Intermediate Certification Authorities tabs.

One way to manager certificates is via command line:

>rem list Current User > Trusted Root Certification Authorities store
>certutil.exe -store -user root

>rem list Local Machine > Intermediate Certification Authorities store
>certutil.exe -store -enterprise CA

>rem GUI version of -store command
>certutil.exe -viewstore -user CA

>rem add certificate to Current User > Trusted Root Certification Authorities store
>certutil.exe -addstore -user root path\to\file.crt

>rem delete certificate from Current User > Trusted Root Certification Authorities store by serial number
>certutil.exe -delstore -user root 03259fa1

>rem GUI version of -delstore command
>certutil.exe -viewdelstore -user CA

The results are as follows (for both Local Machine and Current User Certificate stores):

root
    homestead.test.crt
        error
    ca.homestead.homestead.crt
        appears in Trusted Root Certification Authorities tab
CA
    homestead.test.crt
        doesn't work, appears in Other People tab
    ca.homestead.homestead.crt
        doesn't work, appears in Intermediate Certification Authorities tab

Other options would be double-clicking on a certificate in Explorer, importing certificates from Chrome's Certificate Manager, using Certificates MMC Snap-in (run certmgr.msc), or using CertMgr.exe.

For those who have grep installed, here's how to quickly check where is the certificate:

>certutil.exe -store -user root | grep "homestead\|^root\|^CA" ^
& certutil.exe -store -user CA | grep "homestead\|^root\|^CA" ^
& certutil.exe -store -enterprise root | grep "homestead\|^root\|^CA" ^
& certutil.exe -store -enterprise CA | grep "homestead\|^root\|^CA"

So, installing CA certificate into Current User > Trusted Root Certification Authorities store seems like the best option. And make sure not to forget to restart your browser.

more in-depth explanation of how it works

In Vagrantfile it requires scripts/homestead.rb, then runs Homestead.configure. That's the method, that configures vagrant to make all the needed preparations.

There we can see:

if settings.include? 'sites'
    settings["sites"].each do |site|

        # Create SSL certificate
        config.vm.provision "shell" do |s|
            s.name = "Creating Certificate: " + site["map"]
            s.path = scriptDir + "/create-certificate.sh"
            s.args = [site["map"]]
        end

        ...

        config.vm.provision "shell" do |s|
            ...
            s.path = scriptDir + "/serve-#{type}.sh"
            ...
        end

        ...
    end
end

So, these two files create certificate and nginx config respectively.

further reading

How to make browser trust localhost SSL certificate?

这篇关于如何获取在本地Laravel Homestead站点上运行的https证书的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！