Helio Campos Mello de Andrade HelioCampos
| #!/usr/bin/python | |
| # | |
| # Usage: packer-config my-template.yaml | packer build - | |
| # | |
| # Constructs a Packer JSON configuration file from the specified YAML | |
| # template file and writes it to STDOUT. | |
| # | |
| # The YAML template format adds some flexibility and readability by | |
| # adding comments and an !include directive, allowing for the | |
| # following template syntax: |
| #!/bin/bash | |
| # Script to backup git repo to S3 | |
| # Set bucket, dir, password and account to use for the backup. I keep mine in local env vars | |
| # These are set by localrc which lives on an encrypted home directory and is executed by my bashrc | |
| bucket=$GITHUB_BACKUP_BUCKET | |
| dir=$GITHUB_BACKUP_DIR | |
| password=$GITHUB_BACKUP_PASSWORD | |
| account=$GITHUB_ACCOUNT |
| # This gist is compatible with Ansible 1.x . | |
| # For Ansible 2.x , please check out: | |
| # - https://gist.github.com/dmsimard/cd706de198c85a8255f6 | |
| # - https://github.com/n0ts/ansible-human_log | |
| # This program is free software: you can redistribute it and/or modify | |
| # it under the terms of the GNU General Public License as published by | |
| # the Free Software Foundation, either version 3 of the License, or | |
| # (at your option) any later version. | |
| # |
| [default] | |
| access_key = asf | |
| bucket_location = US | |
| cloudfront_host = cloudfront.amazonaws.com | |
| cloudfront_resource = /2010-07-15/distribution | |
| default_mime_type = binary/octet-stream | |
| delete_removed = False | |
| dry_run = False | |
| encoding = UTF-8 | |
| encrypt = False |
This simple script will take a picture of a whiteboard and use parts of the ImageMagick library with sane defaults to clean it up tremendously.
The script is here:
#!/bin/bash
convert $1 -morphology Convolve DoG:15,100,0 -negate -normalize -blur 0x1 -channel RBG -level 60%,91%,0.1 $2
| [5:08pm] Luis_Byclosure: I'm having problems applying the "5 Why" rule, to the feature | |
| "login" (imagine an application like youtube) | |
| [5:08pm] Luis_Byclosure: how do you explain the business value of the feature "login"? | |
| [5:09pm] Luis_Byclosure: In order to be recognized among other people, I want to login | |
| in the application (?) | |
| [5:09pm] Luis_Byclosure: why do I want to be recognized among other people? | |
| [5:11pm] aslakhellesoy: Why do people have to log in? | |
| [5:12pm] Luis_Byclosure: I dunno... why? | |
| [5:12pm] aslakhellesoy: I'm asking you | |
| [5:13pm] aslakhellesoy: Why have you decided login is needed? |
At its core an X.509 certificate is a digital document that has been encoded and/or digitally signed according to RFC 5280.
In fact, the term X.509 certificate usually refers to the IETF’s PKIX Certificate and CRL Profile of the X.509 v3 certificate standard, as specified in RFC 5280, commonly referred to as PKIX for Public Key Infrastructure (X.509).
#X509 File Extensions
The first thing we have to understand is what each type of file extension is. There is a lot of confusion about what DER, PEM, CRT, and CER are and many have incorrectly said that they are all interchangeable. While in certain cases some can be interchanged the best practice is to identify how your certificate is encoded and then label it correctly. Correctly labeled certificates will be much easier to manipulat
#Encodings (also used as extensions)
Creating a Certificate Authority is easy. There are many scripts out there to do it for you. However, creating a CA that is easy to manage can be tricky. This should walk you through creating a CA and explain all the pieces.
Note: This page takes an extra step to make a fairly PKIX-compliant Certificate Authority. In pariticular, it ensures that the email address associated with your CA is in the SubjectAltName extension rather than in the DN. The former is the PKIX and X509v3 standard way of presenting an email address while the later is the old X509v1 way.