Hi V, The long name is in conformation to Steve's TNO Philosophy, We took that literally & use RoboForm to make 20 Character ID's & Steve's Password Service to make 63 Digit Alpha Numeric Passkeys. All stored Locally with RoboForm . Super Secured.That is a really long name you got there 6B...6B As to your question I have not tried it, hopefully someone knows something. If this is a new bug it really does need to be figured out and solved.
Hi Steve, Cellular Hotspot is where We use Phone's Cellular Data Network & the Phone as WiFi Router / HotSpot. On Windows Phones it's called Mobile HotSpot & on Android, it is named as HotSpot & Tethering in Network Settings. No idea yet what it's called on iPhones. Sharing a screenshot, that may help.Could you describe what you mean by a Cellular Hotspot Network? What exactly are you using and what did you do? We know of no configuration where it should not work.
Hi P, Cellular HotSpot is like using the Phone's Data over Local WiFi where the Phone becomes Wireless Router, sort of. We tried with MITM disabled, still got the same error that the Logon Page has expired. Would greatly help if someone could have run into this issue & resolved it before us.I'm going to guess that this is like "free WiFi"? If that is the case, the user needs to describe what they mean by "latest build is also unable to authenticate as expected". Does that mean they get a warning and abort? (Which is my guess... they're seeing an IP mismatch and haven't disabled that in the client.)
Despite what has been said in another thread I still cannot tell Windows Defender to ignore sqrl.exe.I use Chrome and had problems until I told Windoze to ignore sqrl.exe.
Sorry, @Alan M Cameron, I must have been in a state where sqrl.exe had not been removed/quarantined yet. As I posted elsewhere, Microsoft claims (and appears) to have updated Windows Defender definitions so it no longer considers sqrl.exe a threat.Despite what has been said in another thread I still cannot tell Windows Defender to ignore sqrl.exe.
I get the steps to get to the point of adding an exclusion but what do you add if you say file it asks you for the file and path.
Could you please give step by step on how to add an exclusion when there is no file to identify.
UPDATE All is well so I think I have eventually got #66 installed.This is not what I found when I recently tried, using Edge, to download version #66. It still complained. However without making any changes to the system I tried to download using Chrome and it worked. I have used SQRL to sign in after logging out and was successful.
Now to see if it will object when I use GRC demo site and remove sqrl.exe.
I think you have been asking how to get past Windows Defender when downloading a file and you can't exclude it yet because you don't have it. For future reference this should help. I posted it in a different thread. Sorry if it didn't get to you earlier.UPDATE All is well so I think I have eventually got #66 installed.
Paul: But he's using the Windows client, so it's same-device and same-IP. It should work fine, right? I think there must be something else going on, likely with his browser.I'm going to guess that this is like "free WiFi"? If that is the case, the user needs to describe what they mean by "latest build is also unable to authenticate as expected". Does that mean they get a warning and abort? (Which is my guess... they're seeing an IP mismatch and haven't disabled that in the client.)
Agreed.I think there must be something else going on
Hi Steve, We are using FireFox ( The Favorite Browser ) with uBlock & ABP Plugins Installed. Have validated that on LANs the setup works as designed. It's only on the Cell HotSpot that this trouble occurs. Using IPv4 on Laptop ( DHCP - 192 Range ). Phone gets the IP from Cellular Service Provider.Paul: But he's using the Windows client, so it's same-device and same-IP. It should work fine, right? I think there must be something else going on, likely with his browser.
Let me try and restate what I think has been communicated:
Using the GRC client on (probably) a laptop, which is connected to the Internet through an Android mobile phone running mobile hotspot mode. This means the client is getting an IP address from the mobile phone (via DHCP) I presume. Any packets sent to the phone are then being "edited" to appear as coming from the phone, using its IP address, and then forwarded on to mobile network.
I believe mobile phones are frequently on IPv6, but I don't know if the mobile hotspot is offering IPv6 to the laptop, or if that is IPv4.
I guess, at this point, we need more information, or we need to know if this configuration has ever worked for anyone, ever.
Yes, but perhaps I didn't clarify my question sufficiently well. I am asking how we prevent SQRL from failling to auto-update simply because the signing string on the certificate changed. That's something that will almost certainly happen again in the future. Auto-update failure is simply not acceptable for most users.there is little Steve can do to prevent malware cops from assuming his code needs extra inspection. All he can do is make his code work well... and let the chips fall where they may.
I think Rob was relating to the auto upgrade failure due to the cert issuer having changed.An analogy: cops have been known to frequently target certain people and cars for extra inspection. This is generally unfair, but it's unclear how the targets can do anything about who they are... and it seems unfair to expect them to live a different life just because they may encounter more resistance than others.
In the same vein it seems there is little Steve can do to prevent malware cops from assuming his code needs extra inspection. All he can do is make his code work well... and let the chips fall where they may.
Understood. And I think all he can do is to be prepared for it in advance, and to add the new info about any future cert [change] to an update before the current cert expires.I am asking how we prevent SQRL from failling to auto-update
[in the future]