Passwork Comparison with OneKey Sparks Detailed Rebuttal from ABP2B on Security Claims
Passwork recently published an article comparing its corporate password manager with OneKey from ABP2B. The comparison used OneKey version 2.0.7 with simplified settings focused on convenience, even though version 2.1.0 was already available at the time of publication.
ABP2B expressed skepticism about vendor-led technical comparisons, noting the risk of emphasizing own advantages while overlooking competitor strengths. After the review, the company released a significant update that included reworked authorization, additional protection for formatted text display, expanded cache management parameters, new group policies, strengthened server-side security policy checks, and changes to hash storage rules.
The comparison examined corporate password managers with additional protection parameters enabled in Passwork and lighter settings in OneKey. ABP2B argued that the existence of an optional simplified access scenario does not mean organizations must use it.
Key technical points raised
- A single master password creates one point of compromise affecting all user vaults, whereas OneKey uses independent secrets per vault to limit breach impact.
- The description of Shamir's Secret Sharing in the article was incorrect: the scheme splits the recovery private key, not the master password, requiring multiple responsible employees for restoration.
- Comparing 300,000 PBKDF2 iterations against 1,000 does not fully reflect system strength without considering the hash function, implementation details, and master password complexity.
- OneKey defaults to GOST 34.12-2018 for the Russian market but allows clients to select other supported algorithms such as AES-256 when required by infrastructure or policy.
- Compromised password checking is presented only as a risk in the article, yet it serves as an optional protective feature that organizations can enable or disable based on their threat model.
- Simplified access options such as PIN codes or no-additional-password mode are configurable and can be restricted through group policies.
Related articles
How a Personal Site Counts Bots Without Storing Any IPs: Pure PHP, No Database, Strict CSP and 160 Tests
A personal website built entirely in pure PHP without frameworks or databases demonstrates advanced defensive security practices while tracking bot activity from an SSH honeypot. The site stores all content in a single JSON file with atomic writes and automatic backups, eliminating database-related attack surfaces and simplifying deployment to folder copying. Strict Content-Security-Policy rules prohibit inline styles and scripts without nonces, forcing the use of SVG attributes, CSSOM updates, and JSON data blocks instead of direct attribute injection. Over 160 automated tests written in PHP attack the site with XSS payloads, CSRF attempts, path traversals, and malformed Markdown to verify that no malicious output reaches the browser. Bot identification relies on behavioral signatures derived from the first twelve cleaned commands of each session, combined with HASSH fingerprints and activity patterns, allowing the site to report unique bot families and address counts without ever publishing IPs. Additional browser-based tests using Chromium validate accessibility, performance budgets, and CSP compliance across desktop and mobile viewports. The entire system runs with zero external dependencies and integrates tests directly into the deployment pipeline.
Russian Finance Ministry Seeks Central Bank Reports on Systematic P2P Transfers to Tax Authorities
The Russian Ministry of Finance has proposed amendments requiring the Central Bank to share data with the Federal Tax Service on individuals whose bank accounts show signs of regular income received from other private citizens. The changes target article 85 of the Tax Code and form part of the budget package bill numbered 617-9. Under the new rules, the Central Bank would identify such citizens through transaction analysis and transmit the information according to a future agreement with the tax service. The Federal Tax Service would also gain expanded powers to request bank statements from non-entrepreneurs without needing prior debt collection or audit triggers. If approved, the provisions would take effect on 1 January 2027 and apply to operations conducted after 1 January 2026. Separate bills under discussion would impose monthly transfer limits of 30,000 rubles on suspected clients starting in 2028 and require the tax service to notify the Central Bank about account openings and income categories.
Baidu Launches Ciyuan Exchange to Establish Trust Standards for AI Model Trading
Baidu Intelligent Cloud has introduced the Ciyuan Exchange, a dedicated trading platform for large AI models that aims to solve quality verification and credit issues in an increasingly crowded market. The platform, unveiled at the Baidu World 2026 Conference, already hosts over 100 supply resources with daily calls exceeding 50 million and daily token usage surpassing 700 billion. Founder Li Yanhong positioned the exchange as an infrastructure layer that moves beyond simple model aggregation toward verifiable identity, ongoing performance monitoring, and supplier credit records. The initiative addresses real procurement risks where identical models from different providers show up to twofold differences in throughput and reliability, according to a China Academy of Information and Communications Technology report. By combining model fingerprinting, capability testing, periodic audits, and continuous credit scoring, the platform seeks to create transparent market mechanisms similar to commodity exchanges. This development signals a broader industry shift from raw model capability competition toward standardized service quality, pricing transparency, and reliable delivery infrastructure.
Windows and MacBook Pro Setup Combines Local Network Access with Dual VPNs and Kill Switch Protection
A user detailed how they integrated an older MacBook Pro into an existing Windows workstation environment while preserving separate user accounts, file sharing, and independent VPN connections. The setup required careful routing configuration to keep the Kill Switch active on both Amnezia VLESS and AmneziaWG without breaking local SMB connectivity. After initial failures caused by the Windows Kill Switch blocking the 192.168.1.0/24 subnet, split tunneling was implemented to route local traffic directly. Separate macOS accounts were created for daily use and a dedicated “Serverok” account for remote scripting and compute tasks. SSH and SFTP ultimately replaced problematic SMB shares for the secondary account, enabling reliable file transfers at over 50 MB/s. The configuration allows simultaneous or sequential use of both machines while maintaining strong VPN protection on each.