| @echo off | |
| setlocal enabledelayedexpansion | |
| set ifname="ローカル エリア接続" | |
| set count=0 | |
| if "%1" equ "" ( | |
| for /F "tokens=1,2,3,4,5 delims=," %%i in (%~dp0ipset.csv) do ( | |
| set "n=00!count!" | |
| echo !n:~-2! %%i %%j |
| #!/usr/bin/env python3 | |
| from msvcrt import get_osfhandle | |
| from ctypes.wintypes import * | |
| from ctypes import * | |
| import os | |
| import struct | |
| if sizeof(c_ulong) == sizeof(c_void_p): | |
| ULONG_PTR = c_ulong | |
| elif sizeof(c_ulonglong) == sizeof(c_void_p): |
| #!/bin/bash | |
| #Run buildDJ3.sh script first in the same folder from: https://gist.github.com/aldaris/fe234d76f3940c42ae9bb5aa69b8e98e | |
| function build() { | |
| mvn clean install | |
| if [ $? -ne 0 ] ; then | |
| exit 1; | |
| fi | |
| } |
| if has('patch-8.0.0238') | |
| if &term =~ "screen" | |
| let &t_BE = "\e[?2004h" | |
| let &t_BD = "\e[?2004l" | |
| exec "set t_PS=\e[200~" | |
| exec "set t_PE=\e[201~" | |
| endif | |
| else | |
| if has('patch-8.0.0210') | |
| set t_BE= |
| #!/bin/bash | |
| DIR=/sys/devices/platform/i8042 | |
| SPEED=200 | |
| SENSITIVITY=200 | |
| modprobe -r psmouse | |
| modprobe psmouse proto=any | |
| while :; do | |
| until [ -f $DIR/serio*/serio*/speed -a -f $DIR/serio*/serio*/sensitivity ]; do | |
| sleep 1 |
Tip
Microsoft active directory servers by default provide LDAP connections over unencrypted connections (boo!).
The steps below will create a new self signed certificate appropriate for use with and thus enabling LDAPS for an AD server. Of course the "self-signed" portion of this guide can be swapped out with a real vendor purchased certificate if required.
Steps have been tested successfully with Windows Server 2012R2, but should work with Windows Server 2008 without modification. Requires a working OpenSSL install (ideally Linux/OSX) and (obviously) a Windows Active Directory server.
Putting cryptographic primitives together is a lot like putting a jigsaw puzzle together, where all the pieces are cut exactly the same way, but there is only one correct solution. Thankfully, there are some projects out there that are working hard to make sure developers are getting it right.
The following advice comes from years of research from leading security researchers, developers, and cryptographers. This Gist was [forked from Thomas Ptacek's Gist][1] to be more readable. Additions have been added from
| #!/usr/bin/env ruby | |
| # encoding: ascii-8bit | |
| # | |
| # 端末の漢字コード設定判別のサンプルスクリプト | |
| # | |
| # コンセプトとしてはUTF-8, EUC-JP, Shift_JISのどれと解釈しても正しい、 | |
| # しかしどのエンコーディングとして解釈したかで端末での表示幅が変わる | |
| # バイト列を送信し、その時のカーソル位置で端末がどのエンコーディング | |
| # として解釈したかを判別する。 | |
| # |
