| View previous topic :: View next topic |
| Author |
Message |
pkv
Joined: 26 Jul 2008 Posts: 7
|
Posted: Wed Jul 30, 2008 7:25 pm Post subject: securing icecast |
|
|
hello all,
(i'm double posting from the french forum since the latter's not been very active lately. I'll translate the answers if any in the french forum so that everybody can share.)
I have questions about securing as much as possible the icecast server on a server which will not run a web server.
In particular, I'd like to know if it is possible to filter IP:
- for the sources;
- for access to the admin interface;
Thanks in advance. |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Wed Jul 30, 2008 9:40 pm Post subject: |
|
|
you can deny/accept certain IPs at the point of new connection, but not for limiting particular requests. The only mechanism post connect that could filter on IP is url auth and that only applies to listeners, the stream auth url I have could be used to filter source clients.
karl. |
|
| Back to top |
|
 |
pkv
Joined: 26 Jul 2008 Posts: 7
|
Posted: Wed Jul 30, 2008 10:13 pm Post subject: |
|
|
| karlH wrote: |
you can deny/accept certain IPs at the point of new connection, but not for limiting particular requests. The only mechanism post connect that could filter on IP is url auth and that only applies to listeners, the stream auth url I have could be used to filter source clients.
karl. |
thanks for the info.
I'll pick then a very strong password for the admin.
And use stream auth url . |
|
| Back to top |
|
 |
|