diff options
Diffstat (limited to 'content/blog')
7 files changed, 21 insertions, 20 deletions
diff --git a/content/blog/2026-02-02-emacs-carnival-2026-02-completion.org b/content/blog/2026-02-02-emacs-carnival-2026-02-completion.org index 8f38cfa..f641a44 100644 --- a/content/blog/2026-02-02-emacs-carnival-2026-02-completion.org +++ b/content/blog/2026-02-02-emacs-carnival-2026-02-completion.org @@ -5,7 +5,7 @@ #+filetags: :emacs:personal: I'm having a great time with the Emacs Carnival, as it has inspired me to write -two posts in such a short time. It's been a much needed inspiration to write +two posts in such a short time. It's been a much-needed inspiration to write during my busy season at work. Anyway, let's get to it. The topic today is [[https://www.emacswiki.org/emacs/CategoryCompletion][Completion]]: the magical thing that @@ -45,8 +45,8 @@ time string, like so: ~2026-02-02 21:52:55~. ~¯\_(ツ)_/¯~ This comes in handy most at work, where I need to constantly use acronyms and -take shorthand notes to fill-out phrases that I'm, unfortunately, required to -re-use constantly. Looking at you, "completeness and accuracy of the data". +take shorthand notes to fill out phrases that I'm, unfortunately, required to +reuse constantly. Looking at you, "completeness and accuracy of the data". * Doom Configuration @@ -67,6 +67,7 @@ Here is how I have my ~:completion~, ~:tools~, and ~:lang~ modules toggled in (spell +flyspell) ; tasing you for misspelling mispelling grammar ; tasing grammar mistake every you make + :tools (lsp +eglot) ; M-x vscode @@ -133,7 +134,7 @@ workflows. ** [[https://github.com/leotaku/flycheck-aspell?tab=readme-ov-file][flyspell]] Flyspell is the last piece to my puzzle, as it allows for easy help in -correcting grammar errors within the buffer. I combine ~flypell~ + ~syntax~ + +correcting grammar errors within the buffer. I combine ~flyspell~ + ~syntax~ + ~grammar~ for ultimate writing guidance. Whether or not I choose to follow that guidance is another story entirely. diff --git a/content/blog/2026-02-12-automating-weblorg-deployments.org b/content/blog/2026-02-12-automating-weblorg-deployments.org index 9cb34cb..ab38020 100644 --- a/content/blog/2026-02-12-automating-weblorg-deployments.org +++ b/content/blog/2026-02-12-automating-weblorg-deployments.org @@ -166,7 +166,7 @@ However, that's way too manual for me. Let's be lazy and take it even further. * GitHub Actions -So, how do we push it further. By removing the need to run a command (outside of +So, how do we push it further? By removing the need to run a command (outside of ~git~) at all! This process will: diff --git a/content/blog/2026-02-21-auditing-aws-iam.org b/content/blog/2026-02-21-auditing-aws-iam.org index ddcb563..36498cc 100644 --- a/content/blog/2026-02-21-auditing-aws-iam.org +++ b/content/blog/2026-02-21-auditing-aws-iam.org @@ -115,7 +115,7 @@ individual accounts and provides centralized access management across all of them from a single place. It connects to an identity source, such as AWS's own directory, Active -Directory, or an externali identity provider (IdP) like Okta or Entra ID, and +Directory, or an external identity provider (IdP) like Okta or Entra ID, and uses that as the source of truth for users and groups. Access is configured within Identity Center itself, not inside individual accounts. @@ -295,7 +295,7 @@ exception, here's how to frame it: - *Deficiency:* User ~iamtestuser1~ is directly assigned the ~AdministratorAccess~ permission set in account ~cmc~, rather than receiving access through a group assignment. -- *Root Cause:* Due to {{ root cuase }}, the user ~iamtestuser1~ was inappropriately +- *Root Cause:* Due to {{ root cause }}, the user ~iamtestuser1~ was inappropriately provisioned the ~AdministratorAccess~ permission directly rather than through a group assignment. - *Risk:* Direct user assignments increase the likelihood of orphaned access diff --git a/content/blog/2026-02-21-auditing-aws-passwords.org b/content/blog/2026-02-21-auditing-aws-passwords.org index 734dc9c..71ef799 100644 --- a/content/blog/2026-02-21-auditing-aws-passwords.org +++ b/content/blog/2026-02-21-auditing-aws-passwords.org @@ -13,7 +13,7 @@ The scripts are available at [[https://github.com/audit-labs/audit-tools/tree/ma * Scoping -First thing's first: scoping. To audit AWS passwords, we need to understand that +First thing first: scoping. To audit AWS passwords, we need to understand that AWS IAM password policies only apply to users with console access. This isn't the same as the password policy for an application built on top of AWS. It also has no effect on users who authenticate through IAM Identity Center, which diff --git a/content/blog/2026-04-22-self-hosting-zerobyte.org b/content/blog/2026-04-22-self-hosting-zerobyte.org index 7404ebd..1af1622 100644 --- a/content/blog/2026-04-22-self-hosting-zerobyte.org +++ b/content/blog/2026-04-22-self-hosting-zerobyte.org @@ -7,7 +7,7 @@ [[https://zerobyte.app][Zerobyte]] is a slick backup solution you can self host. It's one of the easiest apps I've self hosted and the backup jobs are running smoothly. -In this post, I will show you how I've configured backups on my server to backup +In this post, I will show you how I've configured backups on my server to back up data to Cloudflare R2. * Installation @@ -157,7 +157,7 @@ cron pattern). This allows you to specify: - The volume to be backed up - The repository to back up to - The schedule -- The files to backup (all will be backed up if nothing is specifically selected) +- The files to back up (all will be backed up if nothing is specifically selected) - Include/exclude patterns - Retention policies - Custom restic patterns @@ -166,7 +166,7 @@ cron pattern). This allows you to specify: [[https://img.cleberg.net/blog/20260422-self-hosting-zerobyte/backups_01.webp]] Within a backup job, you can configure the related notifications, snapshots, or -backup/edit/cleanup the job. +back up, edit, or clean up the job. #+CAPTION: Backup Job Details [[https://img.cleberg.net/blog/20260422-self-hosting-zerobyte/backups_02.webp]] diff --git a/content/blog/2026-05-20-git-is-not-github.org b/content/blog/2026-05-20-git-is-not-github.org index 9179591..4fc03f3 100644 --- a/content/blog/2026-05-20-git-is-not-github.org +++ b/content/blog/2026-05-20-git-is-not-github.org @@ -87,7 +87,7 @@ For example, I can create a local Git repository, expose it through the Git protocol, and share this info with a friend or coworker. Then, they can clone my repository and we can collaborate by making changes independently and using commits, branches, etc. to push changes back and forth with each other. In this -scenrio, there is *no* host and we are essentially a distributed network of our +scenario, there is *no* host and we are essentially a distributed network of our own. At its core, Git answers technical history questions: @@ -100,7 +100,7 @@ At its core, Git answers technical history questions: - How did this branch differ from that branch? That is valuable, but it is not the whole development process. This is where Git -hosts introduce useful, addition features on top of Git. +hosts introduce useful, additional features on top of Git. * Git Hosts Add the Workflow @@ -145,7 +145,7 @@ First, here are some common controls: - The repository is configured to: - prevent force pushes; - require X approvals; - - prevent approvals from the author or a person who can committed within the + - prevent approvals from the author or a person who committed within the pull request; - require testing to pass prior to merging; - include the relevant change ticket(s)/documentation. @@ -158,26 +158,26 @@ First, here are some common controls: Now, where can we find this evidence? Let's step through each - Normally, reviews and approvals can be found directly within the pull/merge - request. For platforms such as Github, this platform enables code reviews, + request. For platforms such as GitHub, this platform enables code reviews, comments, feedback, and checks directly within the PR flow. In certain cases, this may be documented in a change ticket system and the ticket is referenced within the PR to prove that the PR was tested, reviewed, and approved prior to merging. -- For configurations, GitHub supports both [[https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule][classic branch protections rules]] and +- For configurations, GitHub supports both [[https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule][classic branch protection rules]] and [[https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets][rulesets]], which can enforce all of the checks I mentioned above. - For access, it depends on the company's setup. They may be using GitHub Enterprise, which offers them more control over access, and teams can inspect - the access inheritence through those Enterprise settings. Otherwise, + the access inheritance through those Enterprise settings. Otherwise, non-enterprise GitHub organizations can show evidence of access at both the organization level and the repository level. Auditors can inspect the levels - of access and inheritence to ensure that no users have the ability to develop + of access and inheritance to ensure that no users have the ability to develop changes, manage branch protections, approve changes, and deploy changes. - For branch protection settings, management can provide auditors with an export of the audit logs relevant to the in-scope repositories. This will show you if any events occurred that would have disabled or modified the branch protections in place. -If your inspecting a project where CI/CD pipelines matter, you can also dive +If you're inspecting a project where CI/CD pipelines matter, you can also dive into the team's configuration of their pipeline in terms of the logic, access to modify, and any relevant schedules or triggers. diff --git a/content/blog/2026-06-01-macos-motd.org b/content/blog/2026-06-01-macos-motd.org index 316e97a..5d42f34 100644 --- a/content/blog/2026-06-01-macos-motd.org +++ b/content/blog/2026-06-01-macos-motd.org @@ -116,7 +116,7 @@ chmod +x ~/.motd.sh At this point, the script is ready. We simply need to tell macOS to execute it whenever the user launches a new shell. -To do this, open the =.zprofile= file add a line referencing the script: +To do this, open the =.zprofile= file and add a line referencing the script: #+begin_src shell nano ~/.zprofile |