libre.fm/nowplaying url is contacted and sent the current song being played without my consent

Bug #823021 reported by Joseph Paul Cohen
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

IDS logs show:
--------------------------------------------------------------------------------------------
"POST http://turtle.libre.fm/nowplaying/1.2/ HTTP/1.1" - - "-" "Rhythmbox/0.13.3"
and
"POST http://turtle.libre.fm/submissions/1.2/ HTTP/1.1" - - "-" "Rhythmbox/0.13.3"
--------------------------------------------------------------------------------------------

Wireshark shows details of what is sent. In this case I'm listening to Nine Inch Nails. This request is sent about ever 30 seconds with my current song. I never enabled this service. It should be off by default.

I feel that this is a privacy risk and should not be allowed.
--------------------------------------------------------------------------------------------
"192.168.0.152","89.16.177.55","HTTP","POST /nowplaying/1.2/ HTTP/1.1 (application/x-www-form-urlencoded)"

0000 00 18 73 6e 0e c8 00 19 d1 7f b8 b9 08 00 45 00 ..sn..........E.
0010 00 9b 60 41 40 00 40 06 0e 94 c0 a8 00 98 59 10 ..`A@.@.......Y.
0020 b1 37 ba 17 00 50 96 30 68 5f 61 06 3a a6 80 18 .7...P.0h_a.:...
0030 00 e5 cc 15 00 00 01 01 08 0a 01 b0 08 41 e3 3c .............A.<
0040 7f 1e 73 3d 35 30 62 36 36 35 66 64 65 64 61 33 ..s=50b665fdeda3
0050 62 38 34 36 31 30 66 32 38 61 31 65 62 66 37 62 b84610f28a1ebf7b
0060 30 30 37 65 26 61 3d 4e 69 6e 65 25 32 30 49 6e 007e&a=Nine%20In
0070 63 68 25 32 30 4e 61 69 6c 73 26 74 3d 48 75 72 ch%20Nails&t=Hur
0080 74 26 62 3d 54 68 65 25 32 30 44 6f 77 6e 77 61 t&b=The%20Downwa
0090 72 64 25 32 30 53 70 69 72 61 6c 26 6c 3d 33 37 rd%20Spiral&l=37
00a0 34 26 6e 3d 31 34 26 6d 3d 4&n=14&m=
--------------------------------------------------------------------------------------------

I'm running Ubuntu 11.04 and Rhythmbox 0.13.3

Revision history for this message
Michael Sheldon (michael-sheldon) wrote :

 I'm not able to reproduce this on Debian (Last.fm plugin enabled, but not authenticated with Libre.fm).

 Could you give some more details about your configuration? e.g. Is the Last.fm plugin marked as being enabled? If you click the "Configure" button for that plugin are both "Last.fm" and "Libre.fm" ticked? If you click the Libre.fm tab in the sidebar what does it show?

 Are you certain that you haven't set up the plugin in the past and just forgotten? The fact that the "s" parameter is filled in your data dump there would seem to indicate that you have authenticated with Libre.fm, as this is the session key which is retrieved as part of the authentication handshake (you'd have had to click the little "Log in" button in the Libre.fm tab at some point in the past, after which it would then be displaying some details from your profile.)

 Cheers,
  Mike.

Revision history for this message
Joseph Paul Cohen (jcccnet) wrote :

I was authenticated, but not using the libre.fm library at the time. I logged out of the service and it stopped sending this data.

I would expect that this data would be sent while I was listening to music from libre.fm but that was not the case.

Thanks for looking into this.

Revision history for this message
Michael Sheldon (michael-sheldon) wrote :

 You can optionally select to not send listening statistics at all (but still listen to Libre.fm) by deselecting the "Submit listening data" option on the Libre.fm tab. However this will also stop it from sending data about the tracks from Libre.fm you've listened to as well.

 Sending all listening data is pretty common for most audio scrobblers, however you might want to raise this upstream and suggest that the wording be clarified so that it's more obvious to people who aren't familiar with other scrobbling services.

Revision history for this message
Walter Garcia-Fontes (walter-garcia) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.

Changed in rhythmbox (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.]

Changed in rhythmbox (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.