__
> Von: mkgmap-dev im Auftrag von
> Felix Hartmann
> Gesendet: Donnerstag, 14. September 2017 10:50:55
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] Recent Garmin Firmware "cannot authenticate
> maps" when they are unicode
>
> I w
v im Auftrag von Felix
Hartmann
Gesendet: Donnerstag, 14. September 2017 10:50:55
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Recent Garmin Firmware "cannot authenticate maps"
when they are unicode
I would rephrase it to "Note that neither very old devices (introduced
optimize-index branch, it is in the
> branch since r3968.
> Please suggest improvements if this is not enough.
>
> Gerd
>
>
> Von: mkgmap-dev im Auftrag von
> Felix Hartmann
> Gesendet: Donnerstag, 14. September 2017 00:14:34
> An: D
lease suggest improvements if this is not enough.
Gerd
Von: mkgmap-dev im Auftrag von Felix
Hartmann
Gesendet: Donnerstag, 14. September 2017 00:14:34
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Recent Garmin Firmware "cannot authent
this can go into documentation not the compile process itself I think. The
warning should be for real warnings that happen because of bugs/problems.
On 13 September 2017 at 21:57, franco_bez wrote:
> One last thought:
>
> maybe it's not a bug in mkgmap, and maybe there is no way to fix this on
>
One last thought:
maybe it's not a bug in mkgmap, and maybe there is no way to fix this on our
side.
But in any way there will be more and more people affected as the number of
new Garmin devices increases.
So we should issue a warning message when maps are built with the unicode
option.
Somethi
Waxy wrote
> Hi,
>
> I tested the dach_boundary_gmapsupp_error.img…
>
> On a etrex 30 : no message "cannot authenticate maps" and boundaries are
> visible.
> On a GPSMAP64s : error message "cannot authenticate maps" and the map is
> not listed.
>
> Steph
Hi Steph,
this is exactly what happens
Hi,
I tested the dach_boundary_gmapsupp_error.img…
On a etrex 30 : no message "cannot authenticate maps" and boundaries are
visible.
On a GPSMAP64s : error message "cannot authenticate maps" and the map is
not listed.
Steph
Le 26/08/2017 à 23:01, franco_bez a écrit :
> Hi Gerd and Andrzej,
>
>
Hi Gerd and Andrzej,
I do not see any reason why GARMIN should only require UNICODE maps to
be signed, while LATIN1 maps can remain unsigned.
I suspect that there is a flag in the file header, maybe a new and
undocumented one, that marks the file as "check for signature".
When the Oregon checks t
Hi Franco,
> I do not see any reason why GARMIN should only require UNICODE maps to
> be signed, while LATIN1 maps can remain unsigned.
Signature is a protection for locked map. Garmin can't implement a
protection, which would disable maps already sold, so the protection is
triggered by a feat
Hi Gerd and Andrzej,
I do not see any reason why GARMIN should only require UNICODE maps to be
signed, while LATIN1 maps can remain unsigned.
I suspect that there is a flag in the file header, maybe a new and
undocumented one, that marks the file as "check for signature".
When the Oregon checks t
Hi,
> my understanding is that this is not a bug, but a limitation
> implemented by Garmin.
This is true. Garmin maps can be digitally signed. Many new GPS require,
that Unicode map include signature. Signature is a protection against
tampering, which is reasonable for commercial maps, but it
___
Von: mkgmap-dev im Auftrag von
franco_bez
Gesendet: Freitag, 25. August 2017 22:18:28
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: [mkgmap-dev] Recent Garmin Firmware "cannot authenticate maps" when
they are unicode
Hi all,
maybe it's already a know bug.
I just stumbled over t
Hi all,
maybe it's already a know bug.
I just stumbled over this one:
On a new Oregon750 I got the Error "cannot authenticate maps", while on the
old Oregon550 the maps worked like always.
I found out that changing the option "unicode" to "latin1" in my style did
the trick, the resulting maps w
14 matches
Mail list logo
