| /* | |
| * Copyright 2020 The Netty Project | |
| * | |
| * The Netty Project licenses this file to you under the Apache License, | |
| * version 2.0 (the "License"); you may not use this file except in compliance | |
| * with the License. You may obtain a copy of the License at: | |
| * | |
| * https://www.apache.org/licenses/LICENSE-2.0 | |
| * | |
| * Unless required by applicable law or agreed to in writing, software |
Fibers are an abstraction over sequential computation, similar to threads but at a higher level. There are two ways to think about this model: by example, and abstractly from first principles. We'll start with the example.
(credit here is very much due to Fabio Labella, who's incredible Scala World talk describes these ideas far better than I can)
Consider the following three functions
| #!/usr/bin/env sh | |
| set -- $(locale LC_MESSAGES) | |
| yesptrn="$1"; noptrn="$2"; yesword="$3"; noword="$4" | |
| parent_path=$( cd "$(dirname "${BASH_SOURCE[0]}")" ; pwd -P ) | |
| input_sink=$(pacmd stat |grep -o -P "(?<=Default source name: ).*") | |
| output_sink=$(pacmd stat |grep -o -P "(?<=Default sink name: ).*") | |
| echo "Input:" $input_sink |
| default['sshd']['sshd_config']['AuthenticationMethods'] = 'publickey,keyboard-interactive:pam' | |
| default['sshd']['sshd_config']['ChallengeResponseAuthentication'] = 'yes' | |
| default['sshd']['sshd_config']['PasswordAuthentication'] = 'no' |
This is a compiled list of falsehoods programmers tend to believe about working with time.
Don't re-invent a date time library yourself. If you think you understand everything about time, you're probably doing it wrong.
| # Put in your ~/.ssh/config | |
| ### Problem | |
| # | |
| # You are on a public WiFi network that blocks SSH ports but you don't want to switch | |
| # to pushing your Github changes to GH remotes via HTTPS nor do you want to change the | |
| # remote hostname in all your repos. | |
| Host github.com | |
| Hostname ssh.github.com |
| # Use dig to find out about the k8s records | |
| # dig +vc -p 5300 @127.0.0.1 cluser.local | |
| # Use dig to retrieve an A Record | |
| # dig +vc -p 5300 @127.0.0.1 A cb-example-0000.default.svc.cluster.local | |
| # Use dig to do a reverse lookup (-x flag) | |
| #dig +vc -p 5300 @127.0.0.1 -x 10.0.50.156 | |
| # Add the port forward |
|
You'll probably be working with a single smartcard, so you'll want only one primary key ( |
tl;dr Generate a GPG key pair (exercising appropriate paranoia). Send it to key servers. Create a Keybase account with the public part of that key. Use your keypair to sign git tags and SBT artifacts.
GPG is probably one of the least understood day-to-day pieces of software in the modern developer's toolshed. It's certainly the least understood of the important pieces of software (literally no one cares that you can't remember grep's regex variant), and this is a testament to the mightily terrible user interface it exposes to its otherwise extremely simple functionality. It's almost like cryptographers think that part of the security comes from the fact that bad guys can't figure it out any more than the good guys can.
Anyway, GPG is important for open source in particular because of one specific feature of public/private key cryptography: signing. Any published software should be signed by the developer (or company) who published it. Ideally, consu
This guide is unmaintained and was created for a specific workshop in 2017. It remains as a legacy reference. Use at your own risk.
Workshop Instructor:
This workshop is distributed under a CC BY-SA 4.0 license.
