We're at Release #68 (release candidate 3)


Status
Not open for further replies.
Steve

Steve

Administrator
Staff member
May 6, 2018
1,016
307
www.grc.com
Everyone...

Release #68 is published. It ...

1. Fixes a memory management bug Paul F reported. (This is why I pushed it out immediately.)
2. Updates some wording in the help text.
3. Disables the trick of pasting into the Rescue Code field with Right-clicking. (We need to dissuade ever placing the RC onto the clipboard.)

It appears that our auto-update system is stable once again. (Has anyone tried to download with Edge and SmartScreen recently?) And, while I still intend to make time to look at the app's textual content one final time, I am once again hopeful that we are very nearly finished. :)

Thanks, everyone!
 
C

CVBoykin

Member
Feb 3, 2019
19
2
And I was able to download a copy of the new SQRL client with MS Edge. No complaint from Windows Defender now.
 
alt3rn1ty

alt3rn1ty

Well-known member
Feb 2, 2019
89
4
As per previous update, #67 to #68 update went fine.

Was a bit surprised to see SQRL pop up so soon with another update, but its a pleasant one anyway :)

Win 10 x 64 download was automatic with the client updating itself = No issues
Download with Chromium = No issues
Scanned with Windows Defender, and Malwarebytes = No issues
Download with Edge (Smartscreen on) = No issues
Download with Internet Explorer <shudders> (Smartscreen on) = No issues
 
Last edited:
onekopaka

onekopaka

New member
Feb 20, 2019
4
0
Just like #66 to #67, #67 to #68 by automatic update, worked great for me.
However slight complaint about the update process:

I was playing a game, and SQRL's update popup took my input focus out of my game. Thankfully it was a slow paced game, so it wasn't a big deal, however it would be nice if SQRL's update notification was not so in your face, although I imagine after final release, the update frequency will be relatively low.
 
I

i2n2

Member
Mar 7, 2019
16
2
"serious problem" on macos and wine

357
• Versions in the working stack 2019-04-30
os: macos 10.14.4
wine: Wine Stable.app wine-4.0


• Beginning of the backtrace:
Unhandled exception: page fault on read access to 0x00000008 in 32-bit code (0x0040129f).
Register dump:
CS:001b SS:0023 DS:0023 ES:0023 FS:1007 GS:000f
EIP:0040129f ESP:0032fe94 EBP:0032fe98 EFLAGS:00010206( R- -- I - -P- )
EAX:00000010 EBX:00000000 ECX:201c0f28 EDX:00000000
ESI:0032feb0 EDI:00000003
Stack dump:
0x0032fe94: 00010058 0032fec0 004120af 00000002
0x0032fea4: 00401000 7ffdf000 02100800 4c525153
0x0032feb4: 6c655220 65736165 38362320 0032ff00
0x0032fec4: 00412189 00401000 7ffdf000 02100800
0x0032fed4: 00411b54 00411a6f 0043c9a6 00000001
0x0032fee4: 005b14e8 005b1540 a51ab189 00401000
0200: sel=1007 base=7ffc0000 limit=00000fff 32-bit rw-
Backtrace:
=>0 0x0040129f in sqrl (+0x129f) (0x0032fe98)
1 0x004120af in sqrl (+0x120ae) (0x0032fec0)
2 0x00412189 in sqrl (+0x12188) (0x0032ff00)
3 0x00000000 (0x7ffdf000)
4 0x00000000 (0x00010000)
0x0040129f: movl 0x8(%ebx),%ecx


The old #67 version works under this stack

/ i2n2
 
shanedk

shanedk

Well-known member
May 20, 2018
421
113
i2n2 said:
"serious problem" on macos and wine

View attachment 357
• Versions in the working stack 2019-04-30
os: macos 10.14.4
wine: Wine Stable.app wine-4.0


• Beginning of the backtrace:
Unhandled exception: page fault on read access to 0x00000008 in 32-bit code (0x0040129f).
Register dump:
CS:001b SS:0023 DS:0023 ES:0023 FS:1007 GS:000f
EIP:0040129f ESP:0032fe94 EBP:0032fe98 EFLAGS:00010206( R- -- I - -P- )
EAX:00000010 EBX:00000000 ECX:201c0f28 EDX:00000000
ESI:0032feb0 EDI:00000003
Stack dump:
0x0032fe94: 00010058 0032fec0 004120af 00000002
0x0032fea4: 00401000 7ffdf000 02100800 4c525153
0x0032feb4: 6c655220 65736165 38362320 0032ff00
0x0032fec4: 00412189 00401000 7ffdf000 02100800
0x0032fed4: 00411b54 00411a6f 0043c9a6 00000001
0x0032fee4: 005b14e8 005b1540 a51ab189 00401000
0200: sel=1007 base=7ffc0000 limit=00000fff 32-bit rw-
Backtrace:
=>0 0x0040129f in sqrl (+0x129f) (0x0032fe98)
1 0x004120af in sqrl (+0x120ae) (0x0032fec0)
2 0x00412189 in sqrl (+0x12188) (0x0032ff00)
3 0x00000000 (0x7ffdf000)
4 0x00000000 (0x00010000)
0x0040129f: movl 0x8(%ebx),%ecx


