vlinx-io

“立即采集”引擎分流增量补丁

这是在上一版 Huawei USG OID/SNMP 修复之后安装的增量补丁，只修复：

• 页面点击“立即采集”时，按 collectorDefinitionId 正确分流；
• 已迁移监控项走配置化 CollectionEngine；
• 未迁移监控项继续走 idcos；
• 无启用监控项时返回明确错误，不再假提交。

在 VLX-OPS-X 源码仓库根目录执行：

vlinx-io

“立即采集”引擎分流增量补丁

这是在上一版 Huawei USG OID/SNMP 修复之后安装的增量补丁，只修复：

• 页面点击“立即采集”时，按 collectorDefinitionId 正确分流；
• 已迁移监控项走配置化 CollectionEngine；
• 未迁移监控项继续走 idcos；
• 无启用监控项时返回明确错误，不再假提交。

在 VLX-OPS-X 源码仓库根目录执行：

vlinx-io

Huawei USG 采集修复包

本补丁修复以下问题：

1. “立即采集”只调用旧 idcos、绕过配置化采集器，接口返回成功但没有指标。
2. Huawei USG 多个表型 OID 被错误地当作标量 GET。
3. 部分标量 OID 缺少 .0，查询键与指标提取键不一致。
4. SNMPv1 批量 GET 遇到不支持的 OID 时整包失败，现降级为逐项 GET。
5. 大型 SNMP 设备默认启用批量取值，避免单轮采集耗时过长。

vlinx-io

NativeImage Reverse Engineering

Restoring and protecting Java code is an old and often-discussed issue. Due to the byte-code format used to store Java class files, which contains a lot of meta-information, it can be easily restored to its original code. In order to protect Java code, the industry has adopted many methods, such as obfuscation, bytecode encryption, JNI protection, and so on. However, regardless of the method used, there are still ways and means to crack it.

Binary compilation has always been considered as a relatively effective method of code protection. Java's binary compilation is supported as AOT (Ahead of Time) technology, which means pre-compilation.

However, due to the dynamic nature of the Java language, binary compilation needs to handle issues such as reflection, dynamic proxy, JNI loading, etc., which poses many difficulties. Therefore, for a long time, there has been a lack of a mature, reliable, and adaptable tool for AOT compilation in Java that can be widely applied in p