What will the firmware upgrade process be like?

[DaeCatt]

To upgrade the firmware of an original Solo you have to use either the deprecated Solo Webupdate, a python based command line tool, or the seemingly abandoned Solo Desktop application which hasn't seen any code commits in over a year.

So what can we expect the firmware upgrade process to be like for Solo v2, and how will you guarantee that the Solo v2 remains always up-to-date as the Kickstarter states?

[conorpp]

We'll start by offering two command line tools -- one being the same python command line tool, and another Rust based native command line tool. We're exploring options on how to effectively integrate into some nice frontend or GUI setup.

[oplik0]

So just an update about Tauri if what to use for GUI is still open for discussion.
Since january, it moved into beta. Other than adding some features like cross-platform app tray icon support, self updater or multiwindow support, it removed Node.js dependency for development (replacing node based CLI with a rust one), moved from webview/webview to a new rust based webview library (WRY), and improved the API between rust code and UI (new content loader, better command handling etc.)

Also, it's currently undergoing an audit by Doyensec.

So while still not fully stable, it seems more ready for a production app. Especially here since there already is a Rust-based CLI.

[abe-101]

Is the python tool suitable to use on the solokey V2?

[oplik0]

AFAIK no, only the rust CLI (you can download it from releases now: https://github.com/solokeys/solo2-cli/releases/tag/v0.0.6, or use cargo install solo2) works with solo v2 currently.

[rpavlik]

Any idea where the firmware is coming from? The rust CLI claims the "latest release" is 1:20200101.8, but that seems awfully old, and there are reports of bricking when trying to update the firmware on Reddit. Meanwhile the https://github.com/solokeys/solo2/ repo does show progress and releases but with version numbers and artifacts that seem wholly unrelated.

[oplik0]

It's using latest releases from GitHub, but for some reason the CLI retrieves CalVer from lpc55 versioning package, which is supposed to be major_version:date_of_minor_version.patch_version format.
It should therefore be 1:20211111.8, but it's not as you can see. I haven't actually looked into where lpc55 gets the minor version date from, but it's encoding it as days since 2020-01-01, so presumably it can't get that info from the GitHub release, and therefore sets that value to 0 which is equal to the date you see in the version.

Why is it using CalVer when that doesn't match GitHub releases? No idea honestly. It seems that it was changed in some refactor after 0.0.7 where they moved from a slightly simpler version structure inside the solo2-cli crate itself (that didn't even implement that way of versioning) to using the one from lpc55. I created an issue for moving to SemVer here: solokeys/solo2-cli#27

Edit: also quickly created a PR to change that, since it was quite simple: solokeys/solo2-cli#28

Edit 2: if you want to see more about what the CLI is doing, you can increase the log verbosity by setting SOLO2_LOG environment variable to debug (Powershell: $Env:SOLO2_LOG="debug", cmd: set SOLO2_LOG=debug, bash/zsh: export SOLO2_LOG=debug). For the update command the debug output will include the requests made, including redirects so you can see where exactly it downloads the file from :)

[Iolaum]

I am trying to update a hacker solo2 key but the process appears stuck/stopped with no information as to why:

$ solo2 update
Downloading latest release from https://github.com/solokeys/solo2/
 DEBUG ureq::stream > connecting to api.github.com:443 at 140.82.121.5:443
 DEBUG rustls::client::hs > No cached session for DnsName(DnsName(DnsName("api.github.com")))
 DEBUG rustls::client::hs > Not resuming any session
 DEBUG rustls::client::hs > Using ciphersuite Tls13(Tls13CipherSuite { suite: TLS13_AES_128_GCM_SHA256, bulk: Aes128Gcm })
 DEBUG rustls::client::tls13 > Not resuming
 DEBUG rustls::client::tls13 > TLS1.3 encrypted extensions: [ServerNameAck]
 DEBUG rustls::client::hs    > ALPN protocol is None
 DEBUG ureq::stream          > created stream: TcpStream { addr: 192.168.1.209:59446, peer: 140.82.121.5:443, fd: 5 }
 DEBUG ureq::unit            > sending request GET https://api.github.com/repos/solokeys/solo2/releases/latest
 DEBUG ureq::unit            > writing prelude: GET /repos/solokeys/solo2/releases/latest HTTP/1.1
