kp3 吧，感觉缝小一些，不易进灰。

@coolloves nginx 就加了个 301
nginx listen 80;
server_name www.aaa.com aaa.com ;
add_header Strict-Transport-Security max-age=15768000;
return 301 https://www.aaa.com$request_uri;

@coolloves cache_peer 1.2.3.4 parent 80 0 no-query originserver login=PASS name=web01
这样改，无法打开网页，提示重定向次数过多--

@coolloves 改成 80 的话就是下面这样
# Recommended minimum configuration:
#

# Example rule allowing access from your local networks.
# Adapt to list your (internal) IP networks from where browsing
# should be allowed
acl localnet src 10.0.0.0/8 # RFC1918 possible internal network
acl localnet src 172.16.0.0/12 # RFC1918 possible internal network
acl localnet src 192.168.0.0/16 # RFC1918 possible internal network
acl localnet src fc00::/7 # RFC 4193 local private network range
acl localnet src fe80::/10 # RFC 4291 link-local (directly plugged) machines

acl SSL_ports port 443
acl Safe_ports port 80 # http
acl Safe_ports port 21 # ftp
acl Safe_ports port 443 # https
acl Safe_ports port 70 # gopher
acl Safe_ports port 210 # wais
acl Safe_ports port 1025-65535 # unregistered ports
acl Safe_ports port 280 # http-mgmt
acl Safe_ports port 488 # gss-http
acl Safe_ports port 591 # filemaker
acl Safe_ports port 777 # multiling http
acl CONNECT method CONNECT

#
# Recommended minimum Access Permission configuration:
#
# Deny requests to certain unsafe ports
http_access deny !Safe_ports

# Deny CONNECT to other than secure SSL ports
http_access deny CONNECT !SSL_ports

# Only allow cachemgr access from localhost
http_access allow localhost manager
http_access deny manager

# We strongly recommend the following be uncommented to protect innocent
# web applications running on the proxy server who think the only
# one who can access services on "localhost" is a local user
#http_access deny to_localhost

#
# INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS
#

# Example rule allowing access from your local networks.
# Adapt localnet in the ACL section to list your (internal) IP networks
# from where browsing should be allowed
http_access allow localnet
http_access allow localhost

# And finally deny all other access to this proxy
# http_access allow all

# Squid normally listens to port 3128
visible_hostname localhost

# http_port 3128

http_port 80 accel vhost vport
https_port 443 cert=/etc/squid/ssl/123.pem key=/etc/squid/ssl/123.key accel defaultsite=www.aaa.com
ssl_unclean_shutdown on
cache_peer 1.2.3.4 parent 80 0 no-query no-digest originserver name=web01 login=PASS ssl sslflags=DONT_VERIFY_PEER front-end-https=on
acl sites_server_1 dstdomain .aaa.com
cache_peer_access web01 allow sites_server_1
http_access allow web01

# Uncomment and adjust the following to add a disk cache directory.
cache_dir ufs /var/spool/squid 10000 32 512




# Leave coredumps in the first cache dir
coredump_dir /var/spool/squid

#
# Add any of your own refresh_pattern entries above these.
#
refresh_pattern ^ftp: 1440 20% 10080
refresh_pattern ^gopher: 1440 0% 1440
refresh_pattern -i (/cgi-bin/|\?) 0 0% 0
refresh_pattern . 0 20% 4320

@coolloves
貌似不行，改了直接无法访问了
The system returned:

(71) Protocol error (TLS code: SQUID_ERR_SSL_HANDSHAKE)
Handshake with SSL server failed: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol

此代理和远端主机无法为处理您的请求在相互可接受的安全设置上协商一致。有可能远端计算机不支持安全连接，或者代理对主机的安全凭据不认可。

@wmc 666

参加一手活动看看，说不定就中了。

@ihciah 感谢感谢，我来研究一波

@ihciah 解压了，貌似没查到壳

@bearqq 那就可能是二进制，得不到明文-。-

@bearqq 确实管用，不过得出的文件打开是乱码==，不是到是什么格式的。。。

@ihciah 求问怎么解压

@bearqq 一改就没法运行了--

@linhua 这个能作用到二级目录吗，它是执行的时候在 /tmp 下新建一个 /tmp.XXXX 文件夹，然后把脚本解压其中

@linhua 这个厉害，我试试

@kmahyyg 嗯，但它也是解压到"$gztmp"这个文件夹运行了呀，就是一运行就删了，要不然就能找到解压的安装脚本了

表示这个排版有点醉