profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/bplaxco/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

bplaxco/libmsgsvc 2

A message bus implemented over IRC

bplaxco/mctools 1

Tools for helping out a friend run some processes on his server.

bplaxco/pong-js 1

Pong implemented in JavaScript

johncalvinyoung/asset-rack 1

Static Web Framework for Nodejs

bplaxco/Arduino 0

Misc Arduino sketches

bplaxco/edit 0

A fork of uemacs to mess around with on the side

bplaxco/fake-leaks 0

Things that would cause a git leaks scan to freak out

bplaxco/jenkins-runner 0

A small script for doing remote Jenkins builds from my makefiles

bplaxco/lupkg 0

A packaging tool for combining multiple resources into a single executable.

bplaxco/mailcat 0

prints emails sent to it to stdout

push eventbplaxco/fake-leaks

Braxton Plaxco

commit sha fdcbbadc6e8707ee746b8256c9a52bdd4d431161

Make a change so there's a new commit ~ B'ezrat Hashem ~

view details

push time in 22 days

fork bplaxco/lupkg

A packaging tool for combining multiple resources into a single executable.

fork in 23 days

PR opened keycloak/keycloak

KEYCLOAK-19155: Add a .gitleaks.toml

Help ignore false positives during internal code scans.

+11 -0

0 comment

1 changed file

pr created time in 24 days

push eventbplaxco/keycloak

Braxton Plaxco

commit sha 3a44365004115e8bc70facf33320c0e184faa4fb

KEYCLOAK-19155: Add a .gitleaks.toml Help ignore false positives during internal code scans ~ B'ezrat Hashem ~

view details

push time in 24 days

push eventbplaxco/keycloak

Braxton Plaxco

commit sha dc0a8c1b530d225e3f6beb17e5361ef443115ee9

Add a .gitleaks.toml Help ignore false positives during internal code scans ~ B'ezrat Hashem ~

view details

push time in 24 days

fork bplaxco/keycloak

Open Source Identity and Access Management For Modern Applications and Services

https://www.keycloak.org

fork in 24 days

issue commentreconmap/reconmap

Question about alternate login mechanisms

Cool cool, thanks for confirming ^_^

bplaxco

comment created time in 25 days

issue commentreconmap/reconmap

Question about alternate login mechanisms

@santiagolizardo is there anything that needs to be done with this request (given the plan to add it to the roadmap), or is it alright if stalebot closes it out?

bplaxco

comment created time in a month

create barnchbplaxco/fake-leaks

branch : test

created branch time in a month

push eventbplaxco/fake-leaks

Braxton Plaxco

commit sha 17fe5f788d02ee1b387ab80ee2b7e93e0235987f

Add a test secret to config.json ~ B'ezrat Hashem ~

view details

push time in a month

PR closed osbuild/osbuild-composer

Add .gitleaks.toml

I'd like to add this to help a few scanners avoid false positives. If you have an guidance on how to tune that config so that it doesn't ignore a real leak, just let me know and I can make the necessary changes.

This pull request includes:

  • [X] adequate testing for the new functionality or fixed issue
  • [X] adequate documentation informing people about the change such as
    • [X] create a file in news/unreleased directory if this change should be mentioned in the release news (no need to mention in release)
    • [X] submit a PR for the guides repository if this PR changed any behavior described there: https://www.osbuild.org/guides/ (no behavior was changed)

<!-- Thanks for proposing a change to osbuild-composer!

Please don't remove the above check list. These are things that each pull request must have before it is merged. It helps maintainers to not forget anything.

If the reason for ticking any of the boxes is ambiguous, please add a short note explaining why.

For user-visible changes, "adequate documentation" is an entry describing the change for users in docs/news. Please refer to docs/news/README.md for details.

In addition, if this pull request fixes a downstream issue, please refer to test/README.md and add these additional items:

  • [ ] 1st commit of any rhbz# related PR contains bug reproducer; CI reports FAIL or
  • [ ] PR contains automated tests for new functionality and
  • [ ] QE has approved reproducer/new tests and
  • [ ] Subsequent commits provide bug fixes without modifying the reproducer; CI reports PASS and
  • [ ] QE approves this PR; RHBZ status is set to MODIFIED + Verified=Tested -->
+12 -0

4 comments

1 changed file

bplaxco

pr closed time in 2 months

pull request commentosbuild/osbuild-composer

Add .gitleaks.toml

After a discussion with @ondrejbudai, I'm going to go ahead and kill this so things can be handled on a case by case basis as alerts are raised ^_^

bplaxco

comment created time in 2 months

issue commentreconmap/reconmap

Question about alternate login mechanisms

