The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the
package main | |
import ( | |
"flag" | |
"os" | |
"time" | |
"github.com/coding-yogi/goperf/log" | |
"github.com/coding-yogi/goperf/tests" | |
) |
#!/usr/bin/env python3 | |
# Proof of concept ara with ansible-runner | |
# Requires https://github.com/ansible/ansible-runner/issues/219#issuecomment-496191227 | |
import ansible_runner | |
import os | |
from ara.setup import callback_plugins | |
PLAYBOOK = """ | |
- name: Test for ansible-runner |
javascript:document.body.contentEditable = 'true'; document.designMode='on'; void 0 |
This document contains excerpts from my web server logs collected over a period of 7 years that shows various kinds of recon and attack vectors.
There were a total of 37.2 million lines of logs out of which 1.1 million unique HTTP requests (Method + URI) were found.
$ sed 's/^.* - - \[.*\] "\(.*\) HTTP\/.*" .*/\1/' access.log > requests.txt
#include <time.h> // Robert Nystrom | |
#include <stdio.h> // @munificentbob | |
#include <stdlib.h> // for Ginny | |
#define r return // 2008-2019 | |
#define l(a, b, c, d) for (i y=a;y\ | |
<b; y++) for (int x = c; x < d; x++) | |
typedef int i;const i H=40;const i W | |
=80;i m[40][80];i g(i x){r rand()%x; | |
}void cave(i s){i w=g(10)+5;i h=g(6) | |
+3;i t=g(W-w-2)+1;i u=g(H-h-2)+1;l(u |
package main | |
import ( | |
"bytes" | |
"fmt" | |
"io/ioutil" | |
"log" | |
"golang.org/x/crypto/ssh" | |
kh "golang.org/x/crypto/ssh/knownhosts" |
#!/bin/bash | |
# Copyright 2019 Google LLC. | |
# SPDX-License-Identifier: Apache-2.0 | |
if [[ $# -ne 2 ]]; then | |
echo "Usage: $0 <Service Name> <Path>" | |
exit 1 | |
fi | |
service_name=$1 |
''' | |
Title: SSHtranger Things | |
Author: Mark E. Haase <[email protected]> | |
Homepage: https://www.hyperiongray.com | |
Date: 2019-01-17 | |
CVE: CVE-2019-6111, CVE-2019-6110 | |
Advisory: https://sintonen.fi/advisories/scp-client-multiple-vulnerabilities.txt | |
Tested on: Ubuntu 18.04.1 LTS, OpenSSH client 7.6p1 | |
We have nicknamed this "SSHtranger Things" because the bug is so old it could be |
https://twitter.com/snookca/status/1073299331262889984?s=21
“In what way is JS any more maintainable than CSS? How does writing CSS in JS make it any more maintainable?”
Happy to chat about this. There’s an obvious disclaimer that there’s a cost to css-in-js solutions, but that cost is paid specifically for the benefits it brings; as such it’s useful for some usecases, and not meant as a replacement for all workflows.
(These conversations always get heated on twitter, so please believe that I’m here to converse, not to convince. In return, I promise to listen to you too and change my opinions; I’ve had mad respect for you for years and would consider your feedback a gift. Also, some of the stuff I’m writing might seem obvious to you; I’m not trying to tell you if all people of some of the details, but it might be useful to someone else who bumps into this who doesn’t have context)
So the big deal about css-in-js (cij) is selectors.