Skip to content

Conversation

@suajose
Copy link
Contributor

@suajose suajose commented Dec 6, 2022

PR Summary

Add Instrumentation to AmsiUtil and make the init variable readonly

PR Context

PR Checklist

Making the variable readonly raises the bar for bypass AmsiScan, The new added events helps track tampering and initialization success.

@TravisEz13 TravisEz13 assigned TravisEz13 and unassigned anmenaga Dec 6, 2022
@TravisEz13 TravisEz13 added Backport-5.1-Consider Consider to backport to Windows PowerShell 5.1 due to impact Backport-7.3.x-Consider labels Dec 6, 2022
@ghost ghost added the Waiting on Author The PR was reviewed and requires changes or comments from the author before being accept label Dec 6, 2022
@ghost ghost removed the Waiting on Author The PR was reviewed and requires changes or comments from the author before being accept label Dec 6, 2022
@TravisEz13 TravisEz13 enabled auto-merge (squash) December 9, 2022 16:53
@TravisEz13 TravisEz13 added the CL-Engine Indicates that a PR should be marked as an engine change in the Change Log label Dec 9, 2022
@suajose suajose requested a review from PaulHigin December 12, 2022 21:06
@ghost ghost added Waiting on Author The PR was reviewed and requires changes or comments from the author before being accept and removed Waiting on Author The PR was reviewed and requires changes or comments from the author before being accept labels Dec 12, 2022
auto-merge was automatically disabled December 13, 2022 21:43

Head branch was pushed to by a user without write access

@pull-request-quantifier-deprecated

This PR has 87 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!


Quantification details

Label      : Small
Size       : +76 -11
Percentile : 34.8%

Total files changed: 7

Change summary by file extension:
.man : +49 -3
.cs : +27 -8

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

  • Fast and predictable releases to production:
    • Optimal size changes are more likely to be reviewed faster with fewer
      iterations.
    • Similarity in low PR complexity drives similar review times.
  • Review quality is likely higher as complexity is lower:
    • Bugs are more likely to be detected.
    • Code inconsistencies are more likely to be detected.
  • Knowledge sharing is improved within the participants:
    • Small portions can be assimilated better.
  • Better engineering practices are exercised:
    • Solving big problems by dividing them in well contained, smaller problems.
    • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

  • Use the PullRequestQuantifier to quantify your PR accurately
    • Create a context profile for your repo using the context generator
    • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
    • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
    • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
  • Change your engineering behaviors
    • For PRs that fall outside of the desired spectrum, review the details and check if:
      • Your PR could be split in smaller, self-contained PRs instead
      • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

  • One line was added: +1 -0
  • One line was deleted: +0 -1
  • One line was modified: +1 -1 (git diff doesn't know about modified, it will
    interpret that line like one addition plus one deletion)
  • Change percentiles: Change characteristics (addition, deletion, modification)
    of this PR in relation to all other PRs within the repository.


Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

Copy link
Contributor

@PaulHigin PaulHigin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@PaulHigin PaulHigin merged commit 36282c2 into PowerShell:master Dec 14, 2022
@adityapatwardhan
Copy link
Member

Maintainers discussed this for backport and recommend having more bake time in preview release before backporting.

@ghost
Copy link

ghost commented Apr 13, 2023

🎉v7.3.4 has been released which incorporates this pull request.:tada:

Handy links:

Copy link

@Mirza-Numan Mirza-Numan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ishu solve

adityapatwardhan pushed a commit to adityapatwardhan/PowerShell that referenced this pull request Apr 25, 2023
…owerShell#18727)

* Add Insturmentation to AmsiUtil and make the init variable readonly

* remove unwanted file

* Fix task to hex

* ingnore AsmiInit when not windows

* rename event name

* CR feedback

* the missing dot in the argument documentation because that is very very important.

* CR feedback

Co-authored-by: Jose Sua <josesua@ntdev.microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Backport-5.1-Consider Consider to backport to Windows PowerShell 5.1 due to impact Backport-7.3.x-Done CL-Engine Indicates that a PR should be marked as an engine change in the Change Log Small

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants