Changeset 9c8c9a1 for networking


Ignore:
Timestamp:
04/04/2024 09:15:43 PM (4 weeks ago)
Author:
Douglas R. Reno <renodr@…>
Branches:
trunk
Children:
4e5920a5
Parents:
22b025e
Message:

Adapt Geoclue to use Google's Geolocation Service instead of MLS

This is due to the shutdown at the end of March.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • networking/netlibs/geoclue2.xml

    r22b025e r9c8c9a1  
    158158    </para>
    159159
     160  </sect2>
     161
     162  <sect2 role="configuration">
     163    <title>Configuring GeoClue</title>
     164
     165    <sect3 id="geoclue2-config">
     166      <title>Config Files</title>
     167      <para>
     168        <filename>/etc/geoclue/conf.d/90-lfs-google.conf</filename>
     169      </para>
     170
     171      <indexterm zone="geoclue2 geoclue2-config">
     172        <primary sortas="etc-geoclue-conf.d-90-lfs-google.conf">/etc/geoclue/conf.d/90-lfs-google.conf</primary>
     173      </indexterm>
     174    </sect3>
     175
     176    <sect3><title>Configuration Information</title>
     177
     178      <para>
     179        In March of 2024, Mozilla announced the shutdown of the Mozilla Location
     180        Service. Geoclue uses this service for determining a user's location
     181        when requested by other applications. The only supported alternative by
     182        upstream is to use Google's Geolocation Service.
     183      </para>
     184
     185      <para>
     186        To use Google's Geolocation Service, an API key must be used, and a
     187        configuration file must be created. <emphasis role="bold">This API key
     188        is only intended for use with LFS. Please do not use this API key if you
     189        are building for another distro or distributing binary copies. If you
     190        need an API key, you can request one at
     191        <ulink url="https://www.chromium.org/developers/how-tos/api-keys"/>.</emphasis>
     192      </para>
     193
     194      <para>
     195        Create the configuration needed for using Google's Geolocation Service
     196        as the &root; user:
     197      </para>
     198
     199<screen role="root"><userinput>cat &gt;&gt; /etc/geoclue/conf.d/90-lfs-google.conf &lt;&lt; "EOF"
     200<literal># Begin /etc/geoclue/conf.d/90-lfs-google.conf
     201
     202# This configuration applies for the WiFi source.
     203[wifi]
     204
     205# Set the URL to Google's Geolocation Service.
     206url=https://www.googleapis.com/geolocation/v1/geolocate?key=AIzaSyDxKL42zsPjbke5O8_rPVpVrLrJ8aeE9rQ
     207
     208# End /etc/geoclue/conf.d/90-lfs-google.conf</literal>
     209EOF</userinput></screen>
     210
     211      <para>
     212        If you do not wish to request your location from a Geolocation service,
     213        you can hardcode your location in <filename>/etc/geolocation</filename>
     214        using the format described in
     215        <ulink role='man' url='&man;geoclue'>geoclue(5)</ulink>.
     216      </para>
     217    </sect3>
    160218  </sect2>
    161219
Note: See TracChangeset for help on using the changeset viewer.