odan

Nginx and PHP Setup on Windows

For local development you could also use Nginx with PHP as an replacement for XAMPP.

Install Nginx

• Download Nginx for Windows: http://nginx.org/en/download.html | Direct: nginx-1.19.7.zip
• Extract the ZIP file to c:\nginx
• Open the file c:/nginx/config/nginx.conf and replace the server { ... } section with this configuration:

soarez

How to setup your own CA with OpenSSL

For educational reasons I've decided to create my own CA. Here is what I learned.

First things first

Lets get some context first.

Hakky54

Curl with Java KeyStore

Curl doesn't have support for java keystore file, so therefor the file should be converted to a PEM format. It consists of the following multiple steps:

1. Convert keystore to p12 file
2. Convert p12 file to pem file
3. Run curl command with pem files

One way TLS/SSL/Authentication

Convert keystore to p12 file

subfuzion

There are certain files created by particular editors, IDEs, operating systems, etc., that do not belong in a repository. But adding system-specific files to the repo's .gitignore is considered a poor practice. This file should only exclude files and directories that are a part of the package that should not be versioned (such as the node_modules directory) as well as files that are generated (and regenerated) as artifacts of a build process.

All other files should be in your own global gitignore file:

• Create a file called .gitignore in your home directory and add any filepath patterns you want to ignore.
• Tell git where your global gitignore file is.

Note: The specific name and path you choose aren't important as long as you configure git to find it, as shown below. You could substitute .config/git/ignore for .gitignore in your home directory, if you prefer.

odan

Installing Xdebug for XAMPP with PHP 7.x

• New: XAMPP - XDebug Setup for PHP 8

Requirements

• XAMPP for Windows: https://www.apachefriends.org/download.html
• Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019

Setup

mtigas

Client-side SSL

For excessively paranoid client authentication.

---

Updated Apr 5 2019:

because this is a gist from 2011 that people stumble into and maybe you should AES instead of 3DES in the year of our lord 2019.

some other notes:

vepo

cURL with Java Keystore/Truststore

Curl doesn't have support for java keystore file, so therefor the file should be converted to a PEM format. It consists of the following multiple steps:

1. Convert keystore to p12 file
2. Convert p12 file to pem file
3. Run curl command with pem files

Convert keystore to p12 file

tkersey

Remove file from git repository (history)

SOLUTION: This is the shortest way to get rid of the files:

1. check .git/packed-refs - my problem was that I had there a refs/remotes/origin/master line for a remote repository, delete it, otherwise git won't remove those files

2. (optional) git verify-pack -v .git/objects/pack/#{pack-name}.idx | sort -k 3 -n | tail -5 - to check for the largest files

3. (optional) git rev-list --objects --all | grep #{SHA_FROM_#_3} - to check what files those are

Eng-Fouad

Steps to generate self-signed PKCS#12 SSL certificate and export its keys:

1- Create PKCS#12 keystore (.p12 or .pfx file)

keytool -genkeypair -keystore myKeystore.p12 -storetype PKCS12 -storepass MY_PASSWORD -alias KEYSTORE_ENTRY -keyalg RSA -keysize 2048 -validity 99999 -dname "CN=My SSL Certificate, OU=My Team, O=My Company, L=My City, ST=My State, C=SA" -ext san=dns:mydomain.com,dns:localhost,ip:127.0.0.1

• myKeystore.p12 = keystore filename. It can with .pfx extension as well.
• MY_PASSWORD = password used for the keystore and the private key as well.
• CN = commonName, it will be shown as certiciate name in certificates list.
• OU = organizationUnit, department name for example.

shamil

Client-side SSL

Create a Certificate Authority root (which represents this server)

Organization & Common Name: Some human identifier for this server CA.

openssl genrsa -out ca.key 2048
openssl req -new -x509 -days 365 -key ca.key -out ca.crt

Create the Client Key and CSR