Core Apps » Bazaar

right now there is special URIs for http:// and https:// connections, here is a potenial full mapping:

• fdroidrepo:// for http://
• fdroidrepos:// for https://
• fdroidrepob:// for Bluetooth RFCOMM
• fdroidrepoo:// for OTRDATA

Also, I'm in the process of moving the fingerprint from the 'user' portion of the URI to the 'query string' portion of the URI, which makes more sense. Putting the fingerprint in the user portion confused the browser, which tried to log into the page using that as the username. For example:

• old style fingerprint as user: https://cafebabecafebabecafebabecafebabe@guardianproject.info/fdroid/repo
• new style in query string: https://guardianproject.info/fdroid/repo?fingerprint=cafebabecafebabecafebabecafebabe

Additionally, other bits of info can be included in the query string, like the wifi SSID and BSSID. This allows a URI to be sent via QR or NFC, then the receiver can check whether it is on the same wifi as the sender, which is necessary for local repos to work.

With the current rough plan for OTRDATA integration, F-droid will simply be accessing a 127.0.0.1 based HTTP (or possibly HTTPS) repo. In that design, it will not need to know any specific URI.

What we did discuss was support for HTTP auth via http://user:pass@127.0.0.1:8888/fdroid/repo style format.

The URL format for an RFCOMM StreamConnection :

btspp://
                   hostname:[
                   CN |  
                   UUID];
                   parameters

The URL format for an RFCOMM StreamConnection :
btspp://hostname:[CN | UUID];parameters

• hostname is either localhost to set up a server connection, or the Bluetooth address to create a client connection.
• PSM is the Protocol/Service Multiplexer value, used by a client connecting to a server.
• CN is the Channel Number value, used by a client connecting to a server.
• UUID is the Universally Unique Identifier used when setting up a service on a server. Each UUID is guaranteed to be unique across all time and space.

Parameters include name to describe the service name, and the security parameters authenticate, authorize, and encrypt.

Example : Server RFCOMM URL:
btspp://localhost:2D26618601FB47C28D9F10B8EC891363;authenticate=false; encrypt=false;name= rfcommtest

A client RFCOMM URL:
btspp://0123456789AF:1;master=false;encrypt=false;authenticate=false

Using localhost as a hostname indicates you want a server connection. To create a client connection to a known device and service, use the service's connection URL, found in its ServiceRecord.