Skip to content

Commit f6060d7

Browse files
rebelinuxrebelinux
authored
Merge pull request #214 from AsBuiltReport/dev
v0.9.6 public release
2 parents 1da781d + 7f84d8e commit f6060d7

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

48 files changed

+921
-440
lines changed

‎.github/workflows/Release.yml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ on:
66

77
jobs:
88
publish-to-gallery:
9-
runs-on: windows-2019
9+
runs-on: windows-2022
1010
steps:
1111
- uses: actions/checkout@v4
1212
- name: Set PSRepository to Trusted for PowerShell Gallery

‎AsBuiltReport.Microsoft.AD.psd1‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@
1212
RootModule = 'AsBuiltReport.Microsoft.AD.psm1'
1313

1414
# Version number of this module.
15-
ModuleVersion = '0.9.5'
15+
ModuleVersion = '0.9.6'
1616

1717
# Supported PSEditions
1818
# CompatiblePSEditions = @()
@@ -66,11 +66,11 @@
6666
},
6767
@{
6868
ModuleName = 'Diagrammer.Microsoft.AD';
69-
ModuleVersion = '0.2.15'
69+
ModuleVersion = '0.2.17'
7070
},
7171
@{
7272
ModuleName = 'Diagrammer.Core';
73-
ModuleVersion = '0.2.26'
73+
ModuleVersion = '0.2.27'
7474
}
7575

7676
)

‎CHANGELOG.md‎

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,29 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
77

88
##### This project is community maintained and has no sponsorship from Microsoft, its employees or any of its affiliates.
99

