I would like to know if its possible to restrict access to shares/directories based on who is logged into Twonky Media Server? Right now I have only 1 (!!) user account who can, after authentication, watch anything which can be accessed via Twonky. I do not want my children to be able to watch the latest thriller!
Any ideas? Recommendations?
thanks, Ras
Access restriction / user accounts
-
mgillespie
- Posts:1222
- Joined:Fri Jul 08, 2005 1:19 pm
- AV Hardware:TwonkyMedia AV UPnP Mediaserver (Marvell Kirkwood ARM Sheevaplug with Debian Squeeze).
2x Noxon V2 audio client
1x PS3 Slim 500GB Audio/Video UPnP client.
1x Sony VGF-CP1 Wireless Photoframe. - Location:UK
Re: Access restriction / user accounts
I don't think the DLNA /UPNP protocols allow for authentication.
Perhaps you can setup a cron job (scheduled task, or whatever your OS calls it). and shutdown and startup different servers, at a fixed time of day. So after 10PM, the "daytime" server is shutdown, and a server running from a different config file, with more content is started.
You can specify the config file to use on the commandline.
Will this work?
Perhaps you can setup a cron job (scheduled task, or whatever your OS calls it). and shutdown and startup different servers, at a fixed time of day. So after 10PM, the "daytime" server is shutdown, and a server running from a different config file, with more content is started.
You can specify the config file to use on the commandline.
Will this work?
Please note: Moderators here are voluntary and do not work for PacketVideo or Twonky, please do not attack us. Any posts are personal opinion, and may not be those of PV/Twonky.
Re: Access restriction / user accounts
Thanks for your answer!
1. I run Twonky on unslung NSLU2, so my choice would be setting up a cronjob, but using different config files for different times of the day sounds a little "too work-around" to me. There is an authentication when you log into Twonky WebGui. Has anyone managed to use it with different logins and different access rights on shares.
2. Furthermore: anyone who logs in via web gui is able to tamper with http://home.dns.url/:9100/config Unfortunately there is no way to restrict access to config-page to localhost when you run Twonky on a NAS. Imagine I want to permit somebody access to my music on a remote location via internet but this person should not see my private photo collection.....
Twonky seems to be MY solution BUT there is lots of stuff to do for Dev!
Cheers, Ras.
1. I run Twonky on unslung NSLU2, so my choice would be setting up a cronjob, but using different config files for different times of the day sounds a little "too work-around" to me. There is an authentication when you log into Twonky WebGui. Has anyone managed to use it with different logins and different access rights on shares.
2. Furthermore: anyone who logs in via web gui is able to tamper with http://home.dns.url/:9100/config Unfortunately there is no way to restrict access to config-page to localhost when you run Twonky on a NAS. Imagine I want to permit somebody access to my music on a remote location via internet but this person should not see my private photo collection.....
Twonky seems to be MY solution BUT there is lots of stuff to do for Dev!
Cheers, Ras.