similar to: help writeing rule for preventin spam

On Monday 01 March 2004 23:42, Stefan Neufeind wrote: > Hi, > > I know this has been discussed before - but I don't think that we've > come to a "clean" solution. So let me try to ask again: > > Is there any good way with icecast to prevent browsers / wget's / ... > from capturing a stream? I mean, using Shoutcast afaik it's not > *that* easily

On 8 Mar 2004 at 14:30, Rakotomandimby Mihamina wrote: > On Tuesday 02 March 2004 02:23, Michael Smith wrote: > > Shoutcast just does user-agent sniffing. This makes it look like you > > can't download the stream easily, but that's just misleading you - > > it's completely trivial to do so. > > Yes , i'd say the same. > > > > The most clean

Hi, I know this has been discussed before - but I don't think that we've come to a "clean" solution. So let me try to ask again: Is there any good way with icecast to prevent browsers / wget's / ... from capturing a stream? I mean, using Shoutcast afaik it's not *that* easily possible to download a stream. But using Icecast you can simply do a wget and grab the

On Tuesday 02 March 2004 02:23, Michael Smith wrote: > Shoutcast just does user-agent sniffing. This makes it look like you can't > download the stream easily, but that's just misleading you - it's > completely trivial to do so. Yes , i'd say the same . > > The most clean solution in my eyes would be to implement mms:// or > > rtp:// for mp3/ogg-streams in

Hi everybody, I a, trying to use R as a pipe like this: cat inputData | R --silent RCommandFile >outputData The RCommandFile would contain something like readLines(stdin()). I have tryed various things and none did work cleanly. One possible solution is to use the pipe() function inside R and to pass in the "cat inputData" however this is not very convenient since I would like to

Hello, I have what I would think would be a common situation: I run asterisk at home simply as a land line. I started a new job working remotely and they gave me a SIP account with user name, domain, and proxy. I've never had to deal with sip domains before. My user '140 at 4354766787.com' is handled by a 3rd party provider: 'sip.provider.com' and my local domain on my

Hi Kirill, Thanks for your reply. Such a simple flat file approach would be perfect, and I don't mind at all to require app specific usernames *and* passwords. However, I am unsure how to combine your recipe below with our regular AD userdb/passdb. Perhaps someone can give me some pointers in that direction? MJ On 07/20/2017 06:50 PM, Kirill Miazine wrote: > I'm not familiar

Hi, Further to the other thread about password guessing activities against our dovecot, I would like to implement application specific passwords on our dovecot. Googling results in some documents, but they are all a bit older: > https://www.happyassassin.net/2014/08/26/adding-application-specific-passwords-to-dovecot-when-using-system-user-accounts/ >

I am the sysadmin in an office with an overabundance of Win95 machines and a few NT 4.0 workstations. All installs went relatively easy for logon scripts, wins, etc. I have run into a semi-serious problem with 2 of the 3 NT workstations. (All running the same service pack - 1). When trying to make a share from one of the 2 remaining workstations, I will recevie an error message saying that:

Hi, mj * mj [2017-07-20 13:29]: > Hi, > > Further to the other thread about password guessing activities against our > dovecot, I would like to implement application specific passwords on our > dovecot. [...] > > Is there anone here with some additional notes, ideas, tips, trics on > setting up application specific passwords with dovecot with virtual users? > We are

I transferred a Xen vm that was running on centos 5.7 with samba 3.6.3 to a centos 6.2 bare metal server with one E5502 and 16gig of memory. I have been running Centos for 6 years on different servers for 6 years on several different upgrades. This new server has a dual network card in it. I have samba 3.6.3 on it and here is the smb.conf below: [global] workgroup =

Guess I got where your confusiion lies.... you DON'T set up the ALL contexts the users will have acces to in sip.conf, in this file you will only set 1 single context. All other contexts you want the users to have acces to, you will have to add them in the extensions.conf So what you have to do is the following: -user 2092, set it the createmenu context in sip .conf - in extensions.conf

Dear list, before writeing this mail I really searched in the mailing list and deeply red the HOWTO, but I didn''t find a clear and univoque answer to my doubt. What is the meaning of the priomap? And what kind of TOS concerns? My first opinin was the one-to-one correspondence of the priomap and the 16 values of the four TOS bits. I mean priomap 1 2 0 3 0 0 0 0 0 0 0 0 0 0 0 1 implies

On Thu, 9 Oct 1997, Lowell C. Savage wrote: > I didn't see a description in the various messages of where the file actually > is written. If it is written to the \\server\netlogon directory, don't you > get a locking problem with two or more users loggin in? I mean, if you have > a slow client logging on with one user, and a moment later, another user > logging on another