Native chrome extension that allows OS acccess

61 views
Skip to first unread message

a a

unread,
Nov 11, 2014, 5:42:33 AM11/11/14
to chromium-...@chromium.org
Hi there.

I have read about the "native client" add-ons :

What I want to achieve (without native client though) is to allow to an extension to access the OS (in particular, I need it to access a cryptography token for digitally signing online documents).

From what I have read, this cannot be done with native client, but I have also noticed in a video that the old way (of add-ons accessing the OS) is being removed as we speak (unless I got it wrong).

Is there a way to access the OS with a digitally signed, native add-on?
And will there still be a way in the future?
If there is future in building something like this, I would appreciate some suggestions/link for getting started.

Thanks! :)

Nandu

unread,
Nov 11, 2014, 12:32:53 PM11/11/14
to chromium-...@chromium.org
you cannot have full access to OS via native client, but Nacl ports do have some extensibility.
The easy way for you is to "delegate" the responsibility to Native Message Host (NMH). NMH is not double sandboxed  and can access OS primitives

a a

unread,
Nov 12, 2014, 11:11:01 AM11/12/14
to Nandu, chromium-...@chromium.org
Thanks.
But any idea if NMH will exist in the future?
Because in the video of this page: https://developer.chrome.com/native-client
..at : 18:50
..he mentions something about "closing up direct unsandboxed access".
I am not sure if that means they will remove support from Chrome or something else.. :(


--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To post to this group, send email to chromium-...@chromium.org.
Visit this group at http://groups.google.com/a/chromium.org/group/chromium-extensions/.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/4b33e614-90d0-42fc-b552-1d83ff5181ff%40chromium.org.
For more options, visit https://groups.google.com/a/chromium.org/d/optout.

Nandu

unread,
Nov 12, 2014, 1:14:32 PM11/12/14
to chromium-...@chromium.org, nka...@gmail.com
The part you reference is in context of NPAPI plugins, which does have un-sandboxed access to system.
While the Native applications do run in un-sandboxed mode, the only means of communication between chrome extension (that runs in sandboxed env) and Native host is via message passing (message = data)


On Wednesday, November 12, 2014 8:11:01 AM UTC-8, a a wrote:
Thanks.
But any idea if NMH will exist in the future?
Because in the video of this page: https://developer.chrome.com/native-client
..at : 18:50
..he mentions something about "closing up direct unsandboxed access".
I am not sure if that means they will remove support from Chrome or something else.. :(

2014-11-11 19:32 GMT+02:00 Nandu <nka...@gmail.com>:
you cannot have full access to OS via native client, but Nacl ports do have some extensibility.
The easy way for you is to "delegate" the responsibility to Native Message Host (NMH). NMH is not double sandboxed  and can access OS primitives


On Tuesday, November 11, 2014 2:42:33 AM UTC-8, a a wrote:
Hi there.

I have read about the "native client" add-ons :

What I want to achieve (without native client though) is to allow to an extension to access the OS (in particular, I need it to access a cryptography token for digitally signing online documents).

From what I have read, this cannot be done with native client, but I have also noticed in a video that the old way (of add-ons accessing the OS) is being removed as we speak (unless I got it wrong).

Is there a way to access the OS with a digitally signed, native add-on?
And will there still be a way in the future?
If there is future in building something like this, I would appreciate some suggestions/link for getting started.

Thanks! :)

--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extensions+unsub...@chromium.org.
Reply all
Reply to author
Forward
0 new messages