<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Standards on CuraSec</title><link>https://curasec.metacog.co.kr/tags/standards/</link><description>Recent content in Standards on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 10 Aug 2026 13:39:41 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/standards/index.xml" rel="self" type="application/rss+xml"/><item><title>Tight Security Proofs for BBS Signatures Closed by New Research</title><link>https://curasec.metacog.co.kr/insights/2026-08-10-tight-security-for-bbs-signatures/</link><pubDate>Mon, 10 Aug 2026 13:39:41 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-10-tight-security-for-bbs-signatures/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> BBS signatures underlie privacy-preserving authentication systems being standardized by W3C and IRTF; this paper closes a tightness gap in their security proof, which may affect future scheme selection (BBS vs BBS+) when implementing such systems — no change to running systems required today.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>