This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
From https://github.com/cloudflare/sslconfig/blob/master/patches/nginx__http2_spdy.patch | |
From: Lolo32 | |
Date: Wed, 15 Jun 2016 22:35:52 +0200 | |
Subject: [PATCH] Add SPDY support back to Nginx with HTTP/2, based on cloudflare patch | |
This patch was based on https://github.com/cloudflare/sslconfig/blob/master/patches/nginx__http2_spdy.patch | |
that is for v.0.9. It's tested and working, but need, maybe, additional tests for high load charge. | |
This work on v.1.10.1 and v.1.11.1 of Nginx. | |
--- |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
" Active la coloration syntaxique | |
syntax on | |
" Coloration à utiliser | |
colorscheme elflord | |
" Affichage des caractères invisibles (tabulations, espaces de fin de ligne) | |
set list | |
set listchars=trail:·,tab:»·,nbsp:%,extends:╕,precedes:╘ | |
" Affichage des paires correspondantes |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/sh | |
# Usage Number 0 – CA specification | |
# Specifies the Certificate Authority (CA) who will provide TLS certificates | |
# for the domain. We can only say that the domain will use TLS certificates | |
# from a specific CA. Like we are using Geotrust as CA. It only will allow | |
# Geotrust. It is difficult to get a SSL/TLS certificate from Geotrust | |
# without being WE. | |
# Usage Number 1 – Specific TLS certificate | |
# Specifies the exact TLS certificate that should be used for the domain. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
// Based on https://gist.github.com/aeris/2a0f9beeed94102fd0cb2a8caad964d0 | |
package main | |
import ( | |
"crypto/aes" | |
"crypto/cipher" | |
"crypto/rand" | |
"encoding/binary" | |
"os" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# /etc/apt/apt.conf.d/99-recommended.conf | |
APT::Install-Recommends "false"; | |
APT::AutoRemove::RecommendsImportant "false"; | |
APT::AutoRemove::SuggestsImportant "false"; |
Here we create the master key. We want only Certify
capability: we use the master key only to create the subkeys, Sign - Encrypt - Authenticate
capabilities will be assigned to the subkeys.
Run the following command to start the master key generation process. Select the set your own capabilities
creation process (type 8
)
▶ gpg --full-generate-key --expert
gpg (GnuPG) 2.2.9; Copyright (C) 2018 Free Software Foundation, Inc.
I hereby claim:
- I am lolo32 on github.
- I am lolo32 (https://keybase.io/lolo32) on keybase.
- I have a public key whose fingerprint is 23C4 AAB8 212D 3AC4 FEB3 29EB 6D79 A5C9 0532 54EF
To claim this, I am signing this object: