目前整个互联网环境,被破坏最严重地部分,是 Web 服务体验。当直接破坏难以实现时,就会从流程链的上下游着手,如:DNS 污染。
其它地互联网服务类型,例如:邮件,可能小部分会受到 Web 服务上下游破坏地余震,但整体上基本不受影响。
token_helper = "/Users/me/.vault-helper" |
These commands are based on a askubuntu answer http://askubuntu.com/a/581497 | |
To install gcc-6 (gcc-6.1.1), I had to do more stuff as shown below. | |
USE THOSE COMMANDS AT YOUR OWN RISK. I SHALL NOT BE RESPONSIBLE FOR ANYTHING. | |
ABSOLUTELY NO WARRANTY. | |
If you are still reading let's carry on with the code. | |
sudo apt-get update && \ | |
sudo apt-get install build-essential software-properties-common -y && \ | |
sudo add-apt-repository ppa:ubuntu-toolchain-r/test -y && \ |
用命令行调用android虚拟机里so库文件JNI接口 | |
可用于破解用native代码签名接口调用的手机应用, 而无需反编译so代码 | |
参考: https://davanum.wordpress.com/2007/12/04/command-line-java-on-dalvikvm/ | |
1.com/app/safe目录下放JNI声明文件sign.java(对应于从要破解的手机应用apk内lib文件夹内复制出的sign.so文件): | |
package com.app.safe; | |
public class sign | |
{ | |
static |
[General] | |
loglevel = notify | |
skip-proxy = 127.0.0.1, 192.168.0.0/16, 10.0.0.0/8, 172.16.0.0/12, 100.64.0.0/10, localhost, *.local, ::ffff:0:0:0:0/1, ::ffff:128:0:0:0/1 | |
bypass-tun = 192.168.0.0/16, 10.0.0.0/8, 172.16.0.0/12 | |
# dns-server = 119.29.29.29,223.5.5.5,114.114.115.115 | |
# external-controller-access = [email protected]:6155 | |
# ipv6 = true | |
// REMEMBER TO CHANGE THE external-controller-access' PASSWORD |
#Wed Feb 11 15:27:20 GMT+08:00 2015 | |
setting_froceUseQProxy=false | |
setting_forceUseSystemWebview=false |
# based on http://api.rubyonrails.org/classes/ActionController/RequestForgeryProtection.html | |
module Auth | |
extend ActiveSupport::Concern | |
included do | |
helpers do | |
def session | |
env['rack.session'] | |
end |
At the 2004 Ruby Conference, Jamis Buck had the unenviable task to explain Dependency Injection to a bunch of Ruby developers. First of all, Dependency Injection (DI) and Inversion of Control (IoC) is hard to explain, the benefits are subtle and the dynamic nature of Ruby make those benefits even more marginal. Furthermore examples using DI/IoC are either too simple (and don’t convey the usefulness) or too complex (and difficult to explain in the space of an article or presentation). I once attempted to explain DI/IoC to a room of Java programmers (see onestepback.org/articles/dependencyinjection/), so I can’t pass up trying to explain it to Ruby developers.
Thanks goes to Jamis Buck (the author of the Copland DI/IoC framework) who took the time to review this article and provide feedback.
var gulp = require('gulp'); | |
var concat = require('gulp-concat'); | |
var sass = require('gulp-sass'); | |
var minifyCss = require('gulp-minify-css'); | |
var rename = require('gulp-rename'); | |
var connect = require('gulp-connect'); | |
var paths = { | |
css: ['./www/css/**/*.css'], | |
js: ['./www/js/**/*.js'], |
# In config/initializers/sprockets.rb | |
require 'sprockets' | |
require 'sprockets/server' | |
Sprockets::Server.class_eval do | |
private | |
def headers_with_rails_env_check(*args) |