| #!/bin/bash | |
| CONTENT_TYPE="application/json" | |
| DESCRIPTION="bad things™ are happening" | |
| URL="https://events.pagerduty.com/generic/2010-04-15/create_event.json" | |
| if [ $# -ne 3 ]; then | |
| echo "Usage: pd-event.sh [TYPE] [SERVICE KEY] [INCIDENT KEY]" | |
| echo " - TYPE: [t]rigger | [a]cknowledge | [r]esolve" | |
| echo " - SERVICE KEY: unique identifier for service" |
| .terraform/ | |
| *.pem | |
| *.tf | |
| *.tfstate | |
| *.yaml | |
| *.backup | |
| istio-*/ | |
| cert-manager-*/ | |
| *.swp | |
| env |
| #!/bin/bash | |
| # | |
| # Script semi-automating the process of adding LetsEncrypt certificates to | |
| # serve Acquia staging sites in HTTPS. | |
| # See http://blog.dcycle.com/blog/2018-10-05/https-acquia-stage/ | |
| # | |
| set -e | |
| BASE="$PWD" |
| # Check which version of sed is used when you run the `sed` command | |
| # The version that ships with Mac OS X is | |
| # /usr/bin/sed | |
| which sed | |
| # Install gnu-sed using Homebrew | |
| # The `--with-default-names` option configures `sed` to use gnu-sed | |
| # Without that option, you'll need to type `gsed` to use gnu-sed | |
| brew install --default-names gnu-sed |
| Ansible playbook to setup HTTPS using Let's encrypt on nginx. | |
| The Ansible playbook installs everything needed to serve static files from a nginx server over HTTPS. | |
| The server pass A rating on [SSL Labs](https://www.ssllabs.com/). | |
| To use: | |
| 1. Install [Ansible](https://www.ansible.com/) | |
| 2. Setup an Ubuntu 16.04 server accessible over ssh | |
| 3. Create `/etc/ansible/hosts` according to template below and change example.com to your domain | |
| 4. Copy the rest of the files to an empty directory (`playbook.yml` in the root of that folder and the rest in the `templates` subfolder) |
By default the PLDT HOME FIBR AN5506-04-FA RP2616 comes only with limited settings.
Hidden from the web interface are the rest of the router's capabilities and advanced settings.
We just need to enter the right url for the settings you're looking for.
We need to be logged in before we can do anything else, use your defined password if you already set the admin password.
Source: https://gist.github.com/g0tmi1k/7476eec3f32278adc07039c3e5473708
Improved (Ruby) exploit ~ http://github.com/dreadlocked/Drupalgeddon2/ // https://www.exploit-db.com/exploits/44449/
| <?php | |
| # Fill our vars and run on cli | |
| # $ php -f db-connect-test.php | |
| $dbname = 'name'; | |
| $dbuser = 'user'; | |
| $dbpass = 'pass'; | |
| $dbhost = 'host'; | |
| $connect = mysql_connect($dbhost, $dbuser, $dbpass) or die("Unable to Connect to '$dbhost'"); |
| #!/usr/bin/env bash | |
| # this can be useful when developing against a custom DNS server, or | |
| # for example, if you made a change to the DNS settings of a domain, and you | |
| # know the authoritative nameserver IP address for a domain, you could use this | |
| # to bypass the intermediate DNS cache, and apply an HTTP request using the new | |
| # DNS settings supplied by your specified (authoritative) nameserver | |
| curl --dns-servers <dns.ip,dns.ip> url.com |
| --- | |
| # ^^^ YAML documents must begin with the document separator "---" | |
| # | |
| #### Example docblock, I like to put a descriptive comment at the top of my | |
| #### playbooks. | |
| # | |
| # Overview: Playbook to bootstrap a new host for configuration management. | |
| # Applies to: production | |
| # Description: | |
| # Ensures that a host is configured for management with Ansible. |