10+
## [0.9.6] - 2025-07-23
11+
12+
### Added
13+
14+
- Add System Center Configuration Manager (MEM) information
15+
16+
### Changed
17+
18+
- Update module version to 0.9.6
19+
- Enhance execution time tracking in Get-AbrADDomainObject function
20+
- Enhance output message in Invoke-AsBuiltReport function
21+
- Upgrade Diagrammer.Core module to version `0.2.27`.
22+
- Upgrade Diagrammer.Microsoft.AD module to version `0.2.17`.
23+
- Refactor output object initialization to use ArrayList for improved performance and memory management across multiple scripts.
24+
- Updated instances of output object accumulation to utilize the Add method instead of the += operator, enhancing efficiency in data handling.
25+
- Refine section descriptions across multiple PowerShell scripts for clarity and consistency.
26+
- Updated wording to enhance readability and provide more precise information about the content of each section to better reflect the information presented.
27+
28+
### Fixed
29+
30+
- Fix property names in software object initialization for consistency and clarity (Installed Software section)
31+
- Fix [#210](https://github.com/AsBuiltReport/AsBuiltReport.Microsoft.AD/issues/210)
32+
1033
## [0.9.5] - 2025-05-10
1134

1235
### Added

‎CODE_OF_CONDUCT.md‎

Lines changed: 128 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,128 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
We as members, contributors, and leaders pledge to make participation in our
6+
community a harassment-free experience for everyone, regardless of age, body
7+
size, visible or invisible disability, ethnicity, sex characteristics, gender
8+
identity and expression, level of experience, education, socio-economic status,
9+
nationality, personal appearance, race, religion, or sexual identity
10+
and orientation.
11+
12+
We pledge to act and interact in ways that contribute to an open, welcoming,
13+
diverse, inclusive, and healthy community.
14+
15+
## Our Standards
16+
17+
Examples of behavior that contributes to a positive environment for our
18+
community include:
19+
20+
* Demonstrating empathy and kindness toward other people
21+
* Being respectful of differing opinions, viewpoints, and experiences
22+
* Giving and gracefully accepting constructive feedback
23+
* Accepting responsibility and apologizing to those affected by our mistakes,
24+
and learning from the experience
25+
* Focusing on what is best not just for us as individuals, but for the
26+
overall community
27+
28+
Examples of unacceptable behavior include:
29+
30+
* The use of sexualized language or imagery, and sexual attention or
31+
advances of any kind
32+
* Trolling, insulting or derogatory comments, and personal or political attacks
33+
* Public or private harassment
34+
* Publishing others' private information, such as a physical or email
35+
address, without their explicit permission
36+
* Other conduct which could reasonably be considered inappropriate in a
37+
professional setting
38+
39+
## Enforcement Responsibilities
40+
41+
Community leaders are responsible for clarifying and enforcing our standards of
42+
acceptable behavior and will take appropriate and fair corrective action in
43+
response to any behavior that they deem inappropriate, threatening, offensive,
44+
or harmful.
45+
46+
Community leaders have the right and responsibility to remove, edit, or reject
47+
comments, commits, code, wiki edits, issues, and other contributions that are
48+
not aligned to this Code of Conduct, and will communicate reasons for moderation
49+
decisions when appropriate.
50+
51+
## Scope
52+
53+
This Code of Conduct applies within all community spaces, and also applies when
54+
an individual is officially representing the community in public spaces.
55+
Examples of representing our community include using an official e-mail address,
56+
posting via an official social media account, or acting as an appointed
57+
representative at an online or offline event.
58+
59+
## Enforcement
60+
61+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
62+
reported to the community leaders responsible for enforcement at
63+
rebelinux@gmail.com.
64+
All complaints will be reviewed and investigated promptly and fairly.
65+
66+
All community leaders are obligated to respect the privacy and security of the
67+
reporter of any incident.
68+
69+
## Enforcement Guidelines
70+
71+
Community leaders will follow these Community Impact Guidelines in determining
72+
the consequences for any action they deem in violation of this Code of Conduct:
73+
74+
### 1. Correction
75+
76+
**Community Impact**: Use of inappropriate language or other behavior deemed
77+
unprofessional or unwelcome in the community.
78+
79+
**Consequence**: A private, written warning from community leaders, providing
80+
clarity around the nature of the violation and an explanation of why the
81+
behavior was inappropriate. A public apology may be requested.
82+
83+
### 2. Warning
84+
85+
**Community Impact**: A violation through a single incident or series
86+
of actions.
87+
88+
**Consequence**: A warning with consequences for continued behavior. No
89+
interaction with the people involved, including unsolicited interaction with
90+
those enforcing the Code of Conduct, for a specified period of time. This
91+
includes avoiding interactions in community spaces as well as external channels
92+
like social media. Violating these terms may lead to a temporary or
93+
permanent ban.
94+
95+
### 3. Temporary Ban
96+
97+
**Community Impact**: A serious violation of community standards, including
98+
sustained inappropriate behavior.
99+
100+
**Consequence**: A temporary ban from any sort of interaction or public
101+
communication with the community for a specified period of time. No public or
102+
private interaction with the people involved, including unsolicited interaction
103+
with those enforcing the Code of Conduct, is allowed during this period.
104+
Violating these terms may lead to a permanent ban.
105+
106+
### 4. Permanent Ban
107+
108+
**Community Impact**: Demonstrating a pattern of violation of community
109+
standards, including sustained inappropriate behavior, harassment of an
110+
individual, or aggression toward or disparagement of classes of individuals.
111+
112+
**Consequence**: A permanent ban from any sort of public interaction within
113+
the community.
114+
115+
## Attribution
116+
117+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118+
version 2.0, available at
119+
https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
120+
121+
Community Impact Guidelines were inspired by [Mozilla's code of conduct
122+
enforcement ladder](https://github.com/mozilla/diversity).
123+
124+
[homepage]: https://www.contributor-covenant.org
125+
126+
For answers to common questions about this code of conduct, see the FAQ at
127+
https://www.contributor-covenant.org/faq. Translations are available at
128+
https://www.contributor-covenant.org/translations.

‎CONTRIBUTING.md‎

Lines changed: 142 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,142 @@
1+
# Contributing to this project
2+
3+
Please take a moment to review this document in order to make the contribution
4+
process easy and effective for everyone involved.
5+
6+
Following these guidelines helps to communicate that you respect the time of
7+
the developers managing and developing this open source project. In return,
8+
they should reciprocate that respect in addressing your issue or assessing
9+
patches and features.
10+
11+
12+
## Using the issue tracker
13+
14+
The issue tracker is the preferred channel for [bug reports](#bugs),
15+
[features requests](#features) and [submitting pull
16+
requests](#pull-requests), but please respect the following restrictions:
17+
18+
* Please **do not** use the issue tracker for personal support requests (use
19+
[Stack Overflow](http://stackoverflow.com) or Veeam Forum).
20+
21+
* Please **do not** derail or troll issues. Keep the discussion on topic and
22+
respect the opinions of others.
23+
24+
25+
<a name="bugs"></a>
26+
## Bug reports
27+
28+
A bug is a _demonstrable problem_ that is caused by the code in the repository.
29+
Good bug reports are extremely helpful - thank you!
30+
31+
Guidelines for bug reports:
32+
33+
1. **Use the GitHub issue search** &mdash; check if the issue has already been
34+
reported.
35+
36+
2. **Check if the issue has been fixed** &mdash; try to reproduce it using the
37+
latest `master` or development branch in the repository.
38+
39+
3. **Isolate the problem** &mdash; create a [reduced test
40+
case](http://css-tricks.com/reduced-test-cases/) and a live example.AsBuiltReport.Microsoft.AD
41+
42+
A good bug report shouldn't leave others needing to chase you up for more
43+
information. Please try to be as detailed as possible in your report. What is
44+
your environment? What steps will reproduce the issue? What browser(s) and OS
45+
experience the problem? What would you expect to be the outcome? All these
46+
details will help people to fix any potential bugs.
47+
48+
Example:
49+
50+
> Short and descriptive example bug report title
51+
>
52+
> A summary of the issue and the browser/OS environment in which it occurs. If
53+
> suitable, include the steps required to reproduce the bug.
54+
>
55+
> 1. This is the first step
56+
> 2. This is the second step
57+
> 3. Further steps, etc.
58+
>
59+
> `<url>` - a link to the reduced test case
60+
>
61+
> Any other information you want to share that is relevant to the issue being
62+
> reported. This might include the lines of code that you have identified as
63+
> causing the bug, and potential solutions (and your opinions on their
64+
> merits).
65+
66+
67+
<a name="features"></a>
68+
## Feature requests
69+
70+
Feature requests are welcome. But take a moment to find out whether your idea
71+
fits with the scope and aims of the project. It's up to *you* to make a strong
72+
case to convince the project's developers of the merits of this feature. Please
73+
provide as much detail and context as possible.
74+
75+
76+
<a name="pull-requests"></a>
77+
## Pull requests
78+
79+
Good pull requests - patches, improvements, new features - are a fantastic
80+
help. They should remain focused in scope and avoid containing unrelated
81+
commits.
82+
83+
**Please ask first** before embarking on any significant pull request (e.g.
84+
implementing features, refactoring code, porting to a different language),
85+
otherwise you risk spending a lot of time working on something that the
86+
project's developers might not want to merge into the project.
87+
88+
Please adhere to the coding conventions used throughout a project (indentation,
89+
accurate comments, etc.) and any other requirements (such as test coverage).
90+
91+
Follow this process if you'd like your work considered for inclusion in the
92+
project:
93+
94+
1. [Fork](http://help.github.com/fork-a-repo/) the project, clone your fork,
95+
and configure the remotes:
96+
97+
```bash
98+
# Clone your fork of the repo into the current directory
99+
git clone https://github.com/<your-username>/AsBuiltReport.Microsoft.AD
100+
# Navigate to the newly cloned directory
101+
cd AsBuiltReport.Microsoft.AD
102+
# Assign the original repo to a remote called "upstream"
103+
git remote add upstream https://github.com/AsBuiltReport/AsBuiltReport.Microsoft.AD
104+
```
105+
106+
2. If you cloned a while ago, get the latest changes from upstream:
107+
108+
```bash
109+
git checkout <dev-branch>
110+
git pull upstream <dev-branch>
111+
```
112+
113+
3. Create a new topic branch (off the main project development branch) to
114+
contain your feature, change, or fix:
115+
116+
```bash
117+
git checkout -b <topic-branch-name>
118+
```
119+
120+
4. Commit your changes in logical chunks. Please adhere to these [git commit
121+
message guidelines](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
122+
or your code is unlikely be merged into the main project. Use Git's
123+
[interactive rebase](https://help.github.com/articles/interactive-rebase)
124+
feature to tidy up your commits before making them public.
125+
126+
5. Locally merge (or rebase) the upstream development branch into your topic branch:
127+
128+
```bash
129+
git pull [--rebase] upstream <dev-branch>
130+
```
131+
132+
6. Push your topic branch up to your fork:
133+
134+
```bash
135+
git push origin <topic-branch-name>
136+
```
137+
138+
7. [Open a Pull Request](https://help.github.com/articles/using-pull-requests/)
139+
with a clear title and description.
140+
141+
**IMPORTANT**: By submitting a patch, you agree to allow the project owner to
142+
license your work under the same license as that used by the project.

‎SECURITY.md‎

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
Thanks for helping make AsBuiltReport.Veeam.VBR safe for everyone.
2+
3+
## Security
4+
5+
AsBuiltReport takes the security of our software products and services seriously, including all of the open source code repositories managed through our GitHub organizations, such as [AsBuiltReport](https://github.com/AsBuiltReport).
6+
7+
Even though "open source repositories are outside of the scope of bug bounty program and therefore not eligible for bounty rewards", we will ensure that your finding gets passed along to the appropriate maintainers for remediation.
8+
9+
## Reporting Security Issues
10+
11+
If you believe you have found a security vulnerability in any GitHub-owned repository, please report it to us through coordinated disclosure.
12+
13+
**Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.**
14+
15+
Instead, please send an email to rebelinux@gmail.com.
16+
17+
Please include as much of the information listed below as you can to help us better understand and resolve the issue:
18+
19+
* The type of issue (e.g., buffer overflow, SQL injection, or cross-site scripting)
20+
* Full paths of source file(s) related to the manifestation of the issue
21+
* The location of the affected source code (tag/branch/commit or direct URL)
22+
* Any special configuration required to reproduce the issue
23+
* Step-by-step instructions to reproduce the issue
24+
* Proof-of-concept or exploit code (if possible)
25+
* Impact of the issue, including how an attacker might exploit the issue
26+
27+
This information will help us triage your report more quickly.

‎Src/Private/Get-AbrADCAAIA.ps1‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ function Get-AbrADCAAIA {
55
.DESCRIPTION
66
77
.NOTES
8-
Version: 0.9.5
8+
Version: 0.9.6
99
Author: Jonathan Colon
1010
Twitter: @jcolonfzenpr
1111
Github: rebelinux
@@ -29,13 +29,13 @@ function Get-AbrADCAAIA {
2929
process {
3030
if ($CA) {
3131
Section -Style Heading3 "Authority Information Access (AIA)" {
32-
Paragraph "The following section provides the Certification Authority Information Access details."
32+
Paragraph "This section details the Certification Authority's Authority Information Access (AIA) configuration."
3333
BlankLine
3434
try {
35-
$OutObj = @()
3635
Write-PScriboMessage -Message "Collecting AD CA Authority Information Access information on $($CA.Name)."
3736
$AIA = Get-AuthorityInformationAccess -CertificationAuthority $CA
3837
foreach ($URI in $AIA.URI) {
38+
$OutObj = [System.Collections.ArrayList]::new()
3939
try {
4040
$inObj = [ordered] @{
4141
'Reg URI' = $URI.RegURI
@@ -45,7 +45,7 @@ function Get-AbrADCAAIA {
4545
'Include To Extension' = $URI.IncludeToExtension
4646
'OCSP' = $URI.OCSP
4747
}
48-
$OutObj = [pscustomobject](ConvertTo-HashToYN $inObj)
48+
$OutObj.Add([pscustomobject](ConvertTo-HashToYN $inObj)) | Out-Null
4949

5050
$TableParams = @{
5151
Name = "Authority Information Access - $($CA.Name)"

0 commit comments

Comments
 (0)