Django documentation says to use:
WSGIScriptAlias / /path/to/mysite.com/mysite/wsgi.py
WSGIPythonPath /path/to/mysite.com
<Directory /path/to/mysite.com/mysite>
<Files wsgi.py>
Require all granted
| #!/bin/sh | |
| # | |
| # PR validator: This script will checkout Maven, apply a PR, build the Maven distribution and | |
| # run the Maven integration tests against the just-built distribution. If you | |
| # successfully get to the end of this script then your PR is ready to be reviewed. | |
| # Assumptions: | |
| # 1) You have a functioning version of Maven installed (script tested with 3.2.1) | |
| # 2) You have a decent connection. This script checks out everything from scratch and downloads | |
| # everything into a clean local repository. Not terribly efficient but makes sure there is no |
Django documentation says to use:
WSGIScriptAlias / /path/to/mysite.com/mysite/wsgi.py
WSGIPythonPath /path/to/mysite.com
<Directory /path/to/mysite.com/mysite>
<Files wsgi.py>
Require all granted
| #! /usr/bin/python | |
| import sys | |
| import ldap | |
| from ldap.controls import SimplePagedResultsControl | |
| from distutils.version import LooseVersion | |
| # Check if we're using the Python "ldap" 2.4 or greater API | |
| LDAP24API = LooseVersion(ldap.__version__) >= LooseVersion('2.4') |
#256 colors in putty, tmux/screen and vim There is a detailed answer on stackoverflow. If you are looking for a short one, here it is.
putty
Set Connection -> Data -> Terminal-type string to xterm-256color
tmux
Add this line to ~/.tmux.conf
| <web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee" | |
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | |
| xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee | |
| http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd" | |
| version="3.1"> | |
| </web-app> |
jq will sort (-S) the whole file (.) and compare STDOUT (<()) with diff
diff <(jq -S . A.json) <(jq -S . B.json)
| #!/usr/bin/env python2 | |
| # NOTE: this script was created for educational purposes to assist learning about kerberos tickets. | |
| # Likely to have a few bugs that cause it to fail to decrypt some TGT or Service tickets. | |
| # | |
| # Recommended Instructions: | |
| # Obtain valid kerberos tickets using Rubeus or mimikatz "sekurlsa::tickets /export" | |
| # Optionally convert tickets to ccache format using kekeo "misc::convert ccache <ticketName.kirbi>" | |
| # Obtain appropriate aes256 key using dcsync (krbtgt for TGT or usually target computer account for Service Ticket) | |
| # Run this script to decrypt: | |
| # ./decryptKerbTicket.py -k 5c7ee0b8f0ffeedbeefdeadbeeff1eefc7d313620feedbeefdeadbeefafd601e -t ./[email protected][email protected] |