Thank you and good night Planet PHP

I’ve decided to remove my feed from Planet PHP because of some small minded commentors (Jani and David Rodger). I would like to thank everyone who has read my blog on the planet php feed and I hope I have provided some useful information. If you didn’t think I was relevant to PHP Planet you now have your wish.

29 Responses to “Thank you and good night Planet PHP”

  1. Mark Armendariz writes:

    No reason to get so worked up about a couple comments. I’m sure the majority of your visitors appreciate your writing (I’m one of them).

  2. Thorin writes:

    Keep up the good work Gareth! Don’t let the mindless minority get you down.

    And Ronald if you’re reading, I’m sorry you had to do away with your comment functionality, I still read all the new stuff on your site.

  3. Gareth Heyes writes:

    Thank you for your kind words.

    I’ve made up my mind though, I’m removing the site from the planet php feed. I don’t mind answering valid questions or good points but mindless rubbish gets me down.

    I’m doing blogging to interact with some clever people, which I’ve really enjoyed and it is a shame that some people can’t open their eyes a bit and realise that the stuff I posted can be applied to their applications.

    So from now on I’ll only post on the web security feed which is a shame because other people will probably miss out but I do have a short fuse.

  4. Regin writes:

    What a shame… πŸ™ – luckily it only takes 2 seconds to add your feed!

  5. Jani writes:

    I didn’t mean all your posts have been “off-topic”. Only the exploit/js stuff. Don’t take it so seriously, we live in a free world (or well..most of us πŸ™‚ and it’s supposed to be free to state your opinions, isn’t it? πŸ™‚

    Isn’t it possible to have different channels or something in these blog things? πŸ˜€

  6. Benjamin Klaile writes:

    >> IÒ€ℒm sure the majority of your visitors
    >> appreciate your writing (IÒ€ℒm one of them).

    I second this!
    Your blog is within my “daily feeds” anyway πŸ˜‰

  7. Gareth Heyes writes:

    Jani my article was on the context of security. This is important to secure your PHP applications. If you had read the whole article you would have understood that it provides the reader with knowledge on how to exploit and think about applications from a hacker point of view. Exploiting your PHP applications is the only way to provide good security for your users. If you don’t think that’s relevant then….enough said.

  8. Gareth Heyes writes:

    Thank you Benjamin!

    Nice to hear from my readers and not just useless comments which get me down.

  9. Richard Harrison writes:

    Why don’t you tag your PHP posts with “PHP” and submit a feed for that tag to Planet PHP?

  10. ensi writes:

    Gareth thanks for your posts so far. Keep them comming.

    Added your site to my daily list. It was convenient to read it through planet-php. But it doesn’t really matter from what feed it comes. It’s the source that counts.

  11. Gareth Heyes writes:

    Ensi thanks for the support

    My feed can be retrieved through Planet Web security if required.

    I don’t want to stay on a site which people think my stuff isn’t relevant. They can filter the content in their readers but they still choose to post useless comments on my blog when I spend the time to write this stuff in order to provide I hope useful information.

  12. Gareth Heyes writes:


    My post was tagged with PHP because I thought it was relevant for developers because they need to know how to hack their own stuff.

    I feel strongly about these views and if someone questions it or implies that my stuff doesn’t work without any foundation then I will take action. People will lose out but the real fools will be highlighted.

  13. Gareth Heyes writes:

    Thanks everyone who posted support, you made me feel much better. I’ve not had much sleep and I spent a bit of time preparing that article and when I received just those 2 comments, 1 telling me security isn’t relevant to PHP and the other implying that my exploit didn’t work and was just google ad words spam, I was understandably annoyed.

    I’m staying on the Planet PHP feed but I will no longer post security related stuff to it. So I’m sorry if any new novice developers miss out if they find the Planet PHP feed but you can always grab the security feed from here.

  14. Greg Beaver writes:


    Your posts are informative and useful, I particularly enjoyed the Safari exploit, even though it was not relevant directly to PHP, but more to being security-conscious as a developer in general. A bit of unsolicited advice: you should sleep a night when feeling rebellious and wanting to post things like “seeya planet PHP” πŸ™‚

    I know I’ve sent out a few doozies when I forget this rule and click “Send” or “Post” …

  15. Gareth Heyes writes:

    Thanks Greg

    I’ve had some sleep now and I feel a bit better. I just got a bit silly I think because of 1 or 2 annoying comments. Damn those 24 hour coding sessions, they’re not good for me πŸ™‚

  16. David Rodger writes:

    Did I say the hack wasn’t serious? Did I say it was non-existent? Did I say your post wasn’t relevant? I said none of these things.

    And Jani, it’s his blog, not a democracy. He can do as he wants, including unjustifiably slagging me off! I hope he has the good grace to publish this qualification but I can’t and won’t force him to.

    My copy of Safari (version number included in my comment) does not display the behaviour implied in your description. What that behaviour should be exactly I don’t know, but i assume from the JS I should have had an alert.

    Now if you’d said “Safari preferences must be set as follows…” or “only on this version and lower/higher/sideways”, it might have accounted for it. I suppose I should have anticipated that my “Hmm” might be misinterpreted by the [ahem] “mindless minority”.

  17. Gareth Heyes writes:

    I did over react because I was tired but it was your mistake. I assumed that people would have the intelligence to read the address bar before leaving a comment about it not working on a non-beta product.

    You implied those things.

  18. David Rodger writes:

    I apologise unreservedly to you Gareth. You did talk about the beta. What I was worried about, I suppose, was that such exploits were in earlier versions of Safari and maybe no one had noticed. Your reference to “Apple software update appeared with news of a new beta of Safari” gave me the impression that what preceded was not entirely about the beta (or an earlier beta).

    My real mistake is assuming that Apple was unlikely to introduce new bugs into a newer version (it’s supposed to be an improvement isn’t it?). Don’t know why; an expectation, after years of using Apple products, that it will just work. But it’s happened with PHP releases plenty of times. No reason why anyone else wouldn’t experience it.

    I, and I’m sure that others here, appreciate your work and find it intriguing. It’s very convenient having you on Planet PHP and it would be a shame if you were not. (Besides, your post is actually web-related unlike some other entries about what happened at the pub last night — you know what I mean?)

    I don’t actually want to have to think too hard about this stuff. I just want it to work. It’s hard enough worrying about my PHP code and user input without considering browser hacks. But then the CSS folks probably similar things about MSIE.

  19. Gareth Heyes writes:

    Thank you David no hard feelings.

    We all make mistakes and I must have misinterpreted your comment for being nasty when it probably wasn’t. Sorry about that.

    Yeah that’s why I did take offense to Jani because of all the other unrelated stuff on there, yet he chose to leave a comment on my blog, which I thought was a waste of mine and everyone else’s time.

  20. Gareth Heyes writes:

    I haven’t tagged my latest post about vulnerability with PHP, so it won’t appear on PHP Planet. Even though that knowledge is needed by PHP developers because the very example is used for a PHPIDS system. They are trying to filter out javascript injection.

    But hey it’s not PHP related eh? See how silly some people are.

  21. Tom Macklin writes:

    The reason I hate coding w/ web-types most of the time is this attitude “of I just want it to work.” If you want it to work, then write correct code. The trouble is, you don’t “just want it to work”– you want to get a lot of result w/o much effort or thought.

    I’d check out a different career field.

  22. Tom Macklin writes:

    That last comment was supposed to be a reply just to David Roger comment (#18), but it showed up as a comment on the whole article… my bad.

  23. David Rodger writes:

    Maybe it’s just Safari, Tom, but I don’t see a mechanism for indicating that your reply is to a specific post (unlike, say, Serendipity on Stefan Esser’s site).

    >If you want it to work, then write correct code.

    Tom, do you write code for the web, where this vulnerability and its consequences would become evident? If you’re not a “web type”, I’m impressed that would have spotted it in a nano-second (as opposed to the long, hard slog Gareth put in to find it). Incidentally, what is it of yours that is bad?

    Gareth, could you tell us whether you think what the Safari beta does is what it (or any browser, for that matter) ought to do?

  24. Gareth Heyes writes:

    Well every browser should deny access to write access things like the document object. Firefox’s behavior in this matter is the best.

    But this specific vulnerability is the way Safari handles local files, it seems that if a file is run locally or fooled into thinking it is local then the cross domain policy seems to go out the window. Hence why I could access data from other domains.

    I would recommend everyone uses an alternate browser until Apple release a fix for the beta as this vulnerability is extremely dangerous, it would be possible to hide the iframe and perform any action on any web site and retrieve data as that person.

    Normally I would have reported this to the manufacturer before releasing it to the public but Apple’s attitude deserved otherwise.

  25. Richard Fletcher writes:

    Hi Gareth,

    I’ve been educated and entertained by your posts, and will be subscribing to your own feed.

    Thanks for sharing your work.


  26. Gareth Heyes writes:

    Richard thanks a lot, it helps a great deal if I know people are learning or enjoy my posts.

  27. Tom Macklin writes:

    Gareth- I never have gotten around to saying “thanks” for such an *informative* blog. Most blogs seem to focus on sound bytes– I think this one focuses on, well, focused substance. Not for everyone, but great for those it is for.

  28. Gareth Heyes writes:

    Thanks Tom much appreciated, I always blog about the stuff I’m passionate about and that’s why I find it easy to do, you’re right it’s not for everyone but I’m not trying to appeal to everyone, I just want to share knowledge and talk to clever people.

    In the last few months I’ve talked to some outstanding programmers and starting blogging was probably one of the best decisions I’ve made.

  29. Tom Macklin writes:


    Of course I wouldn’t have spotted the problems with that vulnerability without careful investigation, if ever! In security, people often have their own technique for finding particular types of problems. Also, just because I strive to write correct software doesn’t mean I do it. However, we do have a responsibility to ensure our software does what we claim it does, and most software products claim to be secure.

    BTW- I don’t intend to get involved in a flame war that clogs up this blog… good luck doing your thing.