The old #67 version works under this stack

/ i2n2
Click to expand...
I'm getting the same thing on my Debian box.
 
T

TecMunky

Member
Mar 8, 2019
10
2
SOLVED: I disabled Symantec Endpoint Protection (SEP) again - and this time it worked. I think maybe when I said I had disabled it that it was not really disabled.
---

Update #68 appears to work, but does not. still stuck at #67.
I think it has something to do with Symantec Endpoint Protection, but I can't make an exception this time (I was able to create an exception for #66)

UPDATEs:
Even disabling Symantec Endpoint Protection does NOT solve the issue
Downloading and installing sqrl.exe still leaves me with version #67 installed.

I will try again after I am able to reboot my computer (in a few hours i think)

UPDATE (again):
I don't think it is being blocked by SEP - I manually entered an exception to sqrl-fork.exe and sqrl-installer.exe.
Also, the above two files are clearly available on the system (not quarantined), and disappear after SQRL "apparently updates". And these files do not show up in the quarantine list, as it had when I was trying to update to version 66.
Everything seems to work, but after "updating" nothing is updated, and I get the message again that a new version is available.
 
Last edited:
R

RayG

Well-known member
May 20, 2018
47
4
UK
3. Disables the trick of pasting into the Rescue Code field with Right-clicking. (We need to dissuade ever placing the RC onto the clipboard.)
Click to expand...
#68 - I can no longer paste the RC into the dialogue box :).

However...

I can still get RoboForm to type the RC into the box. Is this another wrinkle you want to try and eradicate. (perhaps for any password manager)
 
Steve

Steve

Administrator
Staff member
May 6, 2018
1,016
307
www.grc.com
@i2n2 and @shanedk :

This is PRECISELY the error that Ramriot (Gary) encountered with WINE and release #67.
https://sqrl.grc.com/threads/were-at-release-67-grcs-sqrl-client-2nd-release-candidate.590/post-4341

ramriot said:
Solution involved removing the existing install & c: drive upgrading to Wine V4 & reinstalling SQRL, which I did with the #66 copy. It then ran the updater which succeeded this time & opened a webpage in the forum.
Click to expand...
 
  • Like
Reactions: Norm
Steve

Steve

Administrator
Staff member
May 6, 2018
1,016
307
www.grc.com
RayG said:
I can still get RoboForm to type the RC into the box. Is this another wrinkle you want to try and eradicate. (perhaps for any password manager)
Click to expand...
Yeah. THAT one is a bridge too far. I'm not going to attempt to block keystroke automation macro systems. If a user wishes to go to that length, I think we should let them! :) Thanks for your testing and feedback.
 
J

JohnBaxter

Member
Apr 18, 2019
5
1
Port Ludlow, WA
On my old Dell tower (about which I don't much care), I got an update failure, Code 8. Before I knew that was Authenticode error I tried disabling "Controlled Folder" protection, then also live protection, without success. (Turned those back on, of course.)

2019-05-01: I revisited the Dell. Downloaded and installed current SQRL version. "Controlled folder access" prevented installation until turned off (fine--that's its job). Removed years old version that was in Documents and forgotten about.


On my little weak Acer laptop, the update ran fine, then (twice) clicking the SQRL QR code to log into the forum produced Web protocol error. (That was using Edge)

Using Firefox, I was already logged in, seemingly because I failed to log out previously in Firefox.

--John
 
Last edited:
Equinoxe

Equinoxe

New member
May 20, 2018
4
0
shanedk

shanedk

Well-known member
May 20, 2018
421
113
Steve

Steve

Administrator
Staff member
May 6, 2018
1,016
307
www.grc.com
@i2n2 and @shanedk : Thanks for getting back to me on this. The big change I made that this must be about is the external compression of the user interface text. If that's it, the trouble is that the client is decompressing the text on-the-fly using a function from the NTDLL.DLL that might not be supported by WINE. If that's the trouble it's annoying since that means I cannot do that at all if I want WINE support, which I clearly do.

The only remaining puzzle, then, is how is Gary (@ramriot) apparently succeeding under his instance of WINE?

Gary: Are you CERTAIN that you're running #68 successfully under WINE?
 
Status
Not open for further replies.
Top Bottom