cập nhật 1 giờ trước

⏱ Độ trễ thật của tab này: trung bình 6.8 giờ sau khi CVE được công bố (n = 5478, sớm nhất 0.1 giờ). Số âm nghĩa là ta thấy trước ngày công bố.

20
BenchProctor 2026.11.16: a smaller public SAST benchmark
💥 Lỗ hổng / Exploit oss-security 2 ngày trước

Posted by info on Nov 16 Hi oss-security, I maintain BenchProctor, an Apache-2.0 corpus for evaluating static application security scanners. Release 2026.11.16 replaces the July corpus, which I withdrew after finding bad safe labels and cases whose modeled flow was unrealis…

🅱 hạng B
20
What Replaces SRM and vSphere Replication on Proxmox?
🛡️ Tin bảo mật Proxmox Forum 3 ngày trước

Hi Everyone, Disaster recovery keeps coming up with folks moving off VMware, usually as some version of "what replaces SRM?" We've answered pieces of this in threads for years, so we finally sat down and wrote the whole thing up properly. Mapping VMware DR Fe…

🅱 hạng B
20
Ceph network setup for Wan rbd replication
🛡️ Tin bảo mật Proxmox Forum 4 ngày trước

Hello, Anyone has some practical docs on network connectivity required for ceph rbd replication? Let's assume I have a dedicated lacp group for internal cluster communication (all the private traffic+ceph client net there) and another one for "production traffic a…

🅱 hạng B
20
Meinung Disaster Recovery Konzept
🛡️ Tin bảo mật Proxmox Forum 6 ngày trước

Hallo zusammen, ich hocke momentan an einem Konzept für ein Disaster Recovery zwischen zwei Standorten. Mich würde mal interessieren, ob meine Idee so umgesetzt werden kann, und was eure Meinung dazu ist. Folgendes Szenario: Standort A und Standort B. Beide Cluster s…

🅱 hạng B
20
Proxmox VE - disaster recovery (equivalent to VMware's SRM)
🛡️ Tin bảo mật Proxmox Forum 6 ngày trước

Hello, We currently have a VMware environment, using vCenter, ESXi clusters and SRM as DR solution (DR between two datacenters in separate locations). We use SRM in combination with synchronous replication on storage level (array based replication). We are considering Prox…

🅱 hạng B