大蝉 – 大蝉's Blog

有CDN的情况下让nginx获取真实IP

By default, Cloudflare acts as a reverse proxy. As such, all connections to your origin web server come from Cloudflare IP addresses, and there are some issues that you need to aware of:

If your web application is using the originating IP of the visitor as part of its logic, it will now use a Cloudflare IP address instead
If you use the content of your access logs, they now contain a Cloudflare IP address as the $remote_addr

However, Cloudflare follows industry standards and includes the visitor’s IP address in the X-Forwarded-For header. We also add a CF-Connecting-IP header that may be used as well. You can use these headers to either restore the originating IP of your visitor for your web application or to be include it in your logs.

Restoring the original visitor IP for your web application

Please use the following Nginx module and the following configuration parameters:

set_real_ip_from 103.21.244.0/22;
set_real_ip_from 103.22.200.0/22;
set_real_ip_from 103.31.4.0/22;
set_real_ip_from 104.16.0.0/12;
set_real_ip_from 108.162.192.0/18;
set_real_ip_from 131.0.72.0/22;
set_real_ip_from 141.101.64.0/18;
set_real_ip_from 162.158.0.0/15;
set_real_ip_from 172.64.0.0/13;
set_real_ip_from 173.245.48.0/20;
set_real_ip_from 188.114.96.0/20;
set_real_ip_from 190.93.240.0/20;
set_real_ip_from 197.234.240.0/22;
set_real_ip_from 198.41.128.0/17;
set_real_ip_from 2400:cb00::/32;
set_real_ip_from 2606:4700::/32;
set_real_ip_from 2803:f800::/32;
set_real_ip_from 2405:b500::/32;
set_real_ip_from 2405:8100::/32;
set_real_ip_from 2c0f:f248::/32;
set_real_ip_from 2a06:98c0::/29;
# use any of the following two
real_ip_header CF-Connecting-IP;
#real_ip_header X-Forwarded-For;

set_real_ip_from 103.21.244.0/22;

set_real_ip_from 103.22.200.0/22;

set_real_ip_from 103.31.4.0/22;

set_real_ip_from 104.16.0.0/12;

set_real_ip_from 108.162.192.0/18;

set_real_ip_from 131.0.72.0/22;

set_real_ip_from 141.101.64.0/18;

set_real_ip_from 162.158.0.0/15;

set_real_ip_from 172.64.0.0/13;

set_real_ip_from 173.245.48.0/20;

set_real_ip_from 188.114.96.0/20;

set_real_ip_from 190.93.240.0/20;

set_real_ip_from 197.234.240.0/22;

set_real_ip_from 198.41.128.0/17;

set_real_ip_from 2400:cb00::/32;

set_real_ip_from 2606:4700::/32;

set_real_ip_from 2803:f800::/32;

set_real_ip_from 2405:b500::/32;

set_real_ip_from 2405:8100::/32;

set_real_ip_from 2c0f:f248::/32;

set_real_ip_from 2a06:98c0::/29;

# use any of the following two

real_ip_header CF-Connecting-IP;

#real_ip_header X-Forwarded-For;

That list of prefixes needs to be updated regularly, and we publish the full list in Cloudflare IP addresses.
Including the original visitor IP in your logs

You can include the variables $http_cf_connecting_ip and $http_x_forwarded_for in the log_format directive.

Also see: Cloudflare and Nginx

MacOS进程报错accept: too many open files解决方法

It seems like there is an entirely different method for changing the open files limit for each version of OS X!

For OS X Sierra (10.12.X) you need to:

