I worked for a computer gaming software development company called Maximum Charisma Studios in 2001-2002. I was the systems and network engineer, doing all of the production and corporate infrastructure -- desktops, servers, Microsoft, GNU/Linux, WAN and LAN networking.
Is it just me or is this guy subtly looking for a job?
This is about the level of competency I've come to expect from Large Government Entities.
No, I think the DHS did exactly what it wanted to, and did it quite well. The US intelligence agencies had two months to exploit the bug before it was even announced. ISS will probably be rewarded with a nice fat government contract.
Wouldn't it be best to issue a statement like "sendmail has an exploitable vulnerability, we recommend that you switch to your standby alternate mail system until we release a fix"?
The problem is, that statement has been generally true for many years now. The people that are still using sendmail either truly need its flexibility or just don't know any better.
One of the reasons the current model--storing credit card numbers and charging them every month--is so popular is that it makes it more likely for people to remain customers. When a customer has to authorize a payment every month, she's more likely to cancel because she has to think about the expense every time. That's why we'll continue to see merchants storing credit card numbers for a long time.
Are you kidding? The Iraqis know the inspectors are looking for nuclear weapons, and they know where they are. It's not as if the inspectors are sneaking around Iraq, communicating with each other through their Dick Tracy brand secret decoder rings. The only way they can catch the Iraqis off guard is to show up where they're not expecting an inspection, not to show up with fancy radiation-detecting wrist watches.
On Win32, ZoneAlarm has a number of features I haven't seen in any other Windows firewall package. The chief among these is the ability to restrict access by programs. Most firewalls would let your CD player send out packets on tcp/80 without thinking about it. ZoneAlarm will let you decide whether this is normal behavior (e.g. WinAmp minibrowser) or something undesirable (like sending out your credit card numbers to Bandlink).
I know about firewalls. I know about network security. But on my personal Win32 boot, where I don't trust all the code I run, I use ZoneAlarm as my firewall of choice. The OpenBSD gateway will catch the incoming packets on tcp/31337, but it won't do a damn bit of good against spyware.
What a great idea! It's already done
on
Mr Anti-Google
·
· Score: 2
On the other hand, the screen resolution is 160x160 pixels.
As of the last time I coded for PalmOS anyway, the documentation made it clear that 160x160 was the size of the a PalmOS system's screen, and I could assume that and even hard-code it. (Of course, a few months later I saw PalmOS systems from Sony at 320x320, but...)
Alternate proposal: enjoy your vacation and don't worry about flying a drone around so you can get free net access. If you just want to use your laptop all night, stay at home or work and use the fast landline connection there.
So every time I fly on a commercial airliner, I'm reminded to turn off my cell phone for the duration of the flight. Yet these people are using wireless technology in the air. And there are lots of stories of people using cell phones on flights (e.g. on Sep 11). What exactly is the danger here in using wireless in the air?
When I first drove in to Virginia I was somewhat frightened to read a sign informing me that "SPEED LIMIT ENFORCED BY AIRCRAFT". I had visions of a helicopter swooping down from a cloud at me, announcing to me on a loudspeaker that I had been speeding, then opening fire with machine guns to make sure I never speed again. Anyway, later I figured out it was a speed trap as you described, but wouldn't the helicopter idea be more effective?
See, I don't get this whole "Army of One" business. If I were to join the army, I wouldn't want to be fighting alone. I'm not delusional: I know I can't defeat enemies Rambo-style. No, I'd want to be part of a "Big-Ass Army of Many Ass-Kicking Soldiers, Tanks, and Other Military Equipent". Apparently I have to sign up with some other country to get this.
And you're going to get yourself a ticket on a cargo plane how? Oh, I suppose you could commandeer it on the ground, but by the time you get in the air, five fighters have already scrambled.
The problem is not that students are sharing files. The problem is that students are sharing files outside the campus network. There's almost always extra bandwidth within the dorms. If a school were to encourage some method of sharing that first tried to download from within the campus, the vast majority of desired files would be found within the dorms, and the external bandwidth usage would diminish. Of course, such a pragmatic approach would make the stop-it-all crowd very unhappy, so it is unlikely to ever be implemented.
Sure. Just send your foo.tex file. Oh, and if you don't want the receipient to have to run TeX fifty times, be sure to send foo.aux, foo.toc, foo.idx, foo.ilg, foo.ind, foo.log, and maybe foo.log for good measure. Actually, maybe just send a tarball...
What I'd be most afraid of is that these people would simply have no interest in using them, either due to ignorance or because a particular library terminal is part of a gang's turf.
Disinterest due to ignorance is likely. However, I don't know about your part of the country, but here in Houston our problems with street gangs don't extend to use of computer terminals at public libraries.
Slashdot Mirror
Just like Googlex.
One of the reasons the current model--storing credit card numbers and charging them every month--is so popular is that it makes it more likely for people to remain customers. When a customer has to authorize a payment every month, she's more likely to cancel because she has to think about the expense every time. That's why we'll continue to see merchants storing credit card numbers for a long time.
Are you kidding? The Iraqis know the inspectors are looking for nuclear weapons, and they know where they are. It's not as if the inspectors are sneaking around Iraq, communicating with each other through their Dick Tracy brand secret decoder rings. The only way they can catch the Iraqis off guard is to show up where they're not expecting an inspection, not to show up with fancy radiation-detecting wrist watches.
Well, for one thing it could call for help even if you're too panicked to do so yourself.
Of course, you've just had to pay an extra $.20 - $1 to actually listen to the CD you already purchased, depending on how much you pay for your CD-Rs.
On Win32, ZoneAlarm has a number of features I haven't seen in any other Windows firewall package. The chief among these is the ability to restrict access by programs. Most firewalls would let your CD player send out packets on tcp/80 without thinking about it. ZoneAlarm will let you decide whether this is normal behavior (e.g. WinAmp minibrowser) or something undesirable (like sending out your credit card numbers to Bandlink).
I know about firewalls. I know about network security. But on my personal Win32 boot, where I don't trust all the code I run, I use ZoneAlarm as my firewall of choice. The OpenBSD gateway will catch the incoming packets on tcp/31337, but it won't do a damn bit of good against spyware.
Alternate proposal: enjoy your vacation and don't worry about flying a drone around so you can get free net access. If you just want to use your laptop all night, stay at home or work and use the fast landline connection there.
So every time I fly on a commercial airliner, I'm reminded to turn off my cell phone for the duration of the flight. Yet these people are using wireless technology in the air. And there are lots of stories of people using cell phones on flights (e.g. on Sep 11). What exactly is the danger here in using wireless in the air?
When I first drove in to Virginia I was somewhat frightened to read a sign informing me that "SPEED LIMIT ENFORCED BY AIRCRAFT". I had visions of a helicopter swooping down from a cloud at me, announcing to me on a loudspeaker that I had been speeding, then opening fire with machine guns to make sure I never speed again. Anyway, later I figured out it was a speed trap as you described, but wouldn't the helicopter idea be more effective?
On flat terrain it kept only 3 legs on the ground at a time. Walking downhill (in the other video) it kep more feet on the ground at a time.
Don't worry, the September 11 hijackers are going to hell: they pirated Microsoft Flight Simulator, remember?
See, I don't get this whole "Army of One" business. If I were to join the army, I wouldn't want to be fighting alone. I'm not delusional: I know I can't defeat enemies Rambo-style. No, I'd want to be part of a "Big-Ass Army of Many Ass-Kicking Soldiers, Tanks, and Other Military Equipent". Apparently I have to sign up with some other country to get this.
And you think this won't be copied and posted in comments by ACs because?
This will be a problem with any "plum" that consists of content only visible to subscribers.
And you're going to get yourself a ticket on a cargo plane how? Oh, I suppose you could commandeer it on the ground, but by the time you get in the air, five fighters have already scrambled.
No. GCC makes it much easier to port your code to other platforms. This is exactly what Intel doesn't like about it.
The problem is not that students are sharing files. The problem is that students are sharing files outside the campus network. There's almost always extra bandwidth within the dorms. If a school were to encourage some method of sharing that first tried to download from within the campus, the vast majority of desired files would be found within the dorms, and the external bandwidth usage would diminish. Of course, such a pragmatic approach would make the stop-it-all crowd very unhappy, so it is unlikely to ever be implemented.
Sure. Just send your foo.tex file. Oh, and if you don't want the receipient to have to run TeX fifty times, be sure to send foo.aux, foo.toc, foo.idx, foo.ilg, foo.ind, foo.log, and maybe foo.log for good measure. Actually, maybe just send a tarball...
Ah, nothing like 1600x1200x32x85 on a 15" LCD... now that's a New Year's resolution I don't mind keeping.