According to the just-released 2021 version of OWASP Top 10 (a curated list of the most critical web application security risks out there), “Cryptographic Failures” are the 2nd most important of the many security concerns we should have as web developers. These concerns include a lot of misuses of cryptographic systems, like choosing weak algorithms, poor randomness sources, or usage of deprecated methods. That is why this is also the second article covering the main topics for cryptography: on our last issue, we covered the main theory, which sometimes is the cause of those errors mentioned above, and right now we will see how to use libsodium, a modern library with the most recommended algorithms already built-in and no weak settings available per default. It is a cross-platform tool, available to use on Windows, Mac, and Linux, and has been included in PHP’s core since 7.2. It also has bindings for Java, NodeJS, Python, Go, and several other languages. So we are safe to say it runs pretty much everywhere. The official website is libsodium.org, and you can find the full documentation there instead of the PHP.net manual as it is sometimes not complete. There is also a Quick Reference and a “Using Libsodium in PHP Projects” article.
Our crew interviews recent contributor Vinícius Campitelli about his articles and involvement with PHP.
- Applying SOLID principles and object calisthenics in practice.
- Getting into programming by scripting IRC chat bots.
- Working with PHP professionally.
- Transitioning into teaching programming.
- PHP User Groups in Brazil and speaking at conferences and meetups.
- Looking forward to the new features of PHP 8.
In Episode 23
Eric, John, and Oscar go through the August 2019 issue.
- Getting started with Symfony 4
- Managing legacy codebases
- PHP++ and the future of PHP
- Karl Hughes talks about running the Chicago PHP User Group.
- Writing better object-oriented code
The post Symfony 4, Legacy Code, the Future of PHP, and Karl Hughes appeared first on php[architect].
Phillip and Kalen recap the first day and a half of Imagine 2018, and Kalen remarks how the entire Magento community is being asked to “level up” with a call to higher standards and higher goals from Magento CEO, Mark Lavelle.
The guys set the record straight on a few things they got wrong, grill newly-hired Magento Evangelist Ben Marks about his role, ask hard questions (where are the forums?) and Ben name-drops with all of the PHP folks he’s getting to know in his newfound role.
- 9:48 Software release schedules around holidays and the idea of release candidates.
- 28:45 Kalen reminisces about his early days of working with Magento
- 29:32 Ben talks about how he got his start in teaching the Magento U courses and the filming of the first video that is still available online.
- 36:11 How Magento 2 is doing a better job of communicating with the community
- 38:50 Search in Magento
- 40:55 Ben talks about what it means being a Developer Evangelist for Magento and how he measures the success of the position
- 1:01:36 How can the community help Ben
- 1:03:07 Ben drops some hints about the new forum solution Magento is looking at for replacing the now read-only forums and a possibly timeline for its release.
Corrections for Ep12
- Colin Mollenhour never submitted code surrounding the improvements in indexing for EE 1.13, but he had exchanged emails with the core team on ideas. Piotr Kaminski clarified that there were already conversations happening internally along these same lines of thinking.
- Piotr also clarified that none of Kalen’s gloriously beautiful code was used in the responsive email designs for EE 1.14. It all came from Classy Llama. Props to the Llamas.
Links / Mentions
- Somewhere in the middle – Sleepless in Seattle
- Vinai Kopp
- Alen Kent‘s Blog
- Phil Sturgeon
- Loosely Coupled
- Davey Shafik
- Jordi Boggiano
- PHP NW
- Meet Magento Poland
- StackOverflow (Magento)
- Chris Hartjes aka @grmpyprogrammer
- Sunshine PHP
- Adam Culp
- Miami South Florida PHP Meetup
- Adrian Cardenas
- Expression Engine
- Marius Strajeru
- Ben Marks – @benmarks