@santiagolizardo cool, thanks! Out of the two (OIDC vs SAML) OIDC would be the preferred (plus I've found that one easy to implement by from scratch if not going the oauth2-proxy route).

bplaxco

comment created time in 2 months

issue openedreconmap/reconmap

Question about alternate login mechanisms

Question, is there any way to set up an OIDC or SAML login flow with Reconmap? Or maybe integrate it with https://oauth2-proxy.github.io/oauth2-proxy/?

I poked around the docs and code a bit but I may have missed it.

created time in 2 months

push eventbplaxco/python-examples

Braxton Plaxco

commit sha 3c0bab746f0da4b255f9a062d93b9afa572b4d8f

Stub out more examples ~ B'ezrat Hashem ~

view details

push time in 2 months

push eventbplaxco/osbuild-composer

Braxton Plaxco

commit sha 98443c1c35979039bacc1da5ead73a88d9f56270

Add a 'more info' link ~ B'ezrat Hashem ~

view details

push time in 2 months

push eventbplaxco/python-examples

Braxton Plaxco

commit sha e3e86aa0c225e5b9598cd82e215af5866312ac98

Stub out more examples ~ B'ezrat Hashem ~

view details

push time in 2 months

push eventbplaxco/python-examples

Braxton Plaxco

commit sha dbb465a37ee44c9d59bbc0a098b19c96fc2dbd01

Add a few examples ~ B'ezrat Hashem ~

view details

push time in 2 months

delete branch bplaxco/python-examples

delete branch : add-license-1

delete time in 2 months

push eventbplaxco/python-examples

bplaxco

commit sha 4dd1e1839705c3182afa966a843aa5f5c9c57c9d

Create LICENSE

view details

bplaxco

commit sha 673013ebd1b60e3600142a39f4a6c4f7ba73a45f

Merge pull request #1 from bplaxco/add-license-1 Create LICENSE

view details

push time in 2 months

PR merged bplaxco/python-examples

Create LICENSE
+21 -0

0 comment

1 changed file

bplaxco

pr closed time in 2 months

PR opened bplaxco/python-examples

Create LICENSE
+21 -0

0 comment

1 changed file

pr created time in 2 months

create barnchbplaxco/python-examples

branch : add-license-1

created branch time in 2 months

create barnchbplaxco/python-examples

branch : main

created branch time in 2 months

created repositorybplaxco/python-examples

A place to capture examples when explaining Python to others

created time in 2 months

push eventbplaxco/fake-leaks

Braxton Plaxco

commit sha 01ef5781aa6233c6b4141e0cb463b451d9aad0e4

Add fake pull secrets ~ B'ezrat Hashem ~

view details

push time in 2 months

issue openedreconmap/web-client

Question about alternate login mechanisms

Question, is there any way to set up an OIDC or SAML login flow with Reconmap? Or maybe integrate it with https://oauth2-proxy.github.io/oauth2-proxy/?

I poked around the docs and code a bit but I may have missed it.

created time in 2 months

pull request commentosbuild/osbuild-composer

Add .gitleaks.toml

Hi! I wonder how this is beneficial to our project? In case of a leak, will you notify us? How? It feels to me that I need more information about this project until I can review this PR. Thanks! :)

Yep we'll notify you. I'll follow up in work chat.

You need to enable the gitleaks GitHub Action at least. Otherwise the config file by itself is useless. There's an external scanner :)

bplaxco

comment created time in 2 months

PR opened osbuild/osbuild-composer

Add .gitleaks.toml

I'd like to add this to help a few scanners avoid false positives. If you have an guidance on how to tune that config so that it doesn't ignore a real leak, just let me know and I can make the necessary changes.

This pull request includes:

  • [X] adequate testing for the new functionality or fixed issue
  • [X] adequate documentation informing people about the change such as
    • [X] create a file in news/unreleased directory if this change should be mentioned in the release news (no need to mention in release)
    • [X] submit a PR for the guides repository if this PR changed any behavior described there: https://www.osbuild.org/guides/ (no behavior was changed)

<!-- Thanks for proposing a change to osbuild-composer!

Please don't remove the above check list. These are things that each pull request must have before it is merged. It helps maintainers to not forget anything.

If the reason for ticking any of the boxes is ambiguous, please add a short note explaining why.

For user-visible changes, "adequate documentation" is an entry describing the change for users in docs/news. Please refer to docs/news/README.md for details.

In addition, if this pull request fixes a downstream issue, please refer to test/README.md and add these additional items:

  • [ ] 1st commit of any rhbz# related PR contains bug reproducer; CI reports FAIL or
  • [ ] PR contains automated tests for new functionality and
  • [ ] QE has approved reproducer/new tests and
  • [ ] Subsequent commits provide bug fixes without modifying the reproducer; CI reports PASS and
  • [ ] QE approves this PR; RHBZ status is set to MODIFIED + Verified=Tested -->
+9 -0

0 comment

1 changed file

pr created time in 2 months

push eventbplaxco/osbuild-composer

Braxton Plaxco

commit sha 649e5115c4a6f60e366a3989698bcb055f1d625d

Add comments to the config ~ B'ezrat Hashem ~

view details

push time in 2 months