He/Him. Microsoft MVP and GitKraken Ambassador. š Poshsecurity.com. š³āš Gay. š± Cat owner.
I'm excited to announce that I'll be presenting a new talk, āThe Boring Security Talkā at both DDD Melbourne and NDC Sydney in September.
I'm happy to announce that Planet PowerShell is now enforcing HTTPS for all aggregated sites. I gave some extra time for authors to make the change. In the end only 3 authors opted out of moving to HTTPS, so I'm happy with the result.
DNS is one of those critical systems that never gets the attention it deserves. Every organisation relies on DNS. It is critical for the smooth operation of your business and yet, it's rarely considered as important as web and email. Your customers canāt find your corporate website or email servers without DNS, without DNS your business isnāt online. People shouldnāt be required to remember an IP address (something that's next to impossible with IPv6) just to access the corporate intranet!
Previously I announced that Planet PowerShell will be enforcing HTTPS for all aggregated sites from August 1st (2018-08-01). That date is now a little over 4 weeks away.
Planet PowerShell has grown over the last 18 months since its launch. The community has grown to over 60 talented individuals, with great content posted every day. During this time, I've been very cautious of making many significant changes, but this is about to change.
GitHub recently announced new features and support for multiple issue templates. Before, GitHub supported a single template, by supporting multiple types of issues, we can gather the right information from the beginning.
It was a wonderful experience to present at the Azure Global Bootcamp in Melbourne this year. This year I spoke about possible methods or patterns for securing Azure resources. This is an extremely board topic, though I focused on App Services, Virtual Network Endpoints and ARM templates.
Several days ago, Jared raised a Pull Request for Posh-SYSLOG to correct an issue with the moduleās manifest. It seems that in version 3.0 of Posh-SYSLOG, I used the PowerShellHostVersion attribute of the module manifest and not PowerShellVersion to specify the minimum Powershell version. This wouldn't have created issues within a normal PowerShell session, but would have prevented the module from loading in VS Code (as Jared reported) or the ISE.
