I used the amazing Creality Helper Script by Guilouz to set up OctoEverywhere on my Creality K1 printer. The script automates much of the process, making it straightforward to get remote access to your printer.
Unfortunately the script failed as it seems the install script doesn’t specify a version for the python pillow package, and the latest version requires gcc. Here’s the error I received:
I recently purchased a Creality K1 Max, and have been enjoying the larger 300x300 print volume. One thing that I found a bit annoying was the default bed mesh size - it’s set to 6x6, which is a bit too small considering the well-known issues of bed warping and levelling. I wanted to change it to 12x12, which although slower to probe, would give me a better idea of the bed’s shape.
I’ve recently switched over to Linux Mint from years of using Ubuntu as a desktop OS. So far, so good - it’s more than decent for a desktop distro, with the window manager Cinnamon taking less CPU and memory than it’s counterparts.
One of my first actions when (re)building is to create a set of VMs - one for study, one for work, one for <INSERT UNFINISHED PROJECT HERE>. Part of this is figuring out which hypervisor to use, which to date has been VMware Workstation. Unfortunately Broadcom’s acquisition has led to price increases impacting the overall support renewal invoice, and I’ve had to drop Workstation to save some $$$.
Hello, fellow DIYers and smart home enthusiasts! Today I want to share with you how I built a garage door opener using an ESP8266 enabled relay and Home Assistant (hass.io). This project was inspired by the need to remotely control my garage door from anywhere in the world, and also to integrate it with my existing smart home system. Here are the steps I followed:
In my previous life as a billable cybersec consultant / technical lead, I was looking for a way to deliver phishing tests across our customers in a consistent and repeatable manner. Many options existed such as those supplied by KnowBe4, Defender for M365, Trend - but we couldn’t warrant the cost burden of those solutions until we’d proven the value of the service.
Scoping Jamf policies for AD groups is a breeze when your users are logging in with AD credentials. But what if you’re O365/AAD only? The Jamf agent won’t recognize an AAD logon unless you’re using Jamf Connect. Sure, it’s unusual to have one without the other, but I have a solution here if you’re running lean.
So you’re running a macOS shop, and using Office 365 for identity, email, and data storage. You want to decrease risk of data loss, manage the security of corporate data, and provide staff the ability to share files in a controlled manner.
You also want to make it super easy for staff to adopt.
The ability to find and install PowerShell modules from online sources like Nuget makes life for a Windows admin a smidge nicer. On the flipside, arbitrary trust of online package repositories and granting servers outbound internet access can be a nightmare for those tasked with protecting a network.
You might find yourself needing to install a PowerShell module (as a nupkg file) on a system with restricted (or no) internet access, as one of our security consultants found himself needing to do.
Our lead infosec analyst Pierre and I recently had the opportunity to attend CyberCon 2019 in Melbourne. The event is organised by AISA in collaboration with the Australian Cyber Security Centre (ACSC). This event brings in 140+ infosec speakers and individuals from over 24 countries.
With so many interesting sessions in technical, governance, and commercial ‘tracks’ it was difficult to select just one for any given hour-long block of time! Many of the sessions were so packed, people were standing in the lobby watching a feed of the session delivered to screens outside the conference rooms.