Host: api.github.com
Accept: */*
User-Agent: solo2-cli
accept-encoding: gzip
 DEBUG rustls::client::tls13 > Ticket saved
 DEBUG rustls::client::tls13 > Ticket saved
 DEBUG ureq::unit            > response 200 to GET https://api.github.com/repos/solokeys/solo2/releases/latest
 DEBUG ureq::stream          > dropping stream: TcpStream { addr: 192.168.1.209:59446, peer: 140.82.121.5:443, fd: 5 }
 DEBUG ureq::stream          > connecting to github.com:443 at 140.82.121.4:443
 DEBUG rustls::client::hs    > No cached session for DnsName(DnsName(DnsName("github.com")))
 DEBUG rustls::client::hs    > Not resuming any session
 DEBUG rustls::client::hs    > Using ciphersuite Tls13(Tls13CipherSuite { suite: TLS13_AES_128_GCM_SHA256, bulk: Aes128Gcm })
 DEBUG rustls::client::tls13 > Not resuming
 DEBUG rustls::client::tls13 > TLS1.3 encrypted extensions: [ServerNameAck]
 DEBUG rustls::client::hs    > ALPN protocol is None
 DEBUG ureq::stream          > created stream: TcpStream { addr: 192.168.1.209:58482, peer: 140.82.121.4:443, fd: 5 }
 DEBUG ureq::unit            > sending request GET https://github.com/solokeys/solo2/releases/download/1.0.9/solo2-firmware-1.0.9.sb2
 DEBUG ureq::unit            > writing prelude: GET /solokeys/solo2/releases/download/1.0.9/solo2-firmware-1.0.9.sb2 HTTP/1.1
Host: github.com
Accept: */*
User-Agent: solo2-cli
accept-encoding: gzip
 DEBUG rustls::client::tls13 > Ticket saved
 DEBUG rustls::client::tls13 > Ticket saved
 DEBUG ureq::unit            > response 302 to GET https://github.com/solokeys/solo2/releases/download/1.0.9/solo2-firmware-1.0.9.sb2
 DEBUG ureq::unit            > redirect 302 https://github.com/solokeys/solo2/releases/download/1.0.9/solo2-firmware-1.0.9.sb2 -> https://objects.githubusercontent.com/github-production-release-asset-2e65be/234604146/a88f7708-56b7-4519-a97b-2602c4863594?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20220501%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20220501T145225Z&X-Amz-Expires=300&X-Amz-Signature=44217fcf9a213e4048058f56f103936046069c1d1c6895e11142d10eef9ef591&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=234604146&response-content-disposition=attachment%3B%20filename%3Dsolo2-firmware-1.0.9.sb2&response-content-type=application%2Foctet-stream
 DEBUG ureq::stream          > dropping stream: TcpStream { addr: 192.168.1.209:58482, peer: 140.82.121.4:443, fd: 5 }
 DEBUG ureq::stream          > connecting to objects.githubusercontent.com:443 at 185.199.111.133:443
 DEBUG rustls::client::hs    > No cached session for DnsName(DnsName(DnsName("objects.githubusercontent.com")))
 DEBUG rustls::client::hs    > Not resuming any session
 DEBUG rustls::client::hs    > Using ciphersuite Tls13(Tls13CipherSuite { suite: TLS13_AES_256_GCM_SHA384, bulk: Aes256Gcm })
 DEBUG rustls::client::tls13 > Not resuming
 DEBUG rustls::client::tls13 > TLS1.3 encrypted extensions: [ServerNameAck]
 DEBUG rustls::client::hs    > ALPN protocol is None
 DEBUG rustls::client::tls13 > Ticket saved
 DEBUG ureq::stream          > created stream: TcpStream { addr: 192.168.1.209:59956, peer: 185.199.111.133:443, fd: 5 }
 DEBUG ureq::unit            > sending request GET https://objects.githubusercontent.com/github-production-release-asset-2e65be/234604146/a88f7708-56b7-4519-a97b-2602c4863594?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20220501%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20220501T145225Z&X-Amz-Expires=300&X-Amz-Signature=44217fcf9a213e4048058f56f103936046069c1d1c6895e11142d10eef9ef591&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=234604146&response-content-disposition=attachment%3B%20filename%3Dsolo2-firmware-1.0.9.sb2&response-content-type=application%2Foctet-stream
 DEBUG ureq::unit            > writing prelude: GET /github-production-release-asset-2e65be/234604146/a88f7708-56b7-4519-a97b-2602c4863594?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20220501%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20220501T145225Z&X-Amz-Expires=300&X-Amz-Signature=44217fcf9a213e4048058f56f103936046069c1d1c6895e11142d10eef9ef591&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=234604146&response-content-disposition=attachment%3B%20filename%3Dsolo2-firmware-1.0.9.sb2&response-content-type=application%2Foctet-stream HTTP/1.1
