TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Digging into Quebec's electronic proof of vaccination

80 点作者 gozmike将近 4 年前

6 条评论

rocqua将近 4 年前
The underlying cryptographic technology here: &quot;Verifiable Credentials&quot; is quite exciting. If you have ever wondered &quot;why aren&#x27;t bureaucracies using digital signatures?&quot; then VCs are interesting.<p>It&#x27;s a pretty decent technical spec for signing statements like &quot;This person has this age&quot; or &quot;this person is vaccinated&quot; or &quot;this person is authorized for this bank-account as executor of a will&quot;. It is a spec written by cryptographers and hackers.<p>At the same time, it is a spec being used by banks, governments, and health-care. That is, its not just a nice technical ivory tower idea, it is actually liked by people who would use it. Why do these organizations want to use this? Because, without cryptographic guarantees, your business processes involve a whole lot of bureaucracy, manual checking of data, implicit trust relations, and friction (so much friction).<p>That friction is part of why people would actually want to use it. Essentially, all you need to do to share required data is scan some QR codes. Another, maybe more important part, is control over your data. You determine who you show your VC. It is not needed for two organizations to have access to all of their shared data they need. They give the used the data, and the user hands it over, or he doesn&#x27;t.<p>The general concept behind all of this is sometimes called SSI (Self Sovereign Identity).
评论 #27356885 未加载
评论 #27363968 未加载
jefft255将近 4 年前
Québec&#x27;s government has historically been incompetent regarding anything digital (a lot of their website are still barely usable), but I want to give credit where credit is due: their vaccine appointment website as well as their proof-of-vaccination has been really well done.
评论 #27357600 未加载
评论 #27356313 未加载
评论 #27355252 未加载
评论 #27357339 未加载
评论 #27356697 未加载
评论 #27357922 未加载
评论 #27355077 未加载
评论 #27358517 未加载
motohagiography将近 4 年前
I&#x27;m surprised to be out of the loop on this. This is the first I&#x27;ve heard of Quebec&#x27;s vaccine passports. As the OP says, it also implies there is an app, with a vendor, an infrastructure, and key management. (smarthealthit and azure as it appears to turn out)<p>The ethics and legality of vaccine passports are still very controversial, and using Quebec as a test ground for it seems like its part of an inevitable push, independent of popular assent to it. It&#x27;s force, basically.<p>Using a JWT is sufficient for the purposes, and the vaccination status is basically a digital ID. This provides some mature and flexible structure to the token format, as opposed to say, a blockchain based one. The scanning app with the URI endpoints is going to be the interesting piece.<p>Having worked in the design of related concept, the main failure modes here are a compromise of the signing key which is probably in an azure HSM instance, or cached somewhere as just a k8s secret, mobile malware that steals or corrupts tokens, and then infrastructure ddos against that API endpoint during a holiday airline rush. There&#x27;s also the question of how the code verification app works, as that&#x27;s where the real vulnerabilites would be.<p>Given the amount of co-ordination required for a scheme like this to work, it is difficult to believe this is not being done in secret, and if so, why?
评论 #27359574 未加载
评论 #27359774 未加载
gregsadetsky将近 4 年前
There&#x27;s a nice JavaScript&#x2F;node version of the decoding code that you can run locally on the shc:&#x2F;... QR code value here:<p><a href="https:&#x2F;&#x2F;gist.github.com&#x2F;remi&#x2F;e3aa2f78845ee13f706ed83aead5145f" rel="nofollow">https:&#x2F;&#x2F;gist.github.com&#x2F;remi&#x2F;e3aa2f78845ee13f706ed83aead5145...</a><p>There&#x27;s also an online version (that works on mobiles and desktops) and decodes everything on the client side:<p><a href="https:&#x2F;&#x2F;fproulx.github.io&#x2F;shc-covid19-decoder&#x2F;" rel="nofollow">https:&#x2F;&#x2F;fproulx.github.io&#x2F;shc-covid19-decoder&#x2F;</a>
JoshMandel将近 4 年前
For reference, the SMART Health Cards Framework (<a href="https:&#x2F;&#x2F;spec.smarthealth.cards" rel="nofollow">https:&#x2F;&#x2F;spec.smarthealth.cards</a>) is the underlying specification behind these QRs. I&#x27;ve had the privilege of working with a broad swath of the healthcare IT ecosystem (in the US and internationally) on these openly licensed, standards-based specifications for consumer access and data sharing.<p>The SMART Health Cards Framework is designed to dovetail with SMART on FHIR APIs for consumer access (which all Electronic Health Record vendors in the US are on the hook to support over the next year).
bjt2n3904将近 4 年前
So... looks like it&#x27;s using ES256. How long would it take to factor the private key?
评论 #27357004 未加载
评论 #27356825 未加载