Microsoft Disables PC-to-PC Migration in Windows 11, Pushes OneDrive Backup Instead

Major Beget Outage Leaves Clients Without Websites, VPS, and Control Panel Access

On the morning of November 2, clients of Russian hosting provider Beget experienced widespread service disruptions starting around 04:50 Moscow time. The outage affected the control panel, personal accounts, virtual private servers, email services, and DNS resolution across multiple infrastructure layers. Beget acknowledged the incident through its official channel and stated that engineers were manually restoring systems directly in data centers while investigating the root cause. Among the impacted resources was the official website of Russia’s product marking system Chestny Znak. Users reported 502 Bad Gateway errors, inaccessible hosted sites, and VPS connectivity failures. The provider has not yet provided an estimated time for full recovery or disclosed whether the incident involved any security compromise.

Evidencestore Provides Cryptographic Proof That Deleted Log Lines Once Existed

Evidencestore is an open-source Go project that acts as an independent witness for system logs, allowing investigators to prove that specific log entries existed at a certain time even after an attacker deletes them from the source server. The system uses hash chains, Merkle trees, external timestamp authorities, and forward-secure mechanisms to create verifiable evidence packages that can be checked offline without trusting the storage operator. In a demonstration, four lines showing a root login attempt from 203.0.113.7 and subsequent malicious commands were erased using sed -i, yet the remote store retained byte-for-byte copies with cryptographic proofs. The collector component handles complex file rotation, inode tracking, and logrotate scenarios to ensure no lines are lost or renumbered. Time is anchored to RFC 3161 timestamps rather than local clocks, and signed heads can be replicated to external Object Lock storage to resist even the storage owner. The project addresses limitations of traditional SIEM systems and hash chains by enabling skeptical third-party verification.

Building Fault-Tolerant DoH on MikroTik RouterOS to Avoid Unreachable Cloudflare Responses

A network administrator encountered a puzzling issue in a branch network where pages using Tailwind CSS from CDN would timeout despite valid DNS resolutions through DoH. The problem stemmed from Cloudflare returning IP addresses like 8.6.112.0 and 8.47.69.0 that had no reachable route from the affected network segment. RouterOS supports only a single active DoH upstream, requiring custom scripting to implement failover between multiple endpoints while maintaining HTTPS encryption and certificate verification. Early script versions failed by checking only response types instead of content validity, temporarily disabling DoH during probes, and falling back to plain DNS that delivered spoofed answers. The refined solution uses static bootstrap entries, JSON API probes with proper timeouts, hysteresis thresholds for state transitions, and verification against known stub prefixes. Certificate trust anchors had to be manually addressed because builtin-trust-store does not cover the SSL.com root used by Cloudflare. The final monitor script runs every 60 seconds, checks date validity to prevent certificate failures, and limits switch attempts to avoid log flooding while ensuring the backup endpoint is tested before and after any transition.