1. Create a file at /Library/LaunchDaemons/limit.maxfiles.plist and paste the following in (feel free to change the two numbers (which are the soft and hard limits, respectively):

&lt;?xml version="1.0" encoding="UTF-8"?&gt;  
&lt;!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"  
"http://www.apple.com/DTDs/PropertyList-1.0.dtd"&gt;
&lt;plist version="1.0"&gt;  
&lt;dict&gt;
&lt;key&gt;Label&lt;/key&gt;
&lt;string&gt;limit.maxfiles&lt;/string&gt;
&lt;key&gt;ProgramArguments&lt;/key&gt;
&lt;array&gt;
&lt;string&gt;launchctl&lt;/string&gt;
&lt;string&gt;limit&lt;/string&gt;
&lt;string&gt;maxfiles&lt;/string&gt;
&lt;string&gt;64000&lt;/string&gt;
&lt;string&gt;524288&lt;/string&gt;
&lt;/array&gt;
&lt;key&gt;RunAtLoad&lt;/key&gt;
&lt;true/&gt;
&lt;key&gt;ServiceIPC&lt;/key&gt;
&lt;false/&gt;
&lt;/dict&gt;
&lt;/plist&gt;

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"

"http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<dict>

<key>Label</key>

<string>limit.maxfiles</string>

<key>ProgramArguments</key>

<array>

<string>launchctl</string>

<string>limit</string>

<string>maxfiles</string>

</array>

<key>RunAtLoad</key>

<true/>

<key>ServiceIPC</key>

</dict>

</plist>

2. Change the owner of your new file:

sudo chown root:wheel /Library/LaunchDaemons/limit.maxfiles.plist

1 2	sudo chown root:wheel /Library/LaunchDaemons/limit.maxfiles.plist

3. Load these new settings:

sudo launchctl load -w /Library/LaunchDaemons/limit.maxfiles.plist

1 2	sudo launchctl load -w /Library/LaunchDaemons/limit.maxfiles.plist

4. Finally, check that the limits are correct:

launchctl limit maxfiles

1	launchctl limit maxfiles

goland: build constraints exclude all Go files 解决方法

原因是无法正确index引用包里的大体积文件造成

解决方法：

1.将goland.vmoptions内JMV内存限制改成

-Xmx4096m

-Xmx4096m

2.help ->edit custome properties 增加

idea.max.intellisense.filesize=999999

1	idea.max.intellisense.filesize=999999

电信光猫HG2xx超级管理员权限获取方法

测试环境：

设备基本信息

设备型号:	HG225GS
设备标识号:	xxxxxxxxxxx
硬件版本:	BCM.V2.0
软件版本:	HG225GS_D1.00_JS1606

1、在浏览器上输入 http://192.168.1.1/logoffaccount.html，设置隐藏用户改为启用，这样就可以用工程账号登陆了。

2、登录工程帐号（用户名：fiberhomehg2x0密码：hg2x0），登录网址http://192.168.1.1/

3.打开http://192.168.1.1/backupsettings.conf下载“backupsettings.conf文件”，用记事本打开，Ctrl+F查找“password”，复制<Password>标记中间一行64BASE加密的字符串。

4.telecomadmin+密码登录

frida双端安装升级

Mac:

pip install frida-tools # CLI tools
pip install frida       # Python bindings
npm install frida       # Node.js bindings

pip install frida-tools # CLI tools

pip install frida # Python bindings

npm install frida # Node.js bindings

iOS:

cydia: https://build.frida.re

Caddy无法启动报错：caddy.service: Main process exited, code=exited, status=1/FAILURE 解决方案

https://caddy.community/t/caddy-wont-start-could-not-start-http-server-for-challenge-listen-tcp-80-bind-permission-denied/2543

修改服务文件，取消以下注释：

;CapabilityBoundingSet=CAP_NET_BIND_SERVICE
;AmbientCapabilities=CAP_NET_BIND_SERVICE
;NoNewPrivileges=true

转：Caddy部署

转自：https://www.giuem.com/caddy-tutorial-for-debian/
继续阅读转：Caddy部署

转：编译可在苹果iOS设备上运行的Go语言程序

转自：link
继续阅读转：编译可在苹果iOS设备上运行的Go语言程序

开启unicorn对NEON(STP SIMD)的支持

CPACR_FPEN_MASK = (0x3 << 20)
CPACR_FPEN_TRAP_NONE = (0x3 << 20)
cpacr = mu.reg_read(UC_ARM64_REG_CPACR_EL1)
cpacr = (cpacr & ~CPACR_FPEN_MASK) | CPACR_FPEN_TRAP_NONE
mu.reg_write(UC_ARM64_REG_CPACR_EL1, cpacr)

CPACR_FPEN_MASK = (0x3 << 20)

CPACR_FPEN_TRAP_NONE = (0x3 << 20)

cpacr = mu.reg_read(UC_ARM64_REG_CPACR_EL1)

cpacr = (cpacr & ~CPACR_FPEN_MASK) | CPACR_FPEN_TRAP_NONE

mu.reg_write(UC_ARM64_REG_CPACR_EL1, cpacr)

var CPACR_FPEN_MASK uint64 = (0x3 << 20)
var CPACR_FPEN_TRAP_NONE uint64= (0x3 << 20)
cpacr, err := mu.RegRead(uc.ARM64_REG_CPACR_EL1)
if err!=nil{
panic(err.Error())
}
cpacr = (cpacr & ^CPACR_FPEN_MASK) | CPACR_FPEN_TRAP_NONE
mu.RegWrite(uc.ARM64_REG_CPACR_EL1, cpacr)

var CPACR_FPEN_MASK uint64 = (0x3 << 20)

var CPACR_FPEN_TRAP_NONE uint64= (0x3 << 20)

cpacr, err := mu.RegRead(uc.ARM64_REG_CPACR_EL1)

if err!=nil{

panic(err.Error())

}

cpacr = (cpacr & ^CPACR_FPEN_MASK) | CPACR_FPEN_TRAP_NONE

mu.RegWrite(uc.ARM64_REG_CPACR_EL1, cpacr)

IDA切换ARM和THUMB指令

ARM AND THUMB MODE SWITCH INSTRUCTIONS

This processor has two instruction encodings: ARM and THUMB.
IDA allows to specify the encoding mode for every single instruction.
For this IDA uses a virtual register T. If its value is zero, then
the ARM mode is used, otherwise the THUMB mode is used.
You can change the value of the register T using
the ‘change segment register value’ command
(the canonical hotkey is Alt-G)