@youshangdemajia GitHub 有公有云版本和私有部署版本，因为我使用不深，也不是专门在研发团队里做开发，所以不清楚实际使用中有哪些区别

m1 pro 表示这个问题只有微信语音有，外呼的时候很严重，出现频率很高

@kjstart 可以考虑一下

国内就用阿里云腾讯云，或者免费套餐的 Cloudflare ，都比国内免费的靠谱。

挂了，影响一大片

@muhuan 就没人修复吗？

@zhaidoudou123 写多了，是快速静音的意思

阿里云的后台在这个行业里算好的了，你对比看看 AWS 、AZURE ，或者看看国内的华为云、腾讯云，要知道腾讯云连 APP 都没有，移动端是小程序。。。。。

Remediation Advice:

This issue was remediated in Log4J v2.15.0. The Apache Logging Services team provides the following mitigation advice:

In previous releases (>=2.10) this behavior can be mitigated by setting system property "log4j2.formatMsgNoLookups" to “true” or by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class). Java 8u121 protects against RCE by defaulting "com.sun.jndi.rmi.object.trustURLCodebase" and "com.sun.jndi.cosnaming.object.trustURLCodebase" to "false".

You can manually check for use of affected versions of Log4J by searching your project repository for Log4J use, which is often in a pom.xml file.

Where possible, upgrade to Log4J version 2.15.0. If you are using Log4J v1 there is a migration guide available.

Please note that Log4J v1 is End Of Life (EOL) and will not receive patches for this issue. Log4J v1 is also vulnerable to other RCE vectors and we recommend you migrate to Log4J 2.15.0 where possible.

If upgrading is not possible, then ensure the -Dlog4j2.formatMsgNoLookups=true system property is set on both client- and server-side components.

@dangyuluo just like xshell, or even better than xhsell

不可能广泛使用，术业有专攻，将不同的软件和技术用到一起的集大成者才是王道

内地学校的学生，是怎么在澳门的线下商店购买的？

前几天的事了，收发之后的大批量到货，现在在在线商店下单 12 月初就可以配送了，也就是 10 天左右，跟之前 3-7 天差不多了。