![jack](https://water.house/system/accounts/avatars/112/959/761/063/687/147/original/167ec7e616a68e28.jpg?format=webp&thumbnail=64)
🇦🇺 Cybersecurity bloke with a bit of personality. This page is a hub for all my blogs and projects—a true @jack of all trades.
Everything here is self-hosted on my own hardware. I cover cybersecurity and various other interests, including:
💬 Macroblogging: https://water.house/@jack/tagged/macroblog 🕵️ Cybersecurity: https://water.house/@jack/tagged/infosec 📸 Photography: https://water.house/@jack/tagged/photography 📝 To-do List: https://water.house/@jack/tagged/todo 🔬 Homelab: https://water.house/@jack/tagged/homelab 📍 Reviews: https://water.house/@jack/tagged/review
@pipes Yeah it's biggest pro is also its con and where the reputation of Debian's stability comes from.
I was using Plasma 6 Wayland 3 months ago in Arch and half my desktop apps were busted. Discord was so bad that I had to use X11.
I was newer to Linux desktop then so I spent so long thinking the problem was with me and trying to figure it out. Wayland Nvdia stability has seemed to settle down a lot though.
I'll miss Wayland 6 as it's really nice on high refresh displays but I think it's a reasonable trade off for stability, and it'll eventually be back.
Been daily driving Arch for 6 months now, but considering moving back to Debian. Not really taking full advantage of the Arch pros
Been daily driving Arch for 6 months now, but considering moving back to Debian. Not really taking full advantage of the Arch pros
While a bleeding-edge kernel is great, I don't particularly need it. pacman
is nice, but apt
gets the job done too. Has anyone else switched from Arch to @debian? If so, did you miss anything from Arch that Debian couldn't replicate?
Knowing When To Walk Away — The Four Hour Interview
Knowing When To Walk Away — The Four Hour Interview
A while ago, I received a lead from a startup for a potential contract.
They reached out to me after undergoing a cybersecurity review by a third-party company and had done very poorly.
For example, they lacked even the most basic security measures like multifactor authentication which I'd consider a bare minimum in today's climate.
Despite this, I was interested as it's kind of my job to help with something like this. Here is how the interview process went:
The first hour The interview process began smoothly. The initial interview was online with the person I'd be reporting to. It lasted an hour, and I felt it went well.
The second hour The next interview was in person with another executive in a related role. Once again, no red flags.
The third hour By the third interview, I was getting a bit tired. This time, it was with a HR executive. I respected the process, but I'll admit that after three hours, the thought of charging for my time had crossed my mind.
The fourth hour After the third interview, they still seemed interested but wanted me to meet with the company that handles their outsourced cybersecurity services, known as a Managed Security Service Provider (MSSP). I was hesitant but agreed. In hindsight, this was a mistake for several reasons:
- Misaligned Priorities: The MSSP doesn't represent the company, and the interview felt off. Most of the questions revolved around how I'd be funneling work to the MSSP and implied that my role would hold little value in the bigger picture.
- Low Cyber Maturity: Given the organisation's low cyber maturity, involving an existing solution at this stage seemed counterproductive.
After a very strange 15-minute interview with the MSSP, they informed me that they had decided not to proceed with the role. Looking back, there are a few things I could have done differently:
- Set Boundaries: I should have budgeted no more than four hours of free time for the interview process.
- Decline External Stakeholder Meetings: I should have refused to meet with external stakeholders who are not directly involved in the decision-making process.
I think it's okay to say no, especially when dealing with startups that are still finding their footing.
What would you do in this situation?
Yeah I originally trying to daily Linux for like the past 10 years but kept falling back to Windows, mainly due to the app compatibility.
A lot of people suggested dual booting but I found that it messed up my workflow, and Level 2 hypervisors don't have great HW acceleration
So what finally made Linux stick for me was Proxmox.. it let daily Linux and still have the option to quickly spin up a Windows VM with a GPU if I needed something urgently, without the hassle of rebooting.
So now, six months later, I’m dailying Arch and also self-hosting a bunch of stuff on Debian, and I haven’t looked back.
I think it's about convenience.
Tags for federation: @acceptable_humor #infosec
@catculation This has happened before and is a really big issue, but wouldn't some sort of network segmentation have helped prevent this especially as it's happened before?
I gave away my wife's Wyze camera and moved to Ubiquiti. It cost me a small fortune.
Not self-hosting at the moment but still, nothing can be as bad as Wyze, right?
@Squizzy @yamanii This extension does exactly that (at least on desktop) and stops doom scrolling without removing them entirely: https://github.com/doma-itachi/Youtube-shorts-block
@Usernameblankface Some sort of attack that manages to take down Cloudflare, AWS, Azure, and Google Services at the same time. Would break a lot more than just the internet though.
@HipHoboHarold @flintheart_glomgold
Yes, I have noticed a trend of homelab hobbyists going back to something like this:
- Soulseek -> Nicotine+ for plentiful, lossless content
- Jellyfin for self-hosting
- Infuse for streaming the content remotely to save storage on your phone.
I don't endorse piracy for ethical reasons, but I get why this is trending up:
-Increasingly aggressive pricing models
-Service quality and content accessibility going down
Really makes it hard for consumers...