Each of these commands will run an ad hoc http static server in your current (or specified) directory, available at http://localhost:8000. Use this power wisely.
$ python -m SimpleHTTPServer 8000
using System; | |
using System.Collections.Generic; | |
using System.Linq; | |
using System.Text; | |
using System.Data.SqlClient; | |
using Dapper; | |
// to have a play, install Dapper.Rainbow from nuget |
//------------------------------------------------------------------------------ | |
// pdbdump.c - dump symbols from .pdb and executable files (public domain). | |
// - to compile; cl.exe /Ox /Zi pdbdump.c | |
// - | |
// - Martin Ridgers, pdbdump 'at' fireproofgravy.co.uk | |
//------------------------------------------------------------------------------ | |
#include <stdio.h> | |
#include <Windows.h> | |
#include <DbgHelp.h> |
Each of these commands will run an ad hoc http static server in your current (or specified) directory, available at http://localhost:8000. Use this power wisely.
$ python -m SimpleHTTPServer 8000
thanks to @neurodyne and this link for updated instructions
This works with the following versions of termsrv.dll
x64 - termsrv.dll - 6.3.9600.17095
Find | Replace |
---|---|
39813C0600000F849E310500 | B80001000089813806000090 |
090085C07F078BD8 | 090085C090908BD8 |
### Last tested February 7 2014 on a Galaxy S3 (d2att) running Cyanogenmod 11 nightly, with Google Authenticator 2.49. | |
### Device with Google Authenticator must have root. | |
### Computer requires Android Developer Tools and SQLite 3. | |
### Connect your device in USB debugging mode. | |
$ cd /tmp | |
$ adb root | |
$ adb pull /data/data/com.google.android.apps.authenticator2/databases/databases |
<?xml version="1.0" encoding="UTF-8"?> | |
<manifest> | |
<remote fetch="git://github.com/" name="gh" /> | |
<!-- Device Repos --> | |
<project name="darkspadez/android_device_lge_g3-common" path="device/lge/g3-common" remote="gh" revision="cm-11.0" /> | |
<project name="darkspadez/android_device_lge_vs985" path="device/lge/vs985" remote="gh" revision="cm-11.0" /> | |
<project name="SlimRoms/device_motorola_falcon" path="device/motorola/falcon" remote="gh" revision="kk4.4" /> | |
<project name="SlimRoms/device_motorola_ghost" path="device/motorola/ghost" remote="gh" revision="kk4.4" /> | |
<project name="SlimRoms/device_motorola_peregrine" path="device/motorola/peregrine" remote="gh" revision="kk4.4" /> |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
import os | |
import sys | |
import bencodepy | |
import humanize | |
import argparse | |
def total_size_files_torrent(file_name): | |
try: | |
parsed = bencodepy.decode_from_file(file_name) |
A. IdentityServer3 docs, samples and source code use OIDC & OAuth2 terms interchangeably to refer to same thing in many areas. I think that's make sense because OIDC introduced as complement & extension for OAuth2.
B. IdentityServer3, STS, OP, OIDC server, OAuth2 server, CSP, IDP and others: means same thing (software that provide/issue tokens to clients) as explained in [Terminology] (http://identityserver.github.io/Documentation/docs/overview/terminology.html).
C. Grants and flows mean same thing, grant was the common term in OAuth2 specs and flow is the common term in OIDC specs.
D. This document will not focus on custom flow/grant.
E. [Important] Choosing wrong flow leads to security threat.