The difference is that an un-initialized pointer will throw an error on compile with gcc.
PHP is perfectly happy with un-initialized variables.
PHP in it's harshest mode will only complain about un-initialized variables if its a string and you try to run $value.= or if its an array and you try to use one of the array functions on it, plus a few others (e.g. unitialized mysql connections).
Don't get me wrong, I've used PHP a lot and recommended it with success in my last work-place. register_globals is however a throw-back and something I'm sure the PHP team would rather forget as soon as possible. All of my apps have always worked fine with safe_mode on and register_globals off.
I'd say part of professional is being forward-looking, so you should have been coding scripts that worked without register globals since the PHP manual starting moving that way, which was at least 2 years ago now.
To be honest that will only affect people who haven't bothered reading any docs or upgrading any software in the last three years and still run PHP with register_globals turned on.
Whether it be Perl,.NET, Java or whatever your choice of web-*. If you don't upgrade it for years or you run with stupid insecure settings that only 3-year-old scripts need then you can expect shit.
(you arent the same guy that coded phpnuke by any chance?)
Hrm something I read recently, possibly the O'Reilly Ethernet book said that 30% limit was for the standard before the full CSMA/CD functionality was added,i.e. the old experimental slotted aloha nets.
I remember you could edit the graphics from some archimedes apps by opening those folders, we had a load of them lying around in my secondary school. Hours of fun to be had pornolizing games and various other bits of software they used.
Luckily it was that long ago, the teachers were more impressed we'd managed to do it than upset at rude messages. Afaik they hardly got used except by us during breaks. I didn't ever have any lessons on them...although thinking back perhaps I can see why now..
How exactly do you think this mystical Linux hardware support comes about.
People buy the laptop and code it themselves then submit it into the kernel. Theres not some huge list of IBM drones coding Linux drivers for every piece of equipment in Thinkpads. Until the machines are released they won't be Linux compatible.
Erm, as someone who has submitted a bug to Microsoft and Cert that is getting very close to the 45 day rule without any sign of an update of fix or even response beyond 1st line customer support I can tell you that #3,
The problem with KAME is that IPSec packets between two hosts can bypass the packet filters.
That is, with KAME on Linux and FreeBSD, packets are not decrypted until after iptables/ipfw has looked at them. That means you cannot packet filter on anything other than IP & MAC Address as you can't read anything else, its all encrypted:)
Apparently FreeS/WAN had a separate device to read from that gave unencrypted packets for filtering.
This only applies to transport IPSec between two complete hosts. You can use tunnel mode onto a tun device and filter from that, and you can also just encrypt traffic based on port.
Either way, I'm kind of relieved that FreeS/WAN has not gone completely and that the above situation still has a fix. A security protocol seems kinda useless when it allows firewall bypassing, especially when it could happen automatically if you have IKE setup and open to the world.
Yea, what exactly is "should the Amiga curse continue" supposed to mean.
If the poster had been around at the time, they would clearly remember the amiga A500, at a stonking 4.7mhz, running on a TV that would shit all over any PC at that time. Start looking at the A1500s and A3000s, PCs took a while to catch up.
Of course the PC's at that time were 286's and earlier, but I still remember laughing at my cousin for spending 5x as much on a PC that went 5x as slow and had a crappy desktop OS that looked about 5 years older.
Amiga curse indeed, well I guess if you consider anything high performance and not a PC a curses, you're right.
Unless the encryption adds 80ms of latency and creates monster jitter.
VoIP isn't the easiest traffic to try and encrypt, for multiple VoIP streams you may need hardware encryption cards to work fast enough. People have enough problems getting regular VoIP to integrate nicely with their networks.
For the individual user it'd probably be a good idea, for an office with 300 phones? It'd add a lot of cost, and your existing POTS aren't encrypted. I don't see it happening much.
Love patch will go into any 2.6 kernel, its not distro-specific. As long as you can compile the kernel from source it'll work.
Its not all experimental patches either, it includes -mm which is often more stable than vanilla release kernels. Reiser4 and packet-writing are about the only experimental things in, the rest is just extra driver support. Oh, and bootsplash.
For full list read the notes file in the above link, tells you exactly what patches were added.
Tells you how to install your self-signed certificate into your clients browsers.
For anyone with too many clients to do this practically... well if you have that many clients you should be making enough money to buy a certificate from a trusted authority.
In the UK you're allowed to install the same version of windows on multiple computers regardless of OEM status or otherwise.
I think the stipulation is that you don't use them all at once, you brought a copy of windows, therefore you are allowed to use it on any one PC at any one time.
Just because the distributer calls it "OEM" or puts a bit of paper in saying "license, ONE PC ONLY" doesn't make it law and doesn't make it true.
Incidently, the advice came from which magazine, anyone know which actual laws this would come under... fair use?
Slashdot Mirror
Blah, they said XP was a media OS and it can't even play DVDs in the default install.
Yes, but how would we keep selling crappy products to everyone if that was the case?
Oh, wait...
HSRP even (hot standby router protocol)
IPv4 routing in Cisco is done by software not hardware.
This already is a Cisco killer for one simple reason, VSRP is crap.
Aye me for one.
Quite disgusting in my opinion to compare someone infringing on copyright with a pirate who rapes, pillages and murders people on the high seas.
Most actual acts of piracy at sea are completely savage affairs with the victims lucky to escape alive.
Obviously this is about the same level as some kid copying a CD instead of paying $4 for it.
The difference is that an un-initialized pointer will throw an error on compile with gcc.
.= or if its an array and you try to use one of the array functions on it, plus a few others (e.g. unitialized mysql connections).
PHP is perfectly happy with un-initialized variables.
PHP in it's harshest mode will only complain about un-initialized variables if its a string and you try to run $value
Don't get me wrong, I've used PHP a lot and recommended it with success in my last work-place. register_globals is however a throw-back and something I'm sure the PHP team would rather forget as soon as possible. All of my apps have always worked fine with safe_mode on and register_globals off.
I'd say part of professional is being forward-looking, so you should have been coding scripts that worked without register globals since the PHP manual starting moving that way, which was at least 2 years ago now.
To be honest that will only affect people who haven't bothered reading any docs or upgrading any software in the last three years and still run PHP with register_globals turned on.
.NET, Java or whatever your choice of web-*. If you don't upgrade it for years or you run with stupid insecure settings that only 3-year-old scripts need then you can expect shit.
Whether it be Perl,
(you arent the same guy that coded phpnuke by any chance?)
If it was only 70 meters high back then would it have been called mount arafat?
With d-midi :-)
Hrm something I read recently, possibly the O'Reilly Ethernet book said that 30% limit was for the standard before the full CSMA/CD functionality was added ,i.e. the old experimental slotted aloha nets.
With the CSMA/CD the rates went up to the 90s
you are very lucky... There's no way for me to see the video under Linux.
Try mplayerplug-in or konqueror.
The whole thing works fine in moz here. Vids and all.
Your average internet cafe user won't do any of the above.
They'll just walk 200 yards down the road to the next cafe where they can use their email.
Ah takes me back.
I remember you could edit the graphics from some archimedes apps by opening those folders, we had a load of them lying around in my secondary school. Hours of fun to be had pornolizing games and various other bits of software they used.
Luckily it was that long ago, the teachers were more impressed we'd managed to do it than upset at rude messages. Afaik they hardly got used except by us during breaks. I didn't ever have any lessons on them...although thinking back perhaps I can see why now..
How exactly do you think this mystical Linux hardware support comes about.
People buy the laptop and code it themselves then submit it into the kernel. Theres not some huge list of IBM drones coding Linux drivers for every piece of equipment in Thinkpads. Until the machines are released they won't be Linux compatible.
Erm, as someone who has submitted a bug to Microsoft and Cert that is getting very close to the 45 day rule without any sign of an update of fix or even response beyond 1st line customer support I can tell you that #3,
"3. Hope somebody out there at random fixes it."
applies just as much to closed source as open.
yep, well pretty much. More so than most manufacturors.
..submitted by a very happy thinkpad/linux user.
Transforming the electricity grid into the worlds largest human microwave.
The problem with KAME is that IPSec packets between two hosts can bypass the packet filters.
:)
That is, with KAME on Linux and FreeBSD, packets are not decrypted until after iptables/ipfw has looked at them. That means you cannot packet filter on anything other than IP & MAC Address as you can't read anything else, its all encrypted
Apparently FreeS/WAN had a separate device to read from that gave unencrypted packets for filtering.
This only applies to transport IPSec between two complete hosts. You can use tunnel mode onto a tun device and filter from that, and you can also just encrypt traffic based on port.
Either way, I'm kind of relieved that FreeS/WAN has not gone completely and that the above situation still has a fix. A security protocol seems kinda useless when it allows firewall bypassing, especially when it could happen automatically if you have IKE setup and open to the world.
Yea, what exactly is "should the Amiga curse continue" supposed to mean.
If the poster had been around at the time, they would clearly remember the amiga A500, at a stonking 4.7mhz, running on a TV that would shit all over any PC at that time. Start looking at the A1500s and A3000s, PCs took a while to catch up.
Of course the PC's at that time were 286's and earlier, but I still remember laughing at my cousin for spending 5x as much on a PC that went 5x as slow and had a crappy desktop OS that looked about 5 years older.
Amiga curse indeed, well I guess if you consider anything high performance and not a PC a curses, you're right.
Thou shalt encrypt
Unless the encryption adds 80ms of latency and creates monster jitter.
VoIP isn't the easiest traffic to try and encrypt, for multiple VoIP streams you may need hardware encryption cards to work fast enough. People have enough problems getting regular VoIP to integrate nicely with their networks.
For the individual user it'd probably be a good idea, for an office with 300 phones? It'd add a lot of cost, and your existing POTS aren't encrypted. I don't see it happening much.
Also, wouldn't it'd be VoIP over IPSec? </pedant>
'ave a look at -H while you're at it.
Unless the ad is for a page on the same site wget won't follow the link, unless you -H.
distcc is pretty handy in that kinda situation :)
Slow PC? fine, get a faster one on the LAN to compile it for you, infact get them all to help. No spare nix machines? Use distccKnppix.
Love patch will go into any 2.6 kernel, its not distro-specific. As long as you can compile the kernel from source it'll work.
Its not all experimental patches either, it includes -mm which is often more stable than vanilla release kernels. Reiser4 and packet-writing are about the only experimental things in, the rest is just extra driver support. Oh, and bootsplash.
For full list read the notes file in the above link, tells you exactly what patches were added.
Fortunately, the open-source SSL systems also provide a solution to this problem.
Look here
Tells you how to install your self-signed certificate into your clients browsers.
For anyone with too many clients to do this practically... well if you have that many clients you should be making enough money to buy a certificate from a trusted authority.
In the UK you're allowed to install the same version of windows on multiple computers regardless of OEM status or otherwise.
I think the stipulation is that you don't use them all at once, you brought a copy of windows, therefore you are allowed to use it on any one PC at any one time.
Just because the distributer calls it "OEM" or puts a bit of paper in saying "license, ONE PC ONLY" doesn't make it law and doesn't make it true.
Incidently, the advice came from which magazine, anyone know which actual laws this would come under... fair use?