vverbose don't show author in output

[mr-tz]

analogous to #973, remove author as not really helpful when inspecting rules

[pradkrish]

I am happy to work on this. is this still open?

[williballenthin]

that would be great! please make an attempt and open a PR for review and merge

[pradkrish]

Thanks, consider me a beginner. The usage is not really clear to me. I installed the developer version in my venv and I am able to import capa inside my venv. Can you give me an example code with an input elf file that I can use for this PR? Thanks.

[mr-tz]

you should be able to test with any PE or ELF file by running capa -vv <sample>

[pradkrish]

When I tried to run capa -vv /usr/bin/pwd

I got the following error

loading :   2%|█▏                                             | 16/665 [00:00<00:00, 2455.50 rules/s]
ERROR:capa:invalid rule: /home/pradeep/repos/capa/capa/../rules/communication/socket/tcp/send/obtain-transmitpackets-callback-function-via-wsaioctl.yml: invalid rule: unexpected statement: number/x64

I found similar error when I tried it on some elf files in capa/tests/data

[mr-tz]

:( please see related issue: mandiant/capa-rules#551
to quickly fix you can checkout the respective rules tag

[mr-tz]

Are you still encountering this error with current master? Anything we can help you with to get started?

[pradkrish]

Thanks, it works now. To fix the issue here, is it about removing line 202 from capa/render/vverbose.py?

[mr-tz]

yeah, kinda, you can take https://github.com/mandiant/capa/pull/973/files as a good example

[pradkrish]

I have a question about the PR process. After committing the changes locally, when I run git push origin <branch-name>, it triggers linting and then tests which ends like this

Results (454.66s):
     479 passed
     129 xfailed
       3 skipped
Tests succeed!! 🎉
Stashed changes 'pre-push-1652443209' restored
SUCCEEDED 🎉🎉

The tests clearly pass but I don't see any updates on the forked repo.

[mr-tz]

You should be able to create a PR on GitHub now for your branch.

[mr-tz]

Do you get any output on the command line?
This page has further details on creating a PR https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request and I am happy to help here as well.

[mr-tz]

@pradkrish can you submit your PR or share your changes? Would love to get this in soon.

[pradkrish]

@mr-tz That is the problem. After the push operation, I do not see it when I checked on my forked repo for the pushed branch. This is despite passing tests. Anyways, the only change I have done is to remove the line capa/render/vverbose.py:202. Sorry that I couldn't complete the PR. I have done this several hundred times and I don't know what I am missing here. 🤔

[mr-tz]

Can you double-check to commit and/or push with the --no-verify option?

[williballenthin]

this was fixed in #981

capa/capa/render/verbose.py

Line 131 in 6fa8f9e

for key in ("namespace", "description", "scope"):