Host: objects.githubusercontent.com
Accept: */*
User-Agent: solo2-cli
accept-encoding: gzip
 DEBUG ureq::unit            > response 200 to GET https://objects.githubusercontent.com/github-production-release-asset-2e65be/234604146/a88f7708-56b7-4519-a97b-2602c4863594?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20220501%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20220501T145225Z&X-Amz-Expires=300&X-Amz-Signature=44217fcf9a213e4048058f56f103936046069c1d1c6895e11142d10eef9ef591&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=234604146&response-content-disposition=attachment%3B%20filename%3Dsolo2-firmware-1.0.9.sb2&response-content-type=application%2Foctet-stream
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 32/316816
 DEBUG ureq::pool            > adding stream to pool: https|objects.githubusercontent.com|443 -> TcpStream { addr: 192.168.1.209:59956, peer: 185.199.111.133:443, fd: 5 }
 DEBUG ureq::stream          > connecting to github.com:443 at 140.82.121.4:443
 DEBUG rustls::client::hs    > Resuming session
 DEBUG rustls::client::hs    > Using ciphersuite Tls13(Tls13CipherSuite { suite: TLS13_AES_128_GCM_SHA256, bulk: Aes128Gcm })
 DEBUG rustls::client::tls13 > Not resuming
 DEBUG rustls::client::tls13 > TLS1.3 encrypted extensions: [ServerNameAck]
 DEBUG rustls::client::hs    > ALPN protocol is None
 DEBUG ureq::stream          > created stream: TcpStream { addr: 192.168.1.209:58484, peer: 140.82.121.4:443, fd: 5 }
 DEBUG ureq::unit            > sending request GET https://github.com/solokeys/solo2/releases/download/1.0.9/solo2-firmware-1.0.9.sha2
 DEBUG ureq::unit            > writing prelude: GET /solokeys/solo2/releases/download/1.0.9/solo2-firmware-1.0.9.sha2 HTTP/1.1
Host: github.com
Accept: */*
User-Agent: solo2-cli
accept-encoding: gzip
 DEBUG rustls::client::tls13 > Ticket saved
 DEBUG rustls::client::tls13 > Ticket saved
 DEBUG ureq::unit            > response 302 to GET https://github.com/solokeys/solo2/releases/download/1.0.9/solo2-firmware-1.0.9.sha2
 DEBUG ureq::unit            > redirect 302 https://github.com/solokeys/solo2/releases/download/1.0.9/solo2-firmware-1.0.9.sha2 -> https://objects.githubusercontent.com/github-production-release-asset-2e65be/234604146/aa2e022d-5ce0-409a-997b-8715217207ae?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20220501%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20220501T145225Z&X-Amz-Expires=300&X-Amz-Signature=139ae49847824421fa32edad5254f23e9d56fd3017a2d45cddcc4233b631bdd2&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=234604146&response-content-disposition=attachment%3B%20filename%3Dsolo2-firmware-1.0.9.sha2&response-content-type=application%2Foctet-stream
 DEBUG ureq::stream          > dropping stream: TcpStream { addr: 192.168.1.209:58484, peer: 140.82.121.4:443, fd: 5 }
 DEBUG ureq::stream          > connecting to objects.githubusercontent.com:443 at 185.199.108.133:443
 DEBUG rustls::client::hs    > Resuming session
 DEBUG rustls::client::hs    > Using ciphersuite Tls13(Tls13CipherSuite { suite: TLS13_AES_256_GCM_SHA384, bulk: Aes256Gcm })
 DEBUG rustls::client::tls13 > Resuming using PSK
 DEBUG rustls::client::tls13 > TLS1.3 encrypted extensions: [ServerNameAck]
 DEBUG rustls::client::hs    > ALPN protocol is None
 DEBUG rustls::client::tls13 > Ticket saved
 DEBUG ureq::stream          > created stream: TcpStream { addr: 192.168.1.209:56492, peer: 185.199.108.133:443, fd: 5 }
 DEBUG ureq::unit            > sending request GET https://objects.githubusercontent.com/github-production-release-asset-2e65be/234604146/aa2e022d-5ce0-409a-997b-8715217207ae?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20220501%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20220501T145225Z&X-Amz-Expires=300&X-Amz-Signature=139ae49847824421fa32edad5254f23e9d56fd3017a2d45cddcc4233b631bdd2&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=234604146&response-content-disposition=attachment%3B%20filename%3Dsolo2-firmware-1.0.9.sha2&response-content-type=application%2Foctet-stream
 DEBUG ureq::unit            > writing prelude: GET /github-production-release-asset-2e65be/234604146/aa2e022d-5ce0-409a-997b-8715217207ae?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20220501%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20220501T145225Z&X-Amz-Expires=300&X-Amz-Signature=139ae49847824421fa32edad5254f23e9d56fd3017a2d45cddcc4233b631bdd2&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=234604146&response-content-disposition=attachment%3B%20filename%3Dsolo2-firmware-1.0.9.sha2&response-content-type=application%2Foctet-stream HTTP/1.1
