swap when one of the devices is acting as WIFI access point

On my Moto G this used to work till recently when the "recipient" was acting as the AP. After some updates it does not work at all and it appears f-droid is completely unable to connect the repo, without giving too many diagnostic details unfortunately.

It does not matter if the WIFI-ap device has any kind of internet connection.

If the "repo" is on the device acting as AP it never worked as f-droid is unable to create a valid URL - displays https://null:8888 in this case

Glad for any hints and known workarounds.

Duplicate of #193 (closed)?

no exact duplicate:

• it fails even when the hotspot has some internet connection
• it used to work when the "receiving" phone acted as hotspot but stopped working recently

..just found out that on the "giving end" I had the https checkbox enabled and on the receiving end a slightly older version of Fdroidclient (no idea why this was not shown in the available updates)

After unchecking the https it works for now, will need to see if the https will work when both clients have the same version?

The HTTPS support is really raw and not something to be used. So I'm going to remove that preference for now, since it just breaks swap.

Reassigned to @eighthave

Milestone changed to 0.96

Status changed to closed by commit 303de3d972eacdda8ac6c4f5ea984ca8d3f1cd64

Regarding HTTPS I was also wondering how/if any kind of SSL certificate checking was done? Possibly a fingerprint could be embedded into the QR code?

The grand plan is to use the same method we use for the repo signing key with the HTTPS connection. You can include the signing key fingerprint in the repo URL, for example:

https://guardianproject.info/fdroid

Since the same key is used both for signing the app metadata, which is working in swap now, as well as the HTTPS certificate, that same fingerprint can be used to verify both the app metadata signing key as well as the HTTPS certificate. This is a non-standard way of verifying HTTPS certificates, so it must be done carefully. Here is the plan I've worked out so far: https://dev.guardianproject.info/projects/bazaar/wiki/Chained_TLS_Cert_Verification

How does "https://guardianproject.info/fdroid" include the signing key in the URL?

But it seems that we were both thinking in a similar direction.

Its in the URL when you click on it:

https://guardianproject.info/fdroid/repo?fingerprint=B7C2EEFD8DAC7806AF67DFCD92EB18126BC08312A7F2D6F3862E46013C7A6135

And its also in the QRCode.

this has a nicer splash page, if you are looking for something to improve on:

https://s3.amazonaws.com/storymaker/index.html

I'd love to see this kind of splash page auto-generated as part of the fdroidserver tools.

thanks, that looks good.

@RichZ please keep us posted on what you come up with!