NPAPI退休和数字签名的未来 [英] NPAPI retirement and the future of digital signature

问题描述

据我了解，浏览器的公司不感兴趣哪些使用智能卡，小应用程序等，再应用。所以，我想问你们有关，你会从现在开始，然后服用无NPAPI的办法。

I understand that browser's companies are not interested about the applications which use Smart Cards, applets, etc, anymore. So, I'd like to ask you guys about the approach that you will be taking from now and then without NPAPI.

在我的公司，我们正在开发一个新的应用程序，它基本上是数字签名机密文件，我们都害怕它，并在此NPAPI小说的nextS步骤。现在，只需Chrome的删除此Netscape浏览器插件，但我知道其他浏览器都计划很快相同。我们将回到桌面应用程序，以数字签名的文件？

In my company we are developing a new app which is basically digitally sign confidential documents and we are afraid of it and the nexts steps on this NPAPI novel. For now, just Chrome is removing this netscape plugin, but I know the other browsers are planning the same soon. Will we be back to desktop apps in order to sign documents digitally?

感谢。

推荐答案

2 FireBreath将允许你写在NPAPI和ActiveX的作品，或通过本地消息传递插件;它越来越接近准备进入测试阶段。它没有任何真正的绘图支持，但会为你工作描述一下。安装过程是一个有点痛，但它的作品。

FireBreath 2 will allow you to write a plugin that works in NPAPI, ActiveX, or through Native Messaging; it's getting close to ready to go into beta. It doesn't have any kind of real drawing support, but would work for what you describe. The install process is a bit of a pain, but it works.

这是本机的消息组件的用途可以与允许传递文本数据的任何连接使用的协议FireWyrm;应该有可能使其与在Firefox JS-ctypes的或振振有词WEB-RTC甚至CORS AJAX的以某种方式工作。现在我们需要解决的唯一的事情就是浏览器，但是我们做到了的方式，应该是pretty移植到其他技术。

The FireWyrm protocol that the native messaging component uses could be used with any connection that allows passing text data; it should be possible to make it work with js-ctypes on firefox or plausibly WEB-RTC or even CORS AJAX in some way. For now the only thing we needed to solve was Chrome, but we did it in a way that should be pretty portable to other technologies.

检查freenode上的#firebreath IRC频道，如果你想帮助与努力。

Check the #firebreath IRC channel on freenode if you want to help with the effort.

这篇关于NPAPI退休和数字签名的未来的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！