search

RealEnder / signTextLSF

WebExtension implementing crypto.signText() over LSF
1 stars 0 forks source link

Add port range support #1

Closed RealEnder closed 7 years ago

RealEnder commented 7 years ago

Local webserver may not bind on 8090/tcp if there is some other daemon there. Currently LSF tries to listen only on 8090/tcp, but this will change to be on par with TLS port range. Keep in mind if we found a web service on some port, this sometimes can be different webserver, eg. used for development or other similar service.

vakata commented 7 years ago

This is actually part of the initial response from the server - there are some required fields in the JSON response defined in the protocol. The JS from https://sign.uslugi.io/ has those checks implemented and has basic feature detection (required algs and methods) - it can serve as a good starting point.

user890104 commented 7 years ago

Some of the checks are implemented, feature detection is copied but not used (I don't know what to pass as a parameter).

RealEnder commented 7 years ago

Currently implemented port ranges are: http: 8090, 23125, 53953 https: 8089, 23124, 53952 All are listening to 127.0.0.1 This requires different jnlp, see #4

user890104 commented 7 years ago

Support for port detection added in 4192f05. Feature detection will be added in #3.