renaissanceboy wrote: > first of all: if i forward ports 9000 and 3843 (or whatever they are), > what real-life security risks does that pose? > second: if i use slimserver's password protection (which i do), does > that offer a significant amount of protection? > third: is it a good idea, as i saw that someone has done, to create a > separate user account for slimserver that only has access to my music > folder?
Do you mean forward without any security? or forward with SSL or equivalent? In general, IMHO, it is a really bad idea to propagate open ports in the wild. What do you mean by "separate user account"? The default setup on Linux slimserver distos is to use a limited 'slimserver' user for exactly the kinds of basic security you are talking about. But it is by no means 'secure' in any serious sense. > so if i don't have any slim devices hardware (which i don't) the only > security risk is that someone could listen to/download my music? i'm > all right with that risk as long as there's no (or no significant) > danger of my files or network in general being accessed. You can't say this. You don't know that some bad person won't access your machine over say 9000 and feed bad commands that cause the SlimServer to react in weird and bad ways. It is unlikely, at least if you aren't using Windows, but you can't know. No one can know. There are some advantages to the SlimServer being written in Perl, it is less likely to have the kinds of buffer overflow problems that other languages can have,but that doesn't mean it is 'safe'. There is no such thing as a safe language in widespread use. Why not just use putty or other SSL tool to forward the ports under SSL? Its a ton safer. IANAL, but the RIAA and others may have differing views on your liability if you allow other folks to listen to your music. -- Pat http://www.pfarrell.com/music/slimserver/slimsoftware.html _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
