Benoit Schweblin benweet

How to debug an HTTPS connection issue with Spring Boot based Java application

Advanced logging:

java -jar -Djavax.net.debug=ssl:handshake:verbose app.jar

make sure you specify correct configuration:

java -jar -Djavax.net.debug=ssl:handshake:verbose app.jar --server.port=8443 --server.security.require-ssl=true --server.ssl.key-store=/path/to/keystore --server.ssl.key-store-password=password --server.ssl.protocol=TLS

See what’s in the store:

keytool -list -keystore /path/to/keystore -storepass password

Restore Rancher 2 cluster/node agents on clusters

This is an unsupported scenario, see rancher/rancher#14731 when there is an official solution.

When cattle-cluster-agent and/or cattle-node-agent are accidentally deleted, or when server-url/cacerts are changed.

Generate definitions

Generate API token in the UI (user -> API & Keys) and save the Bearer token
Find the clusterid in the Rancher UI (format is c-xxxxx), its in the address bar when the cluster is selected

Client-side SSL

For excessively paranoid client authentication.

Original: https://gist.github.com/mtigas/952344

Convert SSL certificate from CRT format to PEM

openssl x509 -in server.crt -out server.der -outform DER
openssl x509 -in server.der -inform DER -out server.pem -outform PEM

Auto-deploying built products to gh-pages with GitHub Actions

This is a set up for projects which want to check in only their source files, but have their gh-pages branch automatically updated with some compiled output every time they push.

A file below this one contains the steps for doing this with Travis CI. However, these days I recommend GitHub Actions, for the following reasons:

It is much easier and requires less steps, because you are already authenticated with GitHub, so you don't need to share secret keys across services like you do when coordinate Travis CI and GitHub.
It is free, with no quotas.
Anecdotally, builds are much faster with GitHub Actions than with Travis CI, especially in terms of time spent waiting for a builder.

Screen Quick Reference

Basic

Description	Command
Start a new session with session name	`screen -S <session_name>`
List running sessions / screens	`screen -ls`
Attach to a running session	`screen -x`
Attach to a running session with name	`screen -r`

	package at.favre.lib.bytes.otherPackage;

	import org.junit.Test;

	import javax.crypto.Cipher;
	import javax.crypto.SecretKey;
	import javax.crypto.spec.GCMParameterSpec;
	import javax.crypto.spec.SecretKeySpec;
	import java.nio.ByteBuffer;
	import java.nio.charset.StandardCharsets;

	package demo;

	import static java.lang.reflect.Modifier.*;

	import java.util.Arrays;
	import java.util.Set;

	import org.springframework.beans.BeansException;
	import org.springframework.beans.factory.annotation.Value;
	import org.springframework.beans.factory.config.BeanExpressionResolver;

	<!-- MIT License -->
	<html>
	<head>
	<script>
	function generateKey(alg, scope) {
	return new Promise(function(resolve) {
	var genkey = crypto.subtle.generateKey(alg, true, scope)
	genkey.then(function (pair) {
	resolve(pair)
	})

	# usage:
	#
	# ```
	# md = new Remarkable()
	# md.use remarkableMath()
	# parsedText = md.render text
	# ```

	remarkableMath = ->
	parser = (state, silent) ->

	#!/usr/bin/ruby
	# chkconfig: 35 99 01
	# description: EC2 DNS registration
	# processname: ec2hostname

	require 'aws-sdk'
	require 'net/http'

	`touch /var/lock/subsys/ec2hostname`