1. point of view of a webhoster speaking @webilea

3. Developer and #devops

4. Study computer science at Uni Basel

5. Linux user

6. mod_rewrite guru

7. NBA Jam addicted

9. Why so famous ?

10. PHP on a server

11. Security

12. Worries and concerns

13. Summary / Q&A

16. PHP5 2004 -> OOP, PDO, JSON, performance

18. Stream, Session, DB access, image processing, ...

19. „Arrays in PHP are the sets and maps of java“

20. Why so famous? Approx. 30% in scripting languages http://phpadvent.org/2010/usage-statistics-by-ilia-alshanetsky

22. Lamp stack (Linux – Apache – Mysql – PHP)

23. Steep learning curve (gains diversity)

24. Community

25. Libraries and ready to use apps

26. PHP on a server Mod_php FastCGI CGI Web Apache Module gateway binary Process Apache process php-cgi php-cgi Configuration Apache conf files wrapper php.ini User Apache user Shell user or suexec user suphp

28. Multiple PHP versions

29. Self compiled PHP version (make install)

30. Control over php.ini

31. PEAR and PECL installed

34. Cross-site scripting (XSS)

35. <?php $d = 2.2250738585072011e-308; ?>

36. Plugin code quality (Wordpress, Joomla, ...)

37. FTP with plain authentication

39. Disabling Functionality

40. Preventing information disclosure (display_errors)

41. Restricting Includes

42. Restrict File Uploads

43. Mod_security (false positive)

44. Check file permission

46. App monster like typo3 or magento

51. App monster like typo3 or magento

52. mod_rewrite voodoo

53. PHP5.3 -> lot of deprecated functions

54. Developers want * bling bling*

55. My website is hacked – what now?

57. No clearing of cached files

58. Updates - „never touch a running system“

59. Store files in database

60. Corrupted databases

62. PHP is highly flexible & configurable

63. Actracts wide range of users

64. Lots of abuse cases are PHP related, but that’s not the fault of PHP

65. Scaling is „limited“ (left out due time limit)

66. Q&A