Hum, I wonder if this is possible?

[Moh]

Using PHP, you can run scripts on remote servers easily.

In our DJ Panel, we log every IP on everything so we know who ever is connected to the radio is allowed or not.

So, I wonder if it's possible to check the current DJ's IP Address with all the IPs in the DJ Panel and if it's an invalid IP Address, it will kick and ban the IP from connecting.

So then, if somebody has "hacked" the radio, another member of staff can use the script to kick them off air, without having the power to kick off anybody.

Thoughts?

[Mickword]

Hmmm... That sounds quite smart and possible I think. But my only problem is that say if a DJ logs into another computer? I always login on one of my 2 comps or sometimes if im alone at school :P.

[Moh]

Yeah, thats the problem isn't it.

Would be good if SAM instead of entering the encoder details, you download a file that has a "session" key of something that's linked to the account. So if the account doesn't exist, then they can't connect. Sadly that's not possible :(

[Johno]

I don't see why it wouldnt be possible, but a lot of people have dynamic IP's and therefore someone could get kicked as they are thought to be not a proper DJ. A more efficient way to do it would just be to like give admin users the ability to kick people from the server.

[Mickword]

Yeah I agree with Johno.

[Moh]

Yeah, our admins do have the ability :P

[Robbie]

Login to the shoutcast in the same way radio stats does and parse the IP thats currently connected from the XML file then just set a cronjob to check every so often so see if the IP matches one in the database and if not then kick them

[Apolva]

Login to the shoutcast in the same way radio stats does and parse the IP thats currently connected from the XML file then just set a cronjob to check every so often so see if the IP matches one in the database and if not then kick them

OMG I half-wrote exactly this!

[Agnostic Bear]

No. Dynamic IP addresses.

[Moh]

Before their show, they have to click "Start Show" in the DJ Panel so that they don't get infractions for been inactive. So the IP's should always be up-to-date :P

[LMS16]

Before their show, they have to click "Start Show" in the DJ Panel so that they don't get infractions for been inactive. So the IP's should always be up-to-date :P

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.

[Dentafrice]

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 :)

[Moh]

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.
Because they're required to update their DJ Says too and without it, you can't view your requests :D


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 :)
Sounds like a good idea. Would be good to have a DJ Panel built into a desktop application.

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 :P

[Source]

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 :P

Because Spacial Audio quite clearly designed the program for cheap, tacky radio stations where DJ's are young and untrustworthy.

[Blob]

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.

[Jahova]

Virtual DJ FTW :P