jasp00 / signtextjs Goto Github PK

In Fedora with Firefox 66.0.2-1.fc29 doesn't work anymore, if I downgrade to a previous version of Firefox works as expected.
Unfortunately I can't see any error in console or anywhere.

After installing the native signtextjs_plus application v0.9.5 on MacOS Mojave, an attempt to sign causes a crash as below.

Dyld Error Message:
Library not loaded: /usr/local/opt/jsoncpp/lib/libjsoncpp.19.dylib
Referenced from: /Library/Application Support/Mozilla/*/signtextjs_plus
Reason: image not found

The signtextjs_plus binary has been bound to a private copy of libjsoncpp, which is not available / not installed as part of the install.

To fix this, the extension needs to depend on a JSON library available natively on MacOS.

When attempting to use crypto.signTextAsync on MacOS Mojave, the attached empty dialog window appears.

The web extensions debugger reports the following:

Loading failed for the <script> with source “blob:null/77744f91-ea5f-5542-8838-ab5fb74437ce”. blank:1
Promise resolved after context unloaded
include.preload.js:546
Promise resolved after context unloaded
include.postload.js:766

A macOS native back end is needed. I am working on the Windows one first and I lack a macOS native environment. A macOS programmer would be helpful; it is a matter of compiling signtextjs_plus.cpp and deploying the application.

I have this error in the console

stderr output from native app signtextjs_plus: Could not detect profile directory
SignText: Native back end disconnected common.js:15:11

This happens in Fedora 33 with firefox-88.0-4.fc33.x86_64

Firefox 53.0 , certificates list is empty.

SignTextJS ( without plus) works fine though.

Users have asked about donations. PayPal does not support GitHub organizations, thus this project cannot accept donations. However, you can donate to the Mozilla Foundation mentioning this project.

You may donate here.

When the web extension returns a list of certs, and the certificate list is empty, the response code error:noMatchingCert is returned.

This message is can be caused by the following scenarios:

• The web extension has picked up certs in the wrong NSS directory and the directory is empty.
• The correct NSS directory is empty.
• The correct NSS directory contains certificates, but the usages are not accepted.
• The correct NSS directory contains certificates, but they are expired or not valid yet.
• The correct NSS directory contains certificates, but do not match an unspecified non_repudiation criteria.
• The correct NSS directory contains certificates, but the certificate cannot be matched to a CA.
• The correct NSS directory contains certificates, but the certificate does not have the email signer key usage,.

The message error:noMatchingCert is too vague to be useful, and end users have no meaningful symptoms they can describe to technical support other than "the list is empty", nor can technical support help without bringing the code up in a debugger.

To fix this, the full list of certificates need to be returned, along with a description of whether the given certificate is valid, and if invalid, why it is invalid. The UI needs to give the option to view invalid certificates, with some kind of tooltip or other mechanism to indicate why the certificate is not a candidate to be selected.

I'm trying to use the latest version (0.9.3) but I'm getting a popup with the text:

signText running...
Please consider using signTextAsync.

Close this window when signing has finished.

When I click OK, nothing happens and the that error message is in the console:

SignText: Unknown encoding 'windows-1251'

Am I doing something wrong?

P.S. Using Firefox ESR version 52.5.3 (64-bit).

Buenos días,

hay alguna manera de poder ver la estructura de la firma resultante del pkcs7 base 64

muchas gracias

saludos

The crypto.signTextAsync() call is not formally documented anywhere.

According to the code, the function defintion is as follows:

function signTextAsync(text, options, resolve, ...CAs)

• From the code, text is a string.
• What data type is options? What are valid options? What are their defaults?
• What is "resolve"? It appears to be a function of some kind, what is it for, and what does it do?
• CAs... the list of CAs. Are these strings? What is the behaviour if this list is empty?

Hello I get
You see this message because of your browser's limitations.
Please consider using signTextAsync.
while signing on macos bigsur with firefox 90
what can I do?

it is related to 857627
and will be fixes by #4

Hello, it seems that signTextJS plus 0.8.5 is not working with Firefox 50.0beta. It gives "TypeError" (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Errors/Unexpected_type).
Also it is not working with Firefox 51.0a2 (2016-10-09) (32 bits). It gives "signtextjsplus:Error: Invalid argument" and "signtextjsplus:TypeError: domWindow.crypto is undefined".

Al utilizar el complemento signTextJS plus 0.9.5 en firefox 72.0.2 sale el error: error:internalError
Utilizo el html de ejemplo que ofreces en: https://github.com/jasp00/signTextJS/tree/master/test/html.
Tengo certificados instalados en firefox y también utilizo el DNIe però no funciona.
El complemento funciona con esta version de firefox? Tengo que hacer alguna configuración adicional?
Gracias

After update to Firefox 59 a message windows is displayed every time I'm trying to sign an order, and nothing else happened(certificate choose dialog is not displayed).

This is the message text:

signText running...
Please consider using signTextAsync.

Close this window when signing has finished.

P.S. I'm using Firefox 59 on openSUSE Leap 42.3 x64.

A Windows native back end is needed. I have been working towards a Win64 port, but this is hard. I lack a Windows native environment and cross-compiling is difficult. A Windows programmer would be helpful; it is a matter of compiling signtextjs_plus.cpp and deploying the application.

When attempting to sign some text using signTestJS+ 0.9.5 on MacOS Mojave and Firefox 60ESR, we enter the code here:

Somehow we leave this code without logging any messages to the browser log.

Looking inside the code, we have two code paths that leave the function with an error but don't log anything:

We also have a variable called s_debug that could, if set to false, suppress all error messages:

When opening the MacOS DMG, the layout of the files signtextjs_plus and signtextjs_plus.json files is such that the files are on top of one another.

It is not clear to an ordinary user what to do at this point.

The files need to be laid out so that they can be dragged to the NativeMessaging folder without changing the view.

Will there be support for Firefox 57 in this plugin?
The mozkeeler version has stated that there won't be: mozkeeler#49 (comment)
However this is marked as required by the FNMT: http://www.cert.fnmt.es/documents/10445900/10528353/solicitud_certificado_persona_fisica.pdf

Thanks

Hello!

We have 2 certificates, and one of them will expire soon, so bank issued new certificate for us.
I installed it into firefox 58 and can successfully login into bank's web interface using it , and I removed old certificate from firefox.
But when I try sign I see two certificates in list, one of which is old certificate and no new certificate, so signing is not possible.
This certificate works with old version of extension in firefox esr.
btw, new certificate has CN Name. TWYRV1f5@gUAAQzo3Kg 2018-01-26 , i.e. have some random data in it and name
while old one has user name and issuer info in it and no date.
but, anyway, this does not explain why old and removed certificate is still listed...

Thank you!

Installed it:

sh ./signtextjs_plus-0.9.0-x86_64-linux-gnu.run
Verifying archive integrity... All good.
Uncompressing signTextJS plus 100%
Installing to /usr/lib/mozilla/native-messaging-hosts

restarted firefox, all I get is window with text:

signText running...
Please consider using signTextAsync.

Close this window when signing has finished.

and OK button.

Thank you!

The plugin has automatically updated to version 0.9.3 but that didn't resolve the problem with the UI. When I click OK I need to manually close the dialog to choose certificate, enter PIN, etc. After I close it the signing works.

I get this in the console:
Scripts may not close windows that were not opened by script. certChooser.js:54:3

Firefox 57.0.4 on Ubuntu x64.

When buttons on certificate chooser dialog are pressed, the dialog is not closed, and on debug console is printed following text:
Scripts may not close windows that were not opened by script.
I am testing with 64 bit firefox 60.0.1 on Windows 10.
On Linux with the same Firefox version everything works.

Hello,

I have an installation with Firefox 57 and Ubuntu 16.04. When I attempt to sing something I get a pop-up saying "signText running... Please consider using signTextAsync. [ОК]" but nothing else. If I click OK it appears again. After I click OK a second time my bank's website says 'certificate error'.

I've installed the native-messaging-hosts bridge into my .mozilla directory.

On the same machine, under a different user with Firefox ESR and the old SignTextJS extension signing works, so my base reader/smartcard setup should be OK.

Any help will be appreciated and thanks for he hard work!

Rado

Firefox 40.0.3 32bit WinXP SP3. signTextJS plus 0.8.6.
When trying to sign, OK and Cancel buttons appear empty, about a few pixels tall. It happenes when requesting a digital certificate from Spain’s Royal Mint (FNMT). I managed to guess which one was the OK button and signing was successful, but this should be addressed. Website error or addon error? Who determines buttons text?

This is the contents of the native-messaging-hosts dir:

aenchevich@pc ~$ ls -l ~/.mozilla/native-messaging-hosts/
total 172
-rw------- 1 aenchevich aenchevich 129632 Jul 10 2018 libjsoncpp.so.0
-rwx------ 1 aenchevich aenchevich 174 Jul 10 2018 signtextjs_plus
-rwx------ 1 aenchevich aenchevich 31720 Jul 10 2018 signtextjs_plus-bin
-rw------- 1 aenchevich aenchevich 237 May 9 17:17 signtextjs_plus.json

However the "about:addons" page says "You don't have any add-ons of this type installed"

And this is the first few lines in "about:support" :

Name Firefox
Version 60.6.3esr
Build ID 20190507003026
Update History
Update Channel esr
User Agent Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0
OS Linux 4.11.8-300.fc26.x86_64

Dear Developers,

Please provide the old 0.8.7 version for manual install so that old browser versions like firefox 45.9 ESR can install it. I need it because the proprietary signing solution I use needs java applet and java applet under linux firefox is supported only in old version of FF

Regards,
vegetzo