Host: objects.githubusercontent.com
Accept: */*
User-Agent: solo2-cli
accept-encoding: gzip
 DEBUG ureq::unit            > response 200 to GET https://objects.githubusercontent.com/github-production-release-asset-2e65be/234604146/aa2e022d-5ce0-409a-997b-8715217207ae?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20220501%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20220501T145225Z&X-Amz-Expires=300&X-Amz-Signature=139ae49847824421fa32edad5254f23e9d56fd3017a2d45cddcc4233b631bdd2&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=234604146&response-content-disposition=attachment%3B%20filename%3Dsolo2-firmware-1.0.9.sha2&response-content-type=application%2Foctet-stream
██████████████████████████████████████████████████████████████████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 32/94
 DEBUG ureq::pool            > adding stream to pool: https|objects.githubusercontent.com|443 -> TcpStream { addr: 192.168.1.209:56492, peer: 185.199.108.133:443, fd: 5 }
Fetched firmware version 1:20200101.9
 DEBUG solo2::transport::pcsc > >> 00a4040009a0000008470000000100
 DEBUG solo2::transport::pcsc > RECV 2 bytes
 DEBUG solo2::transport::pcsc > << 9000
 INFO  solo2::transport       > answer to selecting a00000084700000001: 
 DEBUG solo2::transport::pcsc > >> 0062000000
 DEBUG solo2::transport::pcsc > RECV 18 bytes
 DEBUG solo2::transport::pcsc > << f06f445086ec215badaa0ea95a0444579000
 DEBUG solo2::transport::pcsc > >> 00a4040009a0000008470000000100
 DEBUG solo2::transport::pcsc > RECV 2 bytes
 DEBUG solo2::transport::pcsc > << 9000
 INFO  solo2::transport       > answer to selecting a00000084700000001: 
 INFO  solo2::transport       > using PCSC as minimal transport
 DEBUG solo2::transport::pcsc > >> 0061000000
 DEBUG solo2::transport::pcsc > RECV 6 bytes
 DEBUG solo2::transport::pcsc > << 004000089000
 INFO  solo2::device          > device fw version: 1:20200101.8
 INFO  solo2::device          > new fw version: 1:20200101.9
Tap button on key to confirm, or replug to abort...
 DEBUG solo2::transport::pcsc > >> 00a4040009a0000008470000000100
 DEBUG solo2::transport::pcsc > RECV 2 bytes
 DEBUG solo2::transport::pcsc > << 9000
 INFO  solo2::transport       > answer to selecting a00000084700000001: 
 INFO  solo2::transport       > using PCSC as minimal transport
 DEBUG solo2::transport::pcsc > >> 0051000000

After ~15m I Ctrl-C the shell and re-insert the solo2 key. Thankfully it still works at the previous version. Can't tell what's happening behind the scenes even after I enable debug logging as can be seen above.

After I put the solo2 key back in I get:

$ solo2 app admin version
1:20200101.8