Multi-user support

X-Gote · 14th June 2002, 00:42

It would be nice if a user system could be added with a definable set of rules (maybe including allowable connection time(s)/date(s)) and additionaly would be great if the server itself was a bit more flexible to accomidate automated events, perhaps a minimal scripting api? I wish it could reencode incomming connections to a relative bitrate without the need of 3rd party utils.. A guess I wish for more then just a user system hehe.

Great job so far though!
-Dave

X-Gote · 14th June 2002, 19:13

For anyone that is considering some sort of hack for the multi-user idea, I have working up this concept and I am about to test it out this weekend:

Manage you users in a database (or where ever want) using your favorite web scripting language (ie: php!), whip out your favorite packet sniffer and figure out what the header looks like when the plugin trys to connect, then use that header information to snag the login information (for later use). Now with the header information you could rewrite it and using curl, fake a referer from the webserver (using php, drop an exec() or if curls compiled in.. you know what to do)(ie: client trying to connect) then you can use your script as a gateway acting in a multi-user fashion. The trick is probably making the trip back after you have rewrote the header (client connects, checks the password to one in the database, then writes the header to the one in the config file and sends it on its way to the server) to allow the socket to connect properly.

I bet I could make it work to stream through the script running ona webserver to the DNAS just fine, but I anticpate problems with the redirect method. Probably relies on a solid connection being made at all times of the login process? Any developers that read this have any advice for me?

14th June 2002, 00:42	#1
X-Gote Junior Member Join Date: Jun 2002 Posts: 7	Multi-user support It would be nice if a user system could be added with a definable set of rules (maybe including allowable connection time(s)/date(s)) and additionaly would be great if the server itself was a bit more flexible to accomidate automated events, perhaps a minimal scripting api? I wish it could reencode incomming connections to a relative bitrate without the need of 3rd party utils.. A guess I wish for more then just a user system hehe. Great job so far though! -Dave

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode

14th June 2002, 19:13	#2
X-Gote Junior Member Join Date: Jun 2002 Posts: 7	For anyone that is considering some sort of hack for the multi-user idea, I have working up this concept and I am about to test it out this weekend: Manage you users in a database (or where ever want) using your favorite web scripting language (ie: php!), whip out your favorite packet sniffer and figure out what the header looks like when the plugin trys to connect, then use that header information to snag the login information (for later use). Now with the header information you could rewrite it and using curl, fake a referer from the webserver (using php, drop an exec() or if curls compiled in.. you know what to do)(ie: client trying to connect) then you can use your script as a gateway acting in a multi-user fashion. The trick is probably making the trip back after you have rewrote the header (client connects, checks the password to one in the database, then writes the header to the one in the config file and sends it on its way to the server) to allow the socket to connect properly. I bet I could make it work to stream through the script running ona webserver to the DNAS just fine, but I anticpate problems with the redirect method. Probably relies on a solid connection being made at all times of the login process? Any developers that read this have any advice for me?