
Why not check whos show is next, when they login, update the database rather than them clicking a button everytime, alot of people would forget. It sounds a good idea though
Lew.
Basically here is what I would do.. if it was me..
Have a desktop application that the DJ used before each show to send an update to your server.. the server catches the IP address and adds it to the database. That way the IP is always up to date.
Have a cron job that runs every so often.. it checks the radio stream IP, then compares it.. if it is not in the database, it kicks them off.
Inside of the desktop application they would have to enter their username and password to the panel or something of the sort. That way if someone gained access to the panel.. they still couldn't update their IP address.. they would need the application.
If the panel was attacked, the application could easily check to see if the application has been disabled and not allow any IP updating.
I did this on a similar project, worked great. Could implement it to only allow them to update their IPs on dates / times (within 10 minutes?) of their shows they have booked.
Just a few ideas![]()
Because they're required to update their DJ Says too and without it, you can't view your requests
Sounds like a good idea. Would be good to have a DJ Panel built into a desktop application.Basically here is what I would do.. if it was me..
Have a desktop application that the DJ used before each show to send an update to your server.. the server catches the IP address and adds it to the database. That way the IP is always up to date.
Have a cron job that runs every so often.. it checks the radio stream IP, then compares it.. if it is not in the database, it kicks them off.
Inside of the desktop application they would have to enter their username and password to the panel or something of the sort. That way if someone gained access to the panel.. they still couldn't update their IP address.. they would need the application.
If the panel was attacked, the application could easily check to see if the application has been disabled and not allow any IP updating.
I did this on a similar project, worked great. Could implement it to only allow them to update their IPs on dates / times (within 10 minutes?) of their shows they have booked.
Just a few ideas
Would be good if Special Audio implemented a feature where you can connect to a sever to fetch the encoder details using the username and password. That way a DJ will never know the actual password![]()
Because Spacial Audio quite clearly designed the program for cheap, tacky radio stations where DJ's are young and untrustworthy.
Make it so when the user has to login the next step is to upload a text file with certain, randomly generated contents in it. Check the MD5 hash of the uploaded file and compare it to the one in the database. It will be a different file for everyone, so store the MD5 hash in the user table.
People aren't going to be able to guess their username and password and then magic up a txt file corresponding to the account.
Please note - if your talking about being hacked radio info way without access to the panel, sorry, my mistake. This though, could secure the panel more.
Virtual DJ FTW![]()
"RETIRED" FROM HABBO(X)
:¬:
TOMSPIT / COWLY05
Want to hide these adverts? Register an account for free!