Displaying 20 results from an estimated 6000 matches similar to: "[Fwd: IceCast up to v2.20 multiple vulnerabilities]"
2004 Aug 06
2
Hello everyone, here is some php code.
Okay,
So remember that question I had last week about taking a bunch of relay servers
and greping the status2.xsl file for the number of listeners? I coded it. I
have to apologize right now, as its krufty, nasty, braindead code. But it
works, and I'm rather proud that after being up as long as I have been up
and drinking as much coffee, it works. It should be attached to this e-mail.
I
2004 Aug 06
1
PHP + parsing # of listeners.
Hello all,
I have a quick question I believed was already touched on earlier, but I cannot
find the thread/information in the archives, so I am going to ask away and
ask for your patience. :)
So I have my wonderful little PHP script, and my .pls files, and the relaying
and everything else perfect for my icecast2 setup. But what I still need to
do is pull the # of listners for a mount point, and
2004 Aug 06
1
could not start logging
Hello!
Whenever I get that error, its due to either the directory/file not existing,
or having the wrong file permissions. Remember, it needs the file permissions
of the user you created to be "icecast".
Happy holidays all
--stauf
On Wed, Dec 31, 2003 at 05:00:39PM -0800, jensen galan wrote:
> Greetings!
>
> Running into a snag when trying to fire up icecast:
>
>
2006 Oct 31
0
PSARC 2005/572 PKCS#11 v2.20
Author: izick
Repository: /hg/zfs-crypto/gate
Revision: f7c96af91f148327ba792c8fbcb9e49897664f9c
Log message:
PSARC 2005/572 PKCS#11 v2.20
4920408 PKCS#11 v2.20 support for the Crypto Framework
6287425 residual bzero''s in hmac part of sha2
6287428 add sha2 to the i.kcfconfbase upgrade script
Files:
create: usr/src/common/crypto/blowfish/blowfish_cbc_crypt.c
create:
2006 Oct 31
0
6368332 libpkcs11 should report that it is v2.20 not v2.11
Author: darrenm
Repository: /hg/zfs-crypto/gate
Revision: 14d7bfad76ad917e7df568c6739d34eba6b60a33
Log message:
6368332 libpkcs11 should report that it is v2.20 not v2.11
Files:
update: usr/src/lib/pkcs11/libpkcs11/common/pkcs11Conf.c
update: usr/src/lib/pkcs11/libpkcs11/common/pkcs11Global.h
2004 Aug 06
2
icecast hangs at start
thanks for the reply.
the problem is after i start icecast with icecast -c
/path to icecast.xml, i see the following:
Changed groupid to 501.
Changed userid to 501.
and then it just hangs. i do not get a command prompt
or anything. so i was wondering if there are any
other messages that normally follow during the startup
process.
<p>--- Karl Heyes <karl@xiph.org> wrote:
> On
2004 Aug 06
5
Stream metadata settings
Actually, Sorry guys, I just want to say the below paragraph is misrepresenting.
You can stream music without "paying the piper" without being in copyright
hell. And as a long time icecast user/admin/client/server/whatever, that
below paragraph just makes me really sad to see on this list.
...I'll lurk now.
--Stauf
> When people run icecast without registering their server and
2004 Aug 06
2
One more question of possible note.
Hello again all.
I want to thank Karl H. for pointing me to xiph.org/~karl and getting me
some save files winamp likes the first time. That ucler is at an end.
The next ucler involves two rather quick questions:
I > In icecast1, when a user attempted to connect to the server, didn't it
just kick them to the "default stream", where the default stream was the only
stream being
2006 Jul 18
2
Vulnerability in vixie cron?
Hi,
Recently there have been advisories and patches for
SuSE and RedHat (and probably a few others) regarding
a vulnerability in Vixie Cron. The details say that
there's insufficient checking of the return value of
setuid, which can lead to priviledge escalation and
lets users run cron jobs with root priviledges.
As far as I know, FreBSD also uses Vixie Cron (at least
the cron(8) manpage
2015 Dec 06
1
Listener statistics on a fallback stream
Hello,
On 06-12-15 13:58, Yahav Shasha wrote:
>
> >To me it sounds like a bug; surely the fallback never needs
> statistics,
> only the real steam because this is where listeners connect to.
>
>
> Well, the fallback mount is still a mount-point nonetheless. you could
> still use it as a "regular" mount-point even if its configured as a
>
2004 Aug 06
1
Anyone want to be my hero?
Hello everyone,
I've been using icecast 1 for a long time, and icecast2 has become a
very viable alternative now. There is only one small and rather silly
thing holding me back.
I use liveice for everything. Has anyone hacked liveice to work with
icecast2 and ogg? Is anyone writing another client that isn't darkice?
I would try and port and rewrite, but my coding skills need
2004 Aug 06
1
make problems on libshout CVS.
Yep. That one was right on the nose. Sorry about that folks, I was using
the simple "I'm going to the web cvs and downloading the tarball" instead of
cvs -f -d :pserver:anoncvs@xiph.org:/usr/local/cvsroot login way of doing things
Thanks for the fast reply. I am humbled. :)
On Thu, Mar 13, 2003 at 07:11:44PM +1100, Michael Smith wrote:
> On Thursday 13 March 2003 18:16, Mr.
2015 Mar 13
1
IceCast status - raw XML output
Please add the following XSL file to IceCast distribution (web directory). It returns IceCast's state in raw XML form.
<xsl:stylesheet xmlns:xsl = "http://www.w3.org/1999/XSL/Transform" version = "1.0">
<xsl:output indent="yes" encoding="UTF-8" />
<xsl:template match="@* | node()">
<xsl:copy>
2006 Mar 16
1
script.aculo.us in xsl
Hello, first of all, sorry for my English, I´m a Spanish student and I´m
having some problems with script.aculo.us. These are the following:
I have a XML file like this:
<?xml version="1.0" encoding="iso-8859-1"?>
<?xml-stylesheet type="text/xsl" href="barraNav.xsl"?>
<barraNav>
<boton>
2004 Aug 06
2
commas are status2.xsl?
in the status2.xsl there seems to be some extra commas ...
--snippet of status2.xsl
Global,Client:<xsl:value-of select="connections" /> Source:
<xsl:value-of select="source_connections" />,,<xsl:value-of
select="listeners" />,,
<xsl:for-each select="source">
<xsl:value-of select="@mount" />,,<xsl:value-of
2004 Aug 06
2
icecast status page -status.xsl
So I point my browser to
http://206.168.174.48:8000/status.xsl
Looking at the xsl doc status.xsl I some some nice variables I can
use. For some reason I don't seem to be able to pull out the comment
tag from the ogg file. I used to easytag to add this so i know it
exists.
These appear to work
<xsl:value-of select="artist" /> -
<xsl:value-of select="title"
2004 Aug 06
2
Custom .xsl files?
On Thursday 22 July 2004 04:56, Myke Place wrote:
> I'm curious if it is possible to create custom .xsl files in the /admin
> directory, using the same xsl params that appear in in the web
> interfaces that ship with Icecast2.
Yes. Though I don't know if using an arbitrary one works from the admin
directory. Certainly you can put them in icecast's webroot directory (or some
2006 Feb 17
1
Scriptaculous XSLT-sheet available for download
Hiya!
Being very impressed and pleased with scriptaculous I decided to add
several features of it into a Web Publishing System I’m building.
This WPS (as I fondly call it) makes extensive use of XML/XSLt
translations.
To offer some nice visual effects to customers I made a XSL-stylesheet
which allows my customers to access these effects by enclosing some
content into scriptaculous-tags.
I decided
2020 Sep 21
2
Listener stats
Hello Jordan
Thanks for the reply. I commented out all the fields in the
status-json.xsl but it didn't give me the listener IP. The example
below would show me the source IP. I can get the IP from the web
interface at this location,
http://xxx.xxx.xxx.xxx:8000/admin/listclients.xsl?mount=/dhantal, but
that means I would have to scrape the web interface which I don't want
to do.
2020 Sep 22
2
Listener stats
Good afternoon,
On Tue, 2020-09-22 at 11:43 -0400, Reaz Baksh wrote:
> Too much work.
I would like to refer to Jordan Erickson's comment here.
> If I am able to see it on the web interface I should be able to get a Json or XML file with this in it.
Why not just use the API? Remove the ".xsl" from any URL in the admin
interface and get the raw XML. The rendered webinterface