dnssec-validator issueshttps://gitlab.nic.cz/labs/dnssec-validator/-/issues2017-08-23T10:32:07+02:00https://gitlab.nic.cz/labs/dnssec-validator/-/issues/55Plugin isn't detected by Chrome2017-08-23T10:32:07+02:00Jiří AdámekPlugin isn't detected by ChromeDNSSEC and TLSA plugins are not detected by Chrome when a user has restricted rights in Windows (non administrator). OS: Windows 8.1 64-bit.DNSSEC and TLSA plugins are not detected by Chrome when a user has restricted rights in Windows (non administrator). OS: Windows 8.1 64-bit.https://gitlab.nic.cz/labs/dnssec-validator/-/issues/52both `dnssec-plug` and `dane-plug` shouldn't fallback to root servers2017-08-23T10:32:07+02:00Marek Seberaboth `dnssec-plug` and `dane-plug` shouldn't fallback to root serversI use plugins along with Unbound as my system resolver.
Going to https://bad-sig.dane.verisignlabs.com/ will first try to resolve it through set resolver, and if it fails, it tries again by connecting to root NS (root-servers.net)
...I use plugins along with Unbound as my system resolver.
Going to https://bad-sig.dane.verisignlabs.com/ will first try to resolve it through set resolver, and if it fails, it tries again by connecting to root NS (root-servers.net)
There should be option to disable the extension, to use other than set resolver (then it can be used to test system resolver settings)
Issue exists in both binaries (dnssec-plug and dane-plug)
My system is Chrome Canary (version 40), OSX 10.9.5 2.3.0https://gitlab.nic.cz/labs/dnssec-validator/-/issues/48OS X chromium plugin scripts (tlsa and dnssec) fail to install their respecti...2017-11-17T22:57:27+01:00Ghost UserOS X chromium plugin scripts (tlsa and dnssec) fail to install their respective coresThis issue affects both tlsa and dnssec installation scripts.
Browsers installed:
- Google Chrome (stable) 37.0.2062.124
- Google Chrome Canary 40.0.2173.0
- Chromium (stable) 37.0.2062.124 (281580)
Platform:
- 10.9.5 (13F3...This issue affects both tlsa and dnssec installation scripts.
Browsers installed:
- Google Chrome (stable) 37.0.2062.124
- Google Chrome Canary 40.0.2173.0
- Chromium (stable) 37.0.2062.124 (281580)
Platform:
- 10.9.5 (13F34)
Usage:
mkdir $TMPDIR/dnssec-validator-tmp
cd $TMPDIR/dnssec-validator-tmp
curl -LsO https://secure.nic.cz/files/dnssec-validator/2.2.0/dnssec-plugin-2.2.0.x-macosx.sh
chmod +x dnssec-plugin-2.2.0.x-macosx.sh
./dnssec-plugin-2.2.0.x-macosx.sh
Result:
Cannot install chromium extension on OS X.
A CRX file has been created in the current directory.
-n You may now install the file '/var/folders/z3/dwlmgt356wv9gyshgyyvd3bw0000gn/T/jjj/dnssec-pkg.crx' into those browsers:
-n 'Google Chrome'
-e 1) Run the browser.
-e 2) Open the page chrome://extensions/ .
-e 3) Drag and drop the CRX file into the page and accept the notification.
-e 4) Restart the browser.
Installing the resulting CRX and restarting the browser (for example, Opera) the settings pane always displays the following error:
The DNSSEC validating core could not be initialised. Please install the DNSSEC validating core in the version matching this extension and then restart your browser.
This seems to indicate the core was not installed, however it is unclear what did or did not happen.
(Minor note: `-e` and `-n` output are bashishms)2.3.0Karel SlanýKarel Slaný