Some of our customers' highest-end workstations are SGIs. (There are also a couple Sun Blade 2000s and a LOT of IBM RS/6000s.) SGI will continue selling IRIX and the machiens it runs on until they no longer make money doing so.
SBDs are usually a little deader-sounding than AUDs however. Normally, when someone gives me a SBD feed, I usually do a SBD/AUD matrix mix, just to capture the crowd too. There are a few shows on archive.org that I've taped that way and I tend to favor them over anything else.
As for serious about quality: there's a point of diminishing returns that some people seem to think doesn't exist in the taping subculture... It's kind of depressing to watch a kid with a mini-me and a v2 aim his mk4s at the stacks. I'd say 60% of taping is technique, the other 40% is gear.
XML, as a language spec, is most certainly open. It's what you do with the spec that makes it closed. C is also an open spec, but if I write a program in C, I'm by no means obligated to give everyone the source code to it (despite what some people here insist is the "right thing to do" in all cases.)
I feel bad for you. I don't even know what our products did. I just know they paid me to browse the web all day, and burn my MP3s at work. I think I was also the official pizza orderer for a while.
What you're proposing will cost no less than a high-quality AIT drive, which, though you may need to span tapes in the most extreme of situations, will give you quite a bit of capacity. You can pick up 90GB native-capacity AIT drives now for around $500 or so on eBay. The media is affordable, too.
This at least makes reasonable sense. Unfortunately, the identd requirement still breaks IRC for anybody behind a reasonably-sized firewall, unless the admins pass identd through to the inside (yet another security issue IMO).
The reason you are so confused is because you think that identd is supposed to help you in some way. It doesn't help you as the IRC server admin.
Then why do IRC server admins require it?
The ident information is to help the administrator of the client. You see, if your abusive user is on a shell account, and you go to report abuse to the service provider, that admin is going to ask you for the ident information. Without it he is not going to know which of his users is the abuser. If you turn it off identd checking, you will have no recourse against the abuse.
So, if I go to report an abusive user, and his ident string is "gofuckyourself@some.unix.box.somewhere", you're saying, chances are, it'll be helpful, even when 99% of ident responses are phony? Does anyone even read their "root@" or "abuse@" email? In my experience, these mailboxes go to/dev/null, either explicitly or through neglect.
Why not just ditch ident, and simply ban the entire hostname, subnet, or domain of an abusive user, and let the admin sort it out once he starts receiving complaints from other, legit users? Hell, this is done all the time, anyway. When's the last time you saw a K-line for a single user@unix.box?
Requiring everyone to run ident simply because there are one or two abusive shell account users out there is downright retarded. It's like forcing backward compatibility for Netscape 1.1N users. The times, they have a-changed. Ident must die.
Now, which do you think is the more likely scenario: All the l-users here that have never run an IRC server and are taking out of their ass know best, or that hundreds of experienced server and network ops know what they're doing and require identd for a reason?
I've run several IRC servers since 1996. I am an "experienced server and network op", and I still can't figure it out. Speaking as an admin, I can assure you that ident buys me absolutely nothing in terms of dealing with problematic users. Every single one of them has spoofed a valid ident response, either by changing their "Username" value in mIRC, or by running a randomizing ident server. The commonly-held belief among IRC admins that ident provides security and some sort of audit trail is unquestionably false.
I turned off ident checking on my servers a few months ago, and encourage others I know to do the same.
First of ident is not insecure by itself. Some implementations had buffer overflow problems, but then wich server software hasn't. It can also provide login information like the username but this depends on the setup. For correct working, IRC related, it just needs to return a string on query.
Not true. The real ident servers need to run as root (since they're running on a low port), or if you want to be fancy, they can be started by root and assume another (perhaps jailed) user's identity. Let's assume they all running as root, since I've not seen one that doesn't do so. They need to access/etc/passwd (or the NIS equivalent) as well. Some day or another, someone will figure out a way to exploit the most common version of the ident server(s). It's happened before, it'll happen again.
I tend to treat every service I run on my machines as exploitable. To this end, I disable as many as possible, and, if I have to run a service, I make sure I keep up with it from a security standpoint. Running ident is more work for me, for no real reason.
That someone requires I run a useless service like identd in order to connect to their network has always bugged me. In this day and age, when ident responses are faked far more often than they aren't (EVERY Windows IRC client fakes ident!!), what's the point of opening up a low port and exposing my systems to even more abuse?
So why require ident to be running? Can't it be as easily changed as the nick? Yes it can, on certain setups.
On just about every setup, you mean.
However if you are using/abusing a shell account then the Ident service should be fixed by the admin. It makes therefore the misuse of a certain kinda setup harder (University accounts).
Very few people use their university shell accounts to IRC these days.
Shell accounts are popular for abuse since you are using someone elses IP for youre abuse.
So are Wingate hosts, but there are other ways of dealing with that kind of abuse, as well. If someone's fucking with my server from a shell account (or from anywhere else), banning that hostname or IP range is more than enough.
Other posts have indicated that there are plenty of Ident servers for windows around. Saying just because windows does not support something it is obsolete is stupid. There are plenty of things on windows you need third party apps for.
Yes, and others have noted that "ident" is built into most Windows IRC clients. In nearly all cases, on Windows, ident is faked; I can type whatever I want into the "Username" box in mIRC.
Slashdot Mirror
Some of our customers' highest-end workstations are SGIs. (There are also a couple Sun Blade 2000s and a LOT of IBM RS/6000s.) SGI will continue selling IRIX and the machiens it runs on until they no longer make money doing so.
- A.P.
It came with my computer, so it's free.
Also, I can download it off the Internet from several places.
Nobody cares that Linux doesn't cost money.
- A.P.
Just because it looks like XP doesn't mean it runs the same programs as XP. This has no connection whatsoever to Lindows.
- A.P.
...but I make it a point to never buy from a company that advertises with half-naked popup ads.
- A.P.
If so, feel free to use this one:
"FOR SALE: SLIGHTLY USED"
- A.P.
I'll be at MSG, the Vegas shows, and Greensboro.
Managed to somehow get 4 TS tickets in a row to MSG... it will be a good night.
- A.P.
SBDs are usually a little deader-sounding than AUDs however. Normally, when someone gives me a SBD feed, I usually do a SBD/AUD matrix mix, just to capture the crowd too. There are a few shows on archive.org that I've taped that way and I tend to favor them over anything else.
As for serious about quality: there's a point of diminishing returns that some people seem to think doesn't exist in the taping subculture... It's kind of depressing to watch a kid with a mini-me and a v2 aim his mk4s at the stacks. I'd say 60% of taping is technique, the other 40% is gear.
- A.P. (TLM-170s rocked it last night)
...when we have the Slashdot Cruiser?
Did whoever won that thing actually show up to claim it?
- A.P.
XML, as a language spec, is most certainly open. It's what you do with the spec that makes it closed. C is also an open spec, but if I write a program in C, I'm by no means obligated to give everyone the source code to it (despite what some people here insist is the "right thing to do" in all cases.)
- A.P.
Yes, mister Hairtrigger, we should sue Microsoft simply because they won't release trade secrets. We will surely win.
- A.P.
Ah, you're the shithead who runs "Troll Blacklist". Yeah, I wish you posted at -1, too.
- A.P.
Not at all. And I had a better-paying job in 2 weeks. My 5 weeks' severance pay hadn't even run out.
- A.P.
Wow.
I feel bad for you. I don't even know what our products did. I just know they paid me to browse the web all day, and burn my MP3s at work. I think I was also the official pizza orderer for a while.
- A.P.
All these levies mean music piracy is, therefore, perfectly legal in Canada.
So quit whining.
- A.P.
...the day after the Christmas party, half the office was laid off.
So, mister whining bobblehead-doll recipient, kindly "eat a bag of dicks".
I know plenty of people who'd have accepted a bobblehead doll and a job instead of what they got last year.
What is the difference between the European space program and an old man?
The old man can maintain an erection with the aid of prescription drugs!
- A.P. (SLASHFUNNY post of the day)
What you're proposing will cost no less than a high-quality AIT drive, which, though you may need to span tapes in the most extreme of situations, will give you quite a bit of capacity. You can pick up 90GB native-capacity AIT drives now for around $500 or so on eBay. The media is affordable, too.
- A.P.
I prefer trebuchet.
- A.P.
You were right.
- A.P.
Congratulations to the OpenBSD folks for finally joining the 20th century. I will soon be able to run OpenBSD on my dual-CPU 486 server from 1992.
Next year, I hear they'll have something new called "ipv6".
- A.P.
This is going to have about 1500 comments by the end of the day.
- A.P.
This at least makes reasonable sense. Unfortunately, the identd requirement still breaks IRC for anybody behind a reasonably-sized firewall, unless the admins pass identd through to the inside (yet another security issue IMO).
- A.P.
The reason you are so confused is because you think that identd is supposed to help you in some way. It doesn't help you as the IRC server admin.
Then why do IRC server admins require it?
The ident information is to help the administrator of the client. You see, if your abusive user is on a shell account, and you go to report abuse to the service provider, that admin is going to ask you for the ident information. Without it he is not going to know which of his users is the abuser. If you turn it off identd checking, you will have no recourse against the abuse.
So, if I go to report an abusive user, and his ident string is "gofuckyourself@some.unix.box.somewhere", you're saying, chances are, it'll be helpful, even when 99% of ident responses are phony? Does anyone even read their "root@" or "abuse@" email? In my experience, these mailboxes go to
Why not just ditch ident, and simply ban the entire hostname, subnet, or domain of an abusive user, and let the admin sort it out once he starts receiving complaints from other, legit users? Hell, this is done all the time, anyway. When's the last time you saw a K-line for a single user@unix.box?
Requiring everyone to run ident simply because there are one or two abusive shell account users out there is downright retarded. It's like forcing backward compatibility for Netscape 1.1N users. The times, they have a-changed. Ident must die.
- A.P.
- A.P.
Now, which do you think is the more likely scenario: All the l-users here that have never run an IRC server and are taking out of their ass know best, or that hundreds of experienced server and network ops know what they're doing and require identd for a reason?
I've run several IRC servers since 1996. I am an "experienced server and network op", and I still can't figure it out. Speaking as an admin, I can assure you that ident buys me absolutely nothing in terms of dealing with problematic users. Every single one of them has spoofed a valid ident response, either by changing their "Username" value in mIRC, or by running a randomizing ident server. The commonly-held belief among IRC admins that ident provides security and some sort of audit trail is unquestionably false.
I turned off ident checking on my servers a few months ago, and encourage others I know to do the same.
- A.P.
First of ident is not insecure by itself. Some implementations had buffer overflow problems, but then wich server software hasn't. It can also provide login information like the username but this depends on the setup. For correct working, IRC related, it just needs to return a string on query.
/etc/passwd (or the NIS equivalent) as well. Some day or another, someone will figure out a way to exploit the most common version of the ident server(s). It's happened before, it'll happen again.
Not true. The real ident servers need to run as root (since they're running on a low port), or if you want to be fancy, they can be started by root and assume another (perhaps jailed) user's identity. Let's assume they all running as root, since I've not seen one that doesn't do so. They need to access
I tend to treat every service I run on my machines as exploitable. To this end, I disable as many as possible, and, if I have to run a service, I make sure I keep up with it from a security standpoint. Running ident is more work for me, for no real reason.
That someone requires I run a useless service like identd in order to connect to their network has always bugged me. In this day and age, when ident responses are faked far more often than they aren't (EVERY Windows IRC client fakes ident!!), what's the point of opening up a low port and exposing my systems to even more abuse?
So why require ident to be running? Can't it be as easily changed as the nick? Yes it can, on certain setups.
On just about every setup, you mean.
However if you are using/abusing a shell account then the Ident service should be fixed by the admin. It makes therefore the misuse of a certain kinda setup harder (University accounts).
Very few people use their university shell accounts to IRC these days.
Shell accounts are popular for abuse since you are using someone elses IP for youre abuse.
So are Wingate hosts, but there are other ways of dealing with that kind of abuse, as well. If someone's fucking with my server from a shell account (or from anywhere else), banning that hostname or IP range is more than enough.
Other posts have indicated that there are plenty of Ident servers for windows around. Saying just because windows does not support something it is obsolete is stupid. There are plenty of things on windows you need third party apps for.
Yes, and others have noted that "ident" is built into most Windows IRC clients. In nearly all cases, on Windows, ident is faked; I can type whatever I want into the "Username" box in mIRC.
- A.P.