Help - Search - Members - Calendar
Full Version: Personal/sensitive data in foobar2000.cfg
Hydrogenaudio Forums > Hosted Forums > foobar2000 > General - (fb2k)
Squeller
As sharing complete layouts is not that easy (comlumns ui fcs is only half of the truth), people tend to share their components and the foobar2000 central configuration file. But there's probably the danger to leak personal information, so this should be considered when sharing.

What I see at the moment is:

1) foosic.org username/password
2) mru's (of visited locations e.g.)

Which personal information come to your mind? Which components store sensitive information within the foobar2000.cfg file?
Bachi-Bouzouk
Not sure but Last.fm plugin may store our password and username
david_dl
QUOTE(Squeller @ Jul 8 2006, 22:14) *
As sharing complete layouts is not that easy (comlumns ui fcs is only half of the truth), people tend to share their components and the foobar2000 central configuration file. But there's probably the danger to leak personal information, so this should be considered when sharing.

What I see at the moment is:

1) foosic.org username/password
2) mru's (of visited locations e.g.)

Which personal information come to your mind? Which components store sensitive information within the foobar2000.cfg file?


AFAIK the foosic component only stores a hash of the password. However this is enough to impersonate that user when sending submissions.

The .cfg files were not designed to be shared, apart from privacy issues there are other issues, such as references to non-existant files, drives and audio devices which could all cause major problems.
bhoar
Hmm. two ideas:

1) Add a foobar2000.prv file, to be used for private storage.
2) Add encrypt/decrypt functions that uses something unique to the user account or windows installation as the key or hash-seed, in order to hide the private items.

-brendan
FrozenSpoon
foo_xm stores username & password in clear text. I probably won't bother changing this since XM's authentication is done via clear text HTTP anyways.
Squeller
QUOTE(david_dl @ Jul 8 2006, 02:38) *
The .cfg files were not designed to be shared, apart from privacy issues there are other issues, such as references to non-existant files, drives and audio devices which could all cause major problems.
I know, but it's still the easiest way to share complete layouts. And there are not major problems but only minor. I tell ppl what settings in preferences they'll have to take care of (with my fb2k it's only media library paths, foo_uie_explorer, foo_playlist_bind, none of them would cause problems). And of course at very first they'll have to change the audio driver setting.

QUOTE(bhoar @ Jul 8 2006, 06:57) *
1) Add a foobar2000.prv file, to be used for private storage.
2) Add encrypt/decrypt functions that uses something unique to the user account or windows installation as the key or hash-seed, in order to hide the private items.

From the concept 1) is a bad idea, as, if you have user_profiles_enabled, configurations somewhere under %appdata% are supposed to be private. 2) is a typical solution, but probably support intensive ("my fb2k does no more work after i reinstalled windows!!!11!")

I wish there was a "export configuration file" function which strips out all sensitive data, mru, whatever, but theres one problem: foobar2000 cannot decide about sensitive data which have been stored by 3rd party plugins.
Rasqual
QUOTE(Squeller @ Jul 10 2006, 10:56) *

I wish there was a "export configuration file" function which strips out all sensitive data, mru, whatever, but theres one problem: foobar2000 cannot decide about sensitive data which have been stored by 3rd party plugins.

Wishlist for 1.0 SDK?
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2008 Invision Power Services, Inc.