Depending on your software, the implementation varies, but the mechanism is the same. UDP cancels are posted such that they look like they came from a site called udpcancel. You need to set up your software to reject articles with "udpcancel" in the Path: header.
The faq mentions somehting about this towards the bottom, but it's not really obvious.
we have a business partner that charges for access to their news server. This is the personal newsreader service. You can point tin or trn or nutscrape at it and read news that way without ads. That's why they charge for it.
and if I thought we could get away with it, I'd kill the ads myself. but you're right, I don't have anything to do with that. And unfortunately we need the ads to pay my salary.
I'm not going to post it again as it's been posted several times in thei thread and also in the usenet article.
Call and complain. @Home hasn't been listening to complaints. That's the whole problem. Maybe this will make all of their customers complain and they might see some $$$ floating away from them. Maybe then they'll listen to complaints
deja has a personal newsreader service (unfortunately it's a pay $ervice) where you can point tin at a news server. check out http://www.bcandid.deja.com/
the way a UDP works is that several news admins are generating cancel messages for articles originating from @Home. If you go read the UDP FAQ you would know this. Anyone not wishing to participate in an active UDP can refuse to accept articles from the pseudosite udpcancel. All cancels delaing with an active UDP have udpcancel in their path header.
So, the majority of usenet admins are participating simply because they haven't chosen to ignore these cancels.
Even if a site that ignores these cancels passes them on to another site which honors these cancels, the second site will get the cancels and the messages will go away. (It's magic!) The only news servers where the articles originating from @Home will be found are the guys who ignore the udpcancels.
And not to try to impress you, but I do control a major newsfeed. You can also reach me at my deja.com address. I'm their primary news admin.
yes, when I'm hacking code, I'm hacking. But when I'm hacking on a project in my garage using a blowtorch, a car battery, jumper cables, and a sheet of lexan, am I coding?
"I figured, therefore, Linux source code would have to be shielded from young eyes, lest they get the impression that "fuck" is a valid engineering term."
no. that's how many of these phone book companies make their money. Repackaging of data like that isn't prohibited.
The problem comes in when you read the clause in the precident about the data being collected through automatic or mechanical means.
Have you seen adds in classifieds about writing down phonebook entries and mailing them to someone for money? That's what this is. Someone collecting data manually for re-publishing.
A Windows NT network takes about 5 seconds to install and configure.
5 seconds?? talk about reality! try to get some soon.
ok, samba may not be a breeze to set up, but I've replaced heavily loaded NT file servers with a samba box & the only reason anyone noticed was because it quit crashing.
there are also some Tk smb config tools coming out IIRC. (or maybe they're already out?)
It sounds like there is going to have to be a policy set. "all systems will comply to the security guidelines outlined at (some URL) or they will not be allowed on the network."
Once you get the guidelines set, implement some detection measures (the easy part as you put it) and some automated notification. after some number of warnings (say 3 in as many weeks) just filter all their packets at the router (based on their MAC address).
Yes, it wouldn't take much to change your MAC address, but then they've intentionally circumvented policy & that, I'm sure, is covered in some other policy, with it's own punishment.
Depending on your software, the implementation varies, but the mechanism is the same. UDP cancels are posted such that they look like they came from a site called udpcancel. You need to set up your software to reject articles with "udpcancel" in the Path: header.
The faq mentions somehting about this towards the bottom, but it's not really obvious.
we have a business partner that charges for access to their news server. This is the personal newsreader service. You can point tin or trn or nutscrape at it and read news that way without ads. That's why they charge for it.
and if I thought we could get away with it, I'd kill the ads myself. but you're right, I don't have anything to do with that. And unfortunately we need the ads to pay my salary.
Yes.
This only affects articles originating on @Home's usenet servers. If you post through Deja, you're posting through one of my servers.
read the UDP FAQ.
I'm not going to post it again as it's been posted several times in thei thread and also in the usenet article.
Call and complain. @Home hasn't been listening to complaints. That's the whole problem. Maybe this will make all of their customers complain and they might see some $$$ floating away from them. Maybe then they'll listen to complaints
deja has a personal newsreader service (unfortunately it's a pay $ervice) where you can point tin at a news server. check out http://www.bcandid.deja.com/
regarding deja...
if informed about users causing problems, we can (and do) revoke their posting privs.
If you're seeing such the volume of spam that you;re claim to, then you should let our helpdesk know (help@deja.com)
if you can use a web browser, you can read news.
You can post news.
check out deja.com
the way a UDP works is that several news admins are generating cancel messages for articles originating from @Home. If you go read the UDP FAQ you would know this. Anyone not wishing to participate in an active UDP can refuse to accept articles from the pseudosite udpcancel.
All cancels delaing with an active UDP have udpcancel in their path header.
So, the majority of usenet admins are participating simply because they haven't chosen to ignore these cancels.
Even if a site that ignores these cancels passes them on to another site which honors these cancels, the second site will get the cancels and the messages will go away. (It's magic!) The only news servers where the articles originating from @Home will be found are the guys who ignore the udpcancels.
And not to try to impress you, but I do control a major newsfeed. You can also reach me at my deja.com address. I'm their primary news admin.
use the phone.
I know that may be a foreign concept, but the brokers are very helpful.
catchy tunes?
Well, I guess "Uncle Fucker" was pretty good....
someone moderate this down as it's obviously just a troll
So, does this mean they'll stop shipping their product with perl4 and use perl5 instead?
I buy black felt & after I nuke the CD's for about 5 sec, I glue the felt to the label side, and voila! A coaster!
coder does not completely replace hacker.
yes, when I'm hacking code, I'm hacking. But when I'm hacking on a project in my garage using a blowtorch, a car battery, jumper cables, and a sheet of lexan, am I coding?
But wait, isn't "fuck" a valid engineering term?
I believe what you're looking for is smbclient or smbmount.
note: for smbmount, you'll have to have smbfs support in your kernel.
so don't register....
use the cypherpunk login
I can't assume you already know this (remember what Benny Hill said....), so if you're looking for linuxppc help, have you looked at linuxppc.com?
I'm not a linuxppc person, but it looks like a pretty good site to me.
Good luck!
you need to go look at the hacks page. The hack in question is here
no. that's how many of these phone book companies make their money. Repackaging of data like that isn't prohibited.
The problem comes in when you read the clause in the precident about the data being collected through automatic or mechanical means.
Have you seen adds in classifieds about writing down phonebook entries and mailing them to someone for money? That's what this is. Someone collecting data manually for re-publishing.
yeah... sure. That's the way it worked for me.
The seventh or eighth time I think it finally worked.
A Windows NT network takes about 5 seconds to install and configure.
5 seconds?? talk about reality!
try to get some soon.
ok, samba may not be a breeze to set up, but I've replaced heavily loaded NT file servers with a samba box & the only reason anyone noticed was because it quit crashing.
there are also some Tk smb config tools coming out IIRC. (or maybe they're already out?)
It sounds like there is going to have to be a policy set. "all systems will comply to the security guidelines outlined at (some URL) or they will not be allowed on the network."
Once you get the guidelines set, implement some detection measures (the easy part as you put it) and some automated notification. after some number of warnings (say 3 in as many weeks) just filter all their packets at the router (based on their MAC address).
Yes, it wouldn't take much to change your MAC address, but then they've intentionally circumvented policy & that, I'm sure, is covered in some other policy, with it's own punishment.
don't recognize sarcasm when it bites you in the ass huh?
Yeah, let's start the /... revoloution