wushuzh

Results 25 comments of wushuzh

我用证书登录遇到相同的问题: - 在宿主机 ubuntu 系统可以,导入证书,接入 vpn ok - 在容器 GUI 中,可以导入证书,接入 vpn ok - 在容器 CLI 中,交互模式,输入证书路径,以及证书密码,报错 `import certificate failed, reaseon: !` 容器内 /usr/share/sangfor/EasyConnect/resources/user_cert 目录首先要存在,无论是挂载外部文件夹,还是到容器内部 mkdir 创建(这个是否应该修改一下目前的 Dockerfile ,强制创建一下?权限上是否必须有写权限?) 启动...

使用 openssl 从 p12 文件中,分离出私钥文件,在容器交互提示中输入该文本文件挂载到容器中的完整路径,日志中仍然显示 ImportCertCommon, Failed to Base64Decode for filePath: xxxx (p12 full path name within container)

[用法说明](https://github.com/Hagb/docker-easyconnect/blob/master/doc/usage.md#%E4%BB%85%E9%80%82%E7%94%A8%E4%BA%8E%E7%BA%AF%E5%91%BD%E4%BB%A4%E8%A1%8C%E7%89%88%E6%9C%AC%E7%9A%84%E7%8E%AF%E5%A2%83%E5%8F%98%E9%87%8F)中,命令行版本的各个参数含义的提示是怎么得到的? ``` -d vpn address, make sure it's assigned and the format is right, like "199.201.73.191:443" -t login type, "pwd" means username/password authentication "cert" means certificate authentication -u username -p...

对比一下 docker VNC 手工选择证书,正确导入的日志: ``` [2022-04-19 03:14:21][I][ 167][CheckCertType][Agent] get import cert type is : 0. [2022-04-19 03:14:21][I][1561][CheckPk12CertValid][CheckPk12CertValid] serialNumberHexCString:(XXXXXXXXXXXXXXXXX) serialNumberHexCStringLen:YY [2022-04-19 03:14:21][I][1580][CheckPk12CertValid][CheckPk12CertValid] issuer common name: (ZZZZ)(MMMMMMMMMMMMMM), issuer len:NN [2022-04-19 03:14:21][I][1599][CheckPk12CertValid][CheckPk12CertValid] subject...

launch cmd: ``` docker run --device /dev/net/tun --cap-add NET_ADMIN --name vpn --rm \ -v /root/.config/EasyConnect/upload_cert/:/root/upload_cert -ti \ -p 127.0.0.1:1080:1080 -p 127.0.0.1:8888:8888 -e EC_VER=7.6.7 \ -e CLI_OPTS="-d https://myvpn -t cert -c...

swap values of option `c` and option `l`, and launch the cmd again: ``` docker run --device /dev/net/tun --cap-add NET_ADMIN --name vpn --rm \ -v /root/.config/EasyConnect/upload_cert/:/root/upload_cert \ -ti -p 127.0.0.1:1080:1080...

看最后一次这次 ECAgent 日志,通过参数 c 传入私钥 pem 文件后,开始做证书类型的判定了,还有什么方法从这里继续排查么?任何打开更细粒度的日志的方法? 或者通过 gdb 启动 ECAgent ,咱们有可能获得更多信息么? start-sangfor.sh 中有一个 fake-hwaddr-run 的程序,是什么作用?

launch container with `--cap-add=SYS_PTRACE`, then `apt install strace`. ``` root@24b8fa6543fd:~# ps -ef|grep ECA 57 root /usr/share/sangfor/EasyConnect/resources/bin/ECAgent 917 root tail -f ECAgent.log 5420 root grep ECA root@24b8fa6543fd:~# root@24b8fa6543fd:~# root@24b8fa6543fd:~# strace -p...

开启日志级别到 6 后, ECAagent 的日志: ``` [2022-04-20 10:12:19][D][ 291][main][main] init... [2022-04-20 10:12:19][D][ 33][RunWebServer][main][Enter] [2022-04-20 10:12:19][V][ 81][Lock][FileLock] file lock failed [2022-04-20 10:12:19][E][ 38][RunWebServer][main] there is another ecagent web server is running...