Bug 18847 - update candidate: Meteo-qt stopped worked due api key overusage
Summary: update candidate: Meteo-qt stopped worked due api key overusage
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL: https://openweathermap.desk.com/custo...
Whiteboard: advisory MGA5-32-OK
Keywords: validated_update
Depends on:
Blocks:
 
Reported: 2016-07-03 08:43 CEST by Dimitrios Glentadakis
Modified: 2016-07-19 14:47 CEST (History)
2 users (show)

See Also:
Source RPM: meteo-qt-0.8.4-1mgr5.noarch
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Dimitrios Glentadakis 2016-07-03 08:43:14 CEST 
Advisory:
========================

Meteo-qt stopped working due the api key over usage.
Probably the key has been hijacked so since version 0.9.4
there is one key per user.

References:
https://github.com/dglent/meteo-qt/issues/57
========================

Updated packages in core/updates_testing:
========================
meteo-qt-0.9.4-1.mga5.noarch.rpm

Source RPMs: 
meteo-qt-0.9.4-1.mga5.src.rpm
Thierry Vignaud 2016-07-06 15:08:33 CEST

Summary: Meteo-qt stopped worked due api key overusage => update candidate: Meteo-qt stopped worked due api key overusage

Comment 1 Herman Viaene 2016-07-15 15:07:53 CEST 
MGA5-32 on AcerD620 Xfce
No installation issues
Did not use it before. After registering end configuration, works OK

CC: (none) => herman.viaene
Whiteboard: (none) => MGA5-32-OK

Comment 2 claire robinson 2016-07-19 14:17:57 CEST 
Validating

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

Comment 3 claire robinson 2016-07-19 14:30:00 CEST 
advisory uploaded.

Whiteboard: MGA5-32-OK => advisory MGA5-32-OK

Comment 4 Mageia Robot 2016-07-19 14:47:49 CEST 
An update for this issue has been pushed to the Mageia Updates repository.

http://advisories.mageia.org/MGAA-2016-0105.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.