ELAI Chip Bridge

Browser bridge for chip-card identity verification on ELAI sites. Talks to your USB reader via Chrome Native Messaging.

用户数0

评分--

评论数0

Manifest 版本V3

7日增长--

7日增长率--

视觉预览

ELAI Chip Bridge 媒体预览

3 项素材

趋势

30 日用户趋势

查看最近 30 天的用户变化。

用户增长趋势

评分趋势

30 日评分变化

按时间查看评分波动，辅助判断近期口碑是否稳定。

评分趋势样本还不够，后续快照会继续补齐。

增长概览

日/周/月增长表现

同口径展示 1 天、7 天、30 天的绝对增长与增长率。

1日增长持平

0--

7日增长暂无数据

----

30日增长暂无数据

----

技术摘要

版本、语言与抓取信息

查看发布时间、版本、支持语言、最近更新和抓取时间。

版本1.0.0

ManifestV3

大小10.75KiB

语言数1English

发布时间--

插件简介

查看插件说明、主要功能和适用场景。

The ELAI Chip Bridge lets verifythecard.com, americafirst4us.com, and other ELAI ecosystem websites talk to the chip card in your USB smart-card reader — without opening a localhost network port.

WHAT IT DOES

The extension is a sandboxed Native Messaging bridge between web pages on a small allowlist of origins (verifythecard.com, americafirst4us.com, idregulators.com, idregulars.com, 4pdfs.com) and a local Python helper that talks to your reader via the operating system's PC/SC smart-card subsystem.

When a verifythecard.com page asks "is the chip card in the reader real?", the request flows through the Chrome Native Messaging pipe to the local helper, which runs an ISO 7816-4 SELECT + INTERNAL AUTHENTICATE exchange and returns the result. The chip's private key never leaves the secure element.

WHY USE THE EXTENSION INSTEAD OF A LOCALHOST HELPER?

Earlier ELAI tooling opened a localhost HTTP port to talk to the reader. That works, but it's an attack surface — any tab in any browser can probe it. The Native Messaging architecture eliminates that completely:

评价