CSI debuted in 2000. Da Vinci's Inquest debuted in 1998 and ran for 7 seasons. It's not exactly an original idea so I'm not accusing anyone of copying anyone, but let's be realistic here.
Toss North of 60 in there, if you're into that sort of thing.
Most of those shows have been exported to other countries, so I guess we're doing something right. We're no better and no worse than the Americans. We both put out a lot of crap and a few gems.
Reading through this, I stalled for a second on section 12, specifically the bit about how an IP is a uniquely identifying number. What about NATed connections, gateways, proxy servers, open routers, compromised or otherwise hijacked machines? I'm a professional sysadmin but my router at home is using WEP, and I sure as hell don't monitor what's happening with it. I wouldn't expect any more from an average user.
It's somewhat comforting to know that someone actually LISTENS to the files that they download though, rather than the good old fashioned "you were listing a file with the word 'madonna' in it, your ass is ours."
Section 24 is interesting too, about how the expedited discovery is key because ISPs might purge logs before they get a chance to respond. Why is that an issue? I'm no lawyer, but I would assume that destroying documents that are the subject of a discovery motion would be... uh... frowned upon by judges.
It's not an acknowledgement, is no more of an automatic response than the lack of a bounce message. There's no indication or guarantee that anyone actually looked at the email.
I appreciate the reports, I just don't have time to thank and follow up with everyone who does it.
I work for a small national ISP. We always take action on spam reports (we hate spam as much as you do, probably more...), but almost never respond to the people who make the reports. There are only two of us, and we're very busy -- and I doubt the people who are complaining about no response are going to look any more favorably on an automatic response.
Please though, keep reporting. It helps us weed out the spammers we haven't caught by other means.
Sometimes we just don't get enough information to take action though. If you're going to report spam, send in a copy of the ENTIRE email (useless without headers...), and make sure the timestamps are correct. If your clock is wrong, I'll do my best to figure it out, but I can't promise anything.
That's not a problem with Cisco Clean Access, it's a problem with whoever setup the policies it's using, and their decision that if you don't have antivirus X, you get locked out. Complain to your admin staff, but don't hold your breath.
At this university the rules only enforce that you've got McAfee and the EPO agent installed, that your patterns are up-to-date, and that you're at a reasonably recent patch level for Windows. They're only set to restrict systems we can reasonably expect to enforce policies on. Macs and Linux machines obviously are exempt, as was Vista for a while. (it wasn't supported properly by McAfee)
There's only so far you can go. Ralink chipsets can not be supported without either:
Sticking with an old and outdated version of network-manager
A significant rewrite of either Network-manager, wpa_supplicant or rt2500 (or completing rt2x00)
Option 1 isn't feasible. Network-manager switched to using wpa_supplicant for a reason. Maintaining the old version with the feature set of the current one, as well as backporting code changes would be extremely difficult. Option 2 is just as bad, since they can either propose patchsets that will likely get rejected or write their own driver.
Even then, that's a single chipset. What about all the people stuck on broadcom, or d-link, or anything else that currently requires ndiswrapper + a windows driver?
I understand that people are upset because their hardware doesn't work, but I mean, neither does my sound card (some X-FI something-or-other), and you don't hear me complaining about how it's a fundamental flaw in Ubuntu because people like to listen to shit.
Sort of. Network-manager runs everything through wpa_supplicant, which simplified the backend greatly. The rt2500 driver doesn't (or at least didn't) work properly with wpa_supplicant, instead of implementing WE19 they sorta went off and did their own thing. That may have changed, I stopped tracking the development when I stopped using the card.
So you could blame network-manager for not having a backend for every random card, wpa_supplicant for approximately the same thing, or the rt2500 guys for not sticking to the right standard.
It's not really a bug in anything though, it's just unsupported.
I work at the helpdesk at Dal, and while it's not mentioned on the website, there IS a beta version of the 5.x Cisco VPN client available. If you stop by, they will install it for you. It's not perfect, but it's functional... mostly.
"no need to defrag your hard drive" isn't a feature, and it's barely accurate. Once upon a time someone asserted that there was no point in defragging your hard drive on a multi-user system because with the multitude of unrelated requests, even assuming zero fragmentation you'd still have to scan all over the disk.
I should hope not, otherwise their security claim is factually incorrect: both OpenSSH and Apache have had remote-root flaws in the past 10 years that are exploitable on OpenBSD.
It's a silly distinction to make anyway. There have been multiple local kernel exploits in the past 10 years, and there have been plenty of remote exploits that will give you an 'unprivileged' account. Combine the two and you suddenly have a remote exploit that gets you root. Those don't get counted though.
You're right, the MAC address is in the Ethernet header, not the IP header, but that's mostly-irrelevant. The computer obtained an IP address via DHCP. The DHCP server knows the MAC address of the requesting host, and it knows the IP address it gave out, and it keeps a log of that information (so it knows who has what.)
Going by MAC address obviously isn't a 100% identifier, but I'd say it will identify a computer correctly about 95% of the time.
If the 'expert' in question had a copy of the lease file from the DHCP server, say, it's not unreasonable ID the computer from that.
For what it's worth, Opera doesn't seem to have that problem. The page loaded/rendered so fast on my laptop that I thought they'd cheated and just stuck an image in there.
I second that. You can find old SGI gear (Indigo2, or maybe even an Octane) for nothing, or next to nothing. Not only are they relatively cheap, but they look impressive as well... and you can tie them to things people relate to -- for example, I remember reading somewhere that the graphics folks working on Hollow Man and Gladiator were working on Octanes, and using some of the bigger SGI machines for the actual rendering.
Universities are a decent place to pick up old UNIX workstations as they're 'repurposed'.
I wrote a policy server for Postfix that will allow you to trigger responses to a message based on rbl status, which means you can use presence on an RBL to trigger greylisting of an email, which gives you the best of both worlds.
Slashdot Mirror
... now if only this would lead to a little ego deflation and humility among OpenBSD developers.
As long as I'm dreaming, I also want a pony.
Uhh, what?
CSI debuted in 2000. Da Vinci's Inquest debuted in 1998 and ran for 7 seasons. It's not exactly an original idea so I'm not accusing anyone of copying anyone, but let's be realistic here.
There are lots of quality (or at least popular) Canadian shows. Some are original, some aren't. The Kids in the Hall, SCTV, OWL/TV, The Degrassi series, etc... and hey, if you're a Canadian kid who never watched The Hilarious House of Frightenstein, you really missed out.
Toss North of 60 in there, if you're into that sort of thing.
Most of those shows have been exported to other countries, so I guess we're doing something right. We're no better and no worse than the Americans. We both put out a lot of crap and a few gems.
What IRIX (and everything else) ran on is irrelevant, that statement is simply wrong.
Aside from having "legendary responsiveness", from a single CPU box to SMP monstrosities, you could even guarantee disk/cpu/whatever throughput.
A lot of the old unixes had "legendary responsiveness"; you are not a unique and beautiful snowflake.
BeOS fanboys are funny.
Reading through this, I stalled for a second on section 12, specifically the bit about how an IP is a uniquely identifying number. What about NATed connections, gateways, proxy servers, open routers, compromised or otherwise hijacked machines? I'm a professional sysadmin but my router at home is using WEP, and I sure as hell don't monitor what's happening with it. I wouldn't expect any more from an average user.
It's somewhat comforting to know that someone actually LISTENS to the files that they download though, rather than the good old fashioned "you were listing a file with the word 'madonna' in it, your ass is ours."
Section 24 is interesting too, about how the expedited discovery is key because ISPs might purge logs before they get a chance to respond. Why is that an issue? I'm no lawyer, but I would assume that destroying documents that are the subject of a discovery motion would be... uh... frowned upon by judges.
... so how many of these are fixed by recent microcode updates? How many CAN be fixed by microcode updates?
It's not an acknowledgement, is no more of an automatic response than the lack of a bounce message. There's no indication or guarantee that anyone actually looked at the email.
I appreciate the reports, I just don't have time to thank and follow up with everyone who does it.
I work for a small national ISP. We always take action on spam reports (we hate spam as much as you do, probably more...), but almost never respond to the people who make the reports. There are only two of us, and we're very busy -- and I doubt the people who are complaining about no response are going to look any more favorably on an automatic response.
Please though, keep reporting. It helps us weed out the spammers we haven't caught by other means.
Sometimes we just don't get enough information to take action though. If you're going to report spam, send in a copy of the ENTIRE email (useless without headers...), and make sure the timestamps are correct. If your clock is wrong, I'll do my best to figure it out, but I can't promise anything.
That's not a problem with Cisco Clean Access, it's a problem with whoever setup the policies it's using, and their decision that if you don't have antivirus X, you get locked out. Complain to your admin staff, but don't hold your breath.
At this university the rules only enforce that you've got McAfee and the EPO agent installed, that your patterns are up-to-date, and that you're at a reasonably recent patch level for Windows. They're only set to restrict systems we can reasonably expect to enforce policies on. Macs and Linux machines obviously are exempt, as was Vista for a while. (it wasn't supported properly by McAfee)
I'm not sure why you would create it by hand, that's kinda the point of network-manager.
I've had no problems with wireless on 6.04, 6.10 or 7.04, other than vpnc occasionally failing to notice it's been disconnected.
There's only so far you can go. Ralink chipsets can not be supported without either:
Option 1 isn't feasible. Network-manager switched to using wpa_supplicant for a reason. Maintaining the old version with the feature set of the current one, as well as backporting code changes would be extremely difficult. Option 2 is just as bad, since they can either propose patchsets that will likely get rejected or write their own driver.
Even then, that's a single chipset. What about all the people stuck on broadcom, or d-link, or anything else that currently requires ndiswrapper + a windows driver?
I understand that people are upset because their hardware doesn't work, but I mean, neither does my sound card (some X-FI something-or-other), and you don't hear me complaining about how it's a fundamental flaw in Ubuntu because people like to listen to shit.
Sort of. Network-manager runs everything through wpa_supplicant, which simplified the backend greatly. The rt2500 driver doesn't (or at least didn't) work properly with wpa_supplicant, instead of implementing WE19 they sorta went off and did their own thing. That may have changed, I stopped tracking the development when I stopped using the card.
So you could blame network-manager for not having a backend for every random card, wpa_supplicant for approximately the same thing, or the rt2500 guys for not sticking to the right standard.
It's not really a bug in anything though, it's just unsupported.
That's not correct.
I work at the helpdesk at Dal, and while it's not mentioned on the website, there IS a beta version of the 5.x Cisco VPN client available. If you stop by, they will install it for you. It's not perfect, but it's functional... mostly.
"no need to defrag your hard drive" isn't a feature, and it's barely accurate. Once upon a time someone asserted that there was no point in defragging your hard drive on a multi-user system because with the multitude of unrelated requests, even assuming zero fragmentation you'd still have to scan all over the disk.
That doesn't hold true for a single user system.
I should hope not, otherwise their security claim is factually incorrect: both OpenSSH and Apache have had remote-root flaws in the past 10 years that are exploitable on OpenBSD.
It's a silly distinction to make anyway. There have been multiple local kernel exploits in the past 10 years, and there have been plenty of remote exploits that will give you an 'unprivileged' account. Combine the two and you suddenly have a remote exploit that gets you root. Those don't get counted though.
OpenBSD - Security through self-delusion.
You're right, the MAC address is in the Ethernet header, not the IP header, but that's mostly-irrelevant. The computer obtained an IP address via DHCP. The DHCP server knows the MAC address of the requesting host, and it knows the IP address it gave out, and it keeps a log of that information (so it knows who has what.)
Going by MAC address obviously isn't a 100% identifier, but I'd say it will identify a computer correctly about 95% of the time.
If the 'expert' in question had a copy of the lease file from the DHCP server, say, it's not unreasonable ID the computer from that.
Run KDE!
For what it's worth, Opera doesn't seem to have that problem. The page loaded/rendered so fast on my laptop that I thought they'd cheated and just stuck an image in there.
There are Vista-compatible Cisco VPN client builds, starting with version 4.8.xxxx.
I second that. You can find old SGI gear (Indigo2, or maybe even an Octane) for nothing, or next to nothing. Not only are they relatively cheap, but they look impressive as well... and you can tie them to things people relate to -- for example, I remember reading somewhere that the graphics folks working on Hollow Man and Gladiator were working on Octanes, and using some of the bigger SGI machines for the actual rendering.
Universities are a decent place to pick up old UNIX workstations as they're 'repurposed'.
They blocked the .xxx domain, which is unfortunate, but it was part of a stupid concept to begin with.
Just imagine what China, Iran, etc. would do with control?
Sounds like it's time for Queer Eye for the Straight OS.
I'm going to f---ing bury that thing, I have done it before, and I will do it again.
I'm going to f---ing kill that chair.
I wrote a policy server for Postfix that will allow you to trigger responses to a message based on rbl status, which means you can use presence on an RBL to trigger greylisting of an email, which gives you the best of both worlds.
maRBL
That's not legal, unless you're buying a chunk of hardware along with it.
Even then, I haven't seen 6.5 sets around, only 5.x and 6.2