THIS IS A READ-ONLY ARCHIVE OF THE SQRL PROJECT FORUM
Final Weeks of Pre-Release Tracking | SQRL Forums

Final Weeks of Pre-Release Tracking


Steve

Administrator
Staff member
May 6, 2018
173
72
www.grc.com
While I'm writing the final SQRL Explainer and Specification document, we are approaching the release point for GRC's SQRL client. Since we have fallen into a sort of natural weekly update cycle for the client, I thought that those with the SQRL client installed, who are therefore receiving these weekly updates, might be curious to know what's going on with each change. So this top-pinned post will be updated (probably not many more times) each week to indicate what has changed with each release:

Release 64:
  • Change "Request no SQRL bypass" -to-> "Request no account recovery".
  • Add a feature to copy the textual identity to the system clipboard.
  • Add clear warning to the RC printout page. DO NOT DISCARD!! and why
  • After a password change remind user to change all other devices.
  • Revisit the URL sizing/shortening algorithm in the password prompt.
Release 65/66:
  • Add space pad before dialog titles in title bars.
  • Fixed the can=url bug Paul F discovered.
  • Improved the language of the Rescue Code printout.
  • Add "licenses" link and documented all open source packages used.
  • Added a clear page title to the Rescue Code printout.
  • Changes "Quick Unlock" to "QuickPass" throughout the entire app.
  • Tweaked the version handler to be quite until/unless installed.
  • Verified printing success under Win10 x64
Release 67:
  • Added an installation or upgrade "Help" button.
  • Added external compression to UI strings.
  • Changed Alt-ID system to add a NULL separator.
  • Added SQRL installation success forum page.
  • Added current identity to title of Rekeying dialogs.
  • Added current identity to title of Renaming identity.
  • Added Alt-ID to the Authorize Login dialog title.
Release 68:
  • Fixed "Request no account recovery" in the help text.
  • Fixed crash in the Copy Identity to Clipboard.
  • Disabled Rescue Code input context menu paste.
Release 69:
  • Added "Click to visit the SQRL web forums" to the Learn About SQRL dialog.
  • Fixed Decompression crash in WINE.
  • Change rename handling when only one identity. (Closes rename dialog.)
  • Fixed app crash on Error code 1 during installation.
  • Fixed the Alt-ID problem that SJ Phillips was exhibiting.
Release 70:
  • Added handling for Controlled Folder Access
Release 71:
  • Fixed inadvertent BOLDING of all SQRL dialog UI text.
  • Fixed a SQRL update crash triggered by SHA256 Digest signing.
  • Fixed an interaction between non-installation and screen darkening.
Release 72:
  • Changed "User" to "Select Identity" on the login options dialog.
  • Now defaults the identity name to the base name of a file-imported identity.
  • Unless a problem is found, THIS WILL BE the v1.0 release of GRC's SQRL client for Windows in the "release" channel.
At LONG last, we're there! :)
 
Last edited:
Was this also the version where you stopped going green after only 4 characters of the rescue code?
I don't think so, Dave. That would have been "by design" when I turned off the "Dev" mode features. SO that would have been expected. The items I'm listing here are fixes to things that were not expected! :-|
 
Hi Steve,
May I suggest putting a highlighted note in your changelog which indicates the version at which the SQRL client needs to be re-installed manually rather than updated? Cheers, Scott
 
Happily that was almost certainly a one time mistake. I don't expect that to ever occur again. But, I agree... if it should happen again I'll make a note like that. At the time I DID have a full width, unavoidable banner across the top of the page that needed to be dismissed by the user. It informed them of the need to manually update GRC's SQRL client.
 
Just for clarification, I was meaning the changelog at the top of this post - I've just been testing SQRL sporadically and missed the big banner. I scanned this post for clues to my update problem - if it reads "Release 65/66: ***NOTE THIS VERSION WAS NOT UPDATED AUTOMATICALLY - PLEASE REINSTALL MANUALLY **** it may save repeated questions/posts from others in the same situation. So excited for final release!
 
Yeah that is a good idea, or a nice note in the list somewhere "If you have version XX or earlier, you need to manually update the client, it should then automatically update after that"
 
Not sure where to report bugs?

I found a VERY minor one I think during my identity creation process. When you get to the screen that allows you to save/export/etc. your identity, the screen opens a file picker dialogue and pre-suggests the identity name as the filename. The file picker screen also notes that the file will be saves with a .sqrl extension. In my case, I renamed the suggested file name to 'Michael SQRL Identity File' and saved it. However, when the file was saved the application omitted the .SQRL file extension. I was able to off course manually add it, but if the application is looking for a file association using that the identity file in question would not launch it and it would also be 'screened out' by the file picker is the .SQRL extension is pre-selected.

Other than that, hoping to try it out some more!
 
Not sure where to report bugs?

I found a VERY minor one I think during my identity creation process. When you get to the screen that allows you to save/export/etc. your identity, the screen opens a file picker dialogue and pre-suggests the identity name as the filename. The file picker screen also notes that the file will be saves with a .sqrl extension. In my case, I renamed the suggested file name to 'Michael SQRL Identity File' and saved it. However, when the file was saved the application omitted the .SQRL file extension. I was able to off course manually add it, but if the application is looking for a file association using that the identity file in question would not launch it and it would also be 'screened out' by the file picker is the .SQRL extension is pre-selected.

Other than that, hoping to try it out some more!
I don't think that's a bug. Any Windows application will display the extension on the file name when first prompted to save and if you change the name, you have to also add the extension back
 
Any Windows application will display the extension on the file name when first prompted to save and if you change the name, you have to also add the extension back
Well that's not always true. I think it's up to the app... extensions are a silly kind of magic. I think there are three different approaches developers use:
1. (What Steve seems to have done) Let the file dialog supply a name and assume the user is in control
2. Look for an existing extension (basically a period) at the end of the filename and if none found, add the desired or default one
3. Look for the desired extension at the end of the filename, if not found, add it no matter what (possibly leading to .foo.bar)

The ideal solution would be for the system to have a better file dialog... so that the extension was separated from the filename (and then could possibly be a drop down list rather than free form.)
 
It does sound as though I ought to put the .sqrl file extension back on the end of the user removes any. I don't want to take too much control away from the user, but what Michael did seems like an easily-fixed glitch. :)
 
Yeah, I think it's easy to fix. I'd personally rather end up with a .sqrl.sqrl then nothing, just for simplicity, especially if my 73YO father wanted to ever use it. If he tried to import it on another phone/device trying to explain how to find a file that has no extension is NOT easy.
 
Well that's not always true. I think it's up to the app... extensions are a silly kind of magic. I think there are three different approaches developers use:
1. (What Steve seems to have done) Let the file dialog supply a name and assume the user is in control
2. Look for an existing extension (basically a period) at the end of the filename and if none found, add the desired or default one
3. Look for the desired extension at the end of the filename, if not found, add it no matter what (possibly leading to .foo.bar)

The ideal solution would be for the system to have a better file dialog... so that the extension was separated from the filename (and then could possibly be a drop down list rather than free form.)

Correct. Word files ALWAYS append a .docx to the end for instance, so it's REALLY hard not to end up with a Word file being a Word file. You sometimes get duplicate extension (file.docx.docx for instance), but Windows in default mode tried to hide all the file extensions, so without it being set properly a novice user might not realize that the file they saved is a .sqrl file (right now the file saves a 'extensionless' in current form).