profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/kiwiz/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.

kiwiz/gkeepapi 1169

An unofficial client for the Google Keep API.

Kennysan/CSPTools 37

Content Security Policy Creation tools

kiwiz/keep-cli 21

Terminal-based Google Keep

kiwiz/esquery 18

Elasticsearch querying library

ancat/chef 1

Make available a bunch of cool infosec related projects via chef for e-z installation

blankwall/Build_it_Break_it 1

Repository for Build it Break it Contest Fall 2014

breadchris/PolyCTF 0

CTF challenges for a small competition run specifically for NYU Poly students

startedmkdocs/mkdocs

started time in 12 days

startedmgdm/htmlq

started time in 17 days

startedsecxena/credcheck

started time in 22 days

startedstreaak/keyhacks

started time in 22 days

issue commentkiwiz/gkeepapi

Sync single item

Unfortunately, there is no way to do so - this is exactly how the official clients work too. You can, however, download just the updates to the node tree if you cache it locally. See here for details.

Also, if you just need to dump out the contents of a note, you might be able to use https://github.com/kiwiz/keep-cli

cculpepper

comment created time in 22 days

issue commentreturntocorp/semgrep

Relative `paths` are not handled properly

Relevant thread: https://r2c-community.slack.com/archives/C018NJRRCJ0/p1630349798014700

kiwiz

comment created time in 25 days

issue openedreturntocorp/semgrep

Relative `paths` are not handled properly

Describe the bug Prior to 0.58, an paths.include path with a ./ would properly pick up the file.

To Reproduce

rules:
- id: test-rule
  languages:
  - generic
  message: hi
  paths:
    include:
    - ./readme.md
  patterns:
  - pattern: ''
  severity: INFO
  1. Create a file called readme.md and put some content in it
  2. Run the rule against semgrep 0.57 and 0.58.

Expected behavior Semgrep should scan the target file.

Screenshots If applicable, add screenshots to help explain your problem.

What is the priority of the bug to you?

  • [ ] P0: blocking your adoption of Semgrep or workflow
  • [ ] P1: important to fix or quite annoying
  • [x] P2: regular bug that should get fixed

Environment Official binary

created time in 25 days

delete branch kiwiz/salus

delete branch : optimize

delete time in 25 days

delete branch kiwiz/salus

delete branch : strings_fix

delete time in 25 days

issue commentreturntocorp/semgrep

Semgrep won't scan files that don't end with the right extension

Bump (although it looks like there's work going on in the linked issues)

kiwiz

comment created time in a month

delete branch kiwiz/salus

delete branch : semgrep_no_version_check

delete time in 2 months

PR closed coinbase/salus

Disable semgrep version check

This causes the error handling logic to pick up the wrong line if a new version exists.

+2 -0

2 comments

1 changed file

kiwiz

pr closed time in 2 months

delete branch kiwiz/salus

delete branch : semgrep_0_40

delete time in 2 months

PR closed coinbase/salus

Upgrade semgrep to v0.48.0
+4 -4

8 comments

4 changed files

kiwiz

pr closed time in 2 months

Pull request review commentcoinbase/salus

Integrate Gitleaks scanner

+require "salus/scanners/base"+require "json"++# Gitleaks scanner integration. Detects hardcoded secrets like passwords,+# api keys, and tokens in git repos.+# https://github.com/zricethezav/gitleaks++module Salus::Scanners+  class Gitleaks < Base+    def run+      Dir.chdir(@repository.path_to_repo) do+        copts = config_options+        shell_return = run_shell(+          'gitleaks '\+          '--path . '\+          '--format sarif '\+          '--report /dev/stdout '\+          '--leaks-exit-code 0 ' +

I'm using --leaks-exit-code 0 to distinguish between a configuration error with gitleaks and results (which get processed further down).

kiwiz

comment created time in 2 months

PullRequestReviewEvent

pull request commentcoinbase/salus

Integrate Gitleaks scanner

There are 10+ binary files in the PR. Are all of them needed to test the commit scanning feature?

I haven't exhaustively tested them all, but I confirmed that removing a few will break tests.

kiwiz

comment created time in 2 months

Pull request review commentcoinbase/salus

Integrate Gitleaks scanner

+require "salus/scanners/base"+require "json"++# Gitleaks scanner integration. Detects hardcoded secrets like passwords,+# api keys, and tokens in git repos.+# https://github.com/zricethezav/gitleaks++module Salus::Scanners+  class Gitleaks < Base+    def run+      Dir.chdir(@repository.path_to_repo) do+        copts = config_options+        shell_return = run_shell(+          'gitleaks '\+          '--path . '\+          '--format sarif '\+          '--report /dev/stdout '\

--report is required to output to stdout. Otherwise, only debug data is output (to stderr).

kiwiz

comment created time in 2 months

PullRequestReviewEvent

created repositorykiwiz/temp-test-repo

created time in 2 months

pull request commentkiwiz/gkeepapi

Fix node.untrash()

Thanks for the PR. I've bumped the version and uploaded.

stevearc

comment created time in 2 months

push eventkiwiz/gkeepapi

K

commit sha c5daf8ebfebc2db3db0e9b09e0aab8257ee1ca45

Bump version

view details

push time in 2 months

PR merged kiwiz/gkeepapi

Fix node.untrash()

This call was working locally but failing to untrash the note in Google Keep. It looks like the API has changed.

+3 -2

0 comment

2 changed files

stevearc

pr closed time in 2 months

push eventkiwiz/gkeepapi

Steven Arcangeli

commit sha 970f0de321a2664b4075676506baa5a7c53892f7

Fix node.untrash() This call was working locally but failing to untrash the note in Google Keep. It looks like the API has changed.

view details

Kai

commit sha 2790b55e523317d8f63b74baffa4a29ab8a6ca29

Merge pull request #114 from stevearc/master Fix node.untrash()

view details

push time in 2 months

issue commentkiwiz/gkeepapi

Segmentation fault on Apple M1

The BadAuthentication issue is probably related to https://github.com/kiwiz/gkeepapi/issues/81. Rather than gpsoauth you might get some results with changing the version of pycryptodome (but this might break your env in other unexpected ways).

Your best bet might be to run your code in a Docker container for now. :thinking:

elammertsma

comment created time in 2 months

issue commentkiwiz/gkeepapi

Segmentation fault on Apple M1

Looks like this is related to https://github.com/Legrandin/pycryptodome/issues/506. You might be able to work around this by using a different Python version?

elammertsma

comment created time in 2 months

issue commentkiwiz/gkeepapi

Cannot dedent list item

Thanks for the bug report. Looks like the signal for an unindented ListItem changed to an empty string. I uploaded 0.13.5, which should fix this issue.

stevearc

comment created time in 2 months

push eventkiwiz/gkeepapi

K

commit sha fdf67550325b762b43220bc618af094c672548db

Issue #112: Fix dedenting

view details

push time in 2 months

push eventkiwiz/gkeepapi

Kai

commit sha df8545264f68a51a0784deb68ea26d310fbb2da0

Update README.md

view details

push time in 2 months

push eventkiwiz/salus

ghbren

commit sha 6820293b95e05e67f2516427c905295271c4231c

Merge pull request #398 from CoinsNaulty/fix-readme-logo fix dead link in salus logo in README.md

view details

Kai

commit sha 9ff5232942e0a7676acd2d3ef48c1074c07393d7

Merge branch 'master' into gitleaks

view details

push time in 2 months