{"owner":"winsiderss","repo":"systeminformer","hasSkills":true,"totalSkillsCount":4,"totalTokensCount":1159,"categories":["anthropic-skill","plugin-manifest"],"hasMcp":false,"mcpConfig":null,"found":["tools/CustomBuildTool/.vscode/settings.json","tools/thirdparty/SymCrypt/README.md","tools/CustomBuildTool/Properties/launchSettings.json","tools/CustomBuildTool/NativeMethods.json"],"skills":{"tools/CustomBuildTool/.vscode/settings.json":"{\n    \"dotnet.defaultSolution\": \"CustomBuildTool.sln\"\n}","tools/thirdparty/SymCrypt/README.md":"# Introduction\nSymCrypt is the core cryptographic function library currently used by Windows.\n\n## History\nThe library was started in late 2006 with the first sources committed in Feb 2007.\nInitially the goal was limited to implement symmetric cryptographic operations, hence the name.\nStarting with Windows 8, it has been the primary crypto library for symmetric algorithms.\n\nIn 2015 we started the work of adding asymmetric algorithms to SymCrypt. Since the 1703 release of Windows 10,\nSymCrypt has been the primary crypto library for all algorithms in Windows.\n\n## Goals\nLike any engineering project, SymCrypt is a compromise between conflicting requirements:\n- Provide safe implementations of the cryptographic algorithms needed by Microsoft products.\n- Run on all CPU architectures supported by Windows.\n- Good performance.\n- Minimize maintenance cost.\n- Support FIPS 140 certification of products using SymCrypt.\n- Provide high assurance in the proper functionality of the library.\n\n# Cloning the Repo\nIn some of our Linux modules, SymCrypt uses [Jitterentropy](https://github.com/smuellerDD/jitterentropy-library)\nas a source of FIPS-certifiable entropy. To build these modules, you will need to ensure that the\njitterentropy-library submodule is also cloned. You can do this by running\n`git submodule update --init` after cloning.\n\nThe `unittest/SymCryptDependencies` submodule provides the RSA32 and msbignum implementations which are used as\nbenchmarks in the unit tests when compiled on Windows. Due to licensing restrictions, we cannot release these\nlibraries publicly, so this submodule will only be cloneable by Microsoft employees with access to our private\nAzure DevOps repository. If you are external to Microsoft, you can ignore this submodule. It is only used in\nthe unit tests and does not change the behavior of the SymCrypt product code.\n\n# Building\nThe easiest way to get started building SymCrypt is to use the Python build script, `scripts/build.py`. You\ncan run it with the `--help` argument to get help about which arguments are required and what each one does. For\ndetailed build instructions, including alternative ways to build, see [BUILD.md](BUILD.md).\n\n# Testing\nThe SymCrypt unit test runs extensive functional tests on the SymCrypt library. On Windows it also compares results\nagainst on other implementations such as the Windows APIs CNG and CAPI, and the older crypto libraries rsa32 and\nmsbignum, if they are available. It also provides detailed performance information.\n\nAfter a successful build, you can use the `scripts/test.py` helper script to run the unit tests.\n\n# Versioning and Servicing\nAs of version 101.0.0, SymCrypt uses the version scheme defined by the\n[Semantic Versioning 2.0.0](https://semver.org/spec/v2.0.0.html) specification. This means:\n\n- Major version changes introduce ABI and/or API breaking changes (including behavior changes)\n- Minor version changes introduce backwards compatible additional functionality or improvements, and/or bug fixes\n- Patch version changes introduce backwards compatible bug fixes\n\nThe initial open source release started at version 100 for compatibility with our previous\ninternal versioning scheme.\n\nRegarding servicing, our strong recommendation is that distro vendors and application developers regularly\nupdate to the latest version of SymCrypt and SymCrypt engine for both security fixes and \nfunctionality/performance improvements. We take care to maintain a stable API and ABI for SymCrypt and have\na suite of strong regression tests, and staying on the current version prevents the need for complex\nand potential riskier backports.\n\n# Security Bugs\nIf you believe you have found a problem that affects the security of this code, please do **NOT** create an issue\nor pull request, but instead email your comments to secure@microsoft.com. See [SECURITY.md](SECURITY.md) for more info.\n\n# Contribute\nWe love to receive comments and suggestions. Unfortunately we cannot accept external code contributions except in\nspecific circumstances from vetted partners with whom we have a pre-arranged agreement.\nCryptographic code is considered highly sensitive by many of our large customers.\nWe have some very big customers who put great value in the assurance of the crypto code used in their organization.\nBy restricting the coding to a handful of employees we can greatly reduce the (perceived) risk of malicious contributions.\n\nThis project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).\nFor more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or\ncontact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.\n\n\n","tools/CustomBuildTool/Properties/launchSettings.json":"{\n  \"profiles\": {\n    \"CustomBuildTool\": {\n      \"commandName\": \"Project\",\n      \"commandLineArgs\": \"-build-debug\"\n    },\n    \"Container (Dockerfile)\": {\n      \"commandName\": \"Docker\",\n      \"commandLineArgs\": \"-build-debug\"\n    }\n  }\n}","tools/CustomBuildTool/NativeMethods.json":"{\n  \"$schema\": \"https://aka.ms/CsWin32.schema.json\",\n  \"emitSingleFile\": true,\n  \"public\": true,\n  \"useSafeHandles\": true,\n  \"wideCharOnly\": true,\n  \"friendlyOverloads\": {\n    \"enabled\": false,\n    \"includePointerOverloads\": false\n  },\n  \"allowMarshaling\": false,\n  \"comInterop\": {\n    \"preserveSigMethods\": [ \"*\" ],\n    \"useComSourceGenerators\": true\n  },\n  \"className\": \"PInvoke\"\n}"},"files":{"tools/CustomBuildTool/.vscode/settings.json":"{\n    \"dotnet.defaultSolution\": \"CustomBuildTool.sln\"\n}","tools/thirdparty/SymCrypt/README.md":"# Introduction\nSymCrypt is the core cryptographic function library currently used by Windows.\n\n## History\nThe library was started in late 2006 with the first sources committed in Feb 2007.\nInitially the goal was limited to implement symmetric cryptographic operations, hence the name.\nStarting with Windows 8, it has been the primary crypto library for symmetric algorithms.\n\nIn 2015 we started the work of adding asymmetric algorithms to SymCrypt. Since the 1703 release of Windows 10,\nSymCrypt has been the primary crypto library for all algorithms in Windows.\n\n## Goals\nLike any engineering project, SymCrypt is a compromise between conflicting requirements:\n- Provide safe implementations of the cryptographic algorithms needed by Microsoft products.\n- Run on all CPU architectures supported by Windows.\n- Good performance.\n- Minimize maintenance cost.\n- Support FIPS 140 certification of products using SymCrypt.\n- Provide high assurance in the proper functionality of the library.\n\n# Cloning the Repo\nIn some of our Linux modules, SymCrypt uses [Jitterentropy](https://github.com/smuellerDD/jitterentropy-library)\nas a source of FIPS-certifiable entropy. To build these modules, you will need to ensure that the\njitterentropy-library submodule is also cloned. You can do this by running\n`git submodule update --init` after cloning.\n\nThe `unittest/SymCryptDependencies` submodule provides the RSA32 and msbignum implementations which are used as\nbenchmarks in the unit tests when compiled on Windows. Due to licensing restrictions, we cannot release these\nlibraries publicly, so this submodule will only be cloneable by Microsoft employees with access to our private\nAzure DevOps repository. If you are external to Microsoft, you can ignore this submodule. It is only used in\nthe unit tests and does not change the behavior of the SymCrypt product code.\n\n# Building\nThe easiest way to get started building SymCrypt is to use the Python build script, `scripts/build.py`. You\ncan run it with the `--help` argument to get help about which arguments are required and what each one does. For\ndetailed build instructions, including alternative ways to build, see [BUILD.md](BUILD.md).\n\n# Testing\nThe SymCrypt unit test runs extensive functional tests on the SymCrypt library. On Windows it also compares results\nagainst on other implementations such as the Windows APIs CNG and CAPI, and the older crypto libraries rsa32 and\nmsbignum, if they are available. It also provides detailed performance information.\n\nAfter a successful build, you can use the `scripts/test.py` helper script to run the unit tests.\n\n# Versioning and Servicing\nAs of version 101.0.0, SymCrypt uses the version scheme defined by the\n[Semantic Versioning 2.0.0](https://semver.org/spec/v2.0.0.html) specification. This means:\n\n- Major version changes introduce ABI and/or API breaking changes (including behavior changes)\n- Minor version changes introduce backwards compatible additional functionality or improvements, and/or bug fixes\n- Patch version changes introduce backwards compatible bug fixes\n\nThe initial open source release started at version 100 for compatibility with our previous\ninternal versioning scheme.\n\nRegarding servicing, our strong recommendation is that distro vendors and application developers regularly\nupdate to the latest version of SymCrypt and SymCrypt engine for both security fixes and \nfunctionality/performance improvements. We take care to maintain a stable API and ABI for SymCrypt and have\na suite of strong regression tests, and staying on the current version prevents the need for complex\nand potential riskier backports.\n\n# Security Bugs\nIf you believe you have found a problem that affects the security of this code, please do **NOT** create an issue\nor pull request, but instead email your comments to secure@microsoft.com. See [SECURITY.md](SECURITY.md) for more info.\n\n# Contribute\nWe love to receive comments and suggestions. Unfortunately we cannot accept external code contributions except in\nspecific circumstances from vetted partners with whom we have a pre-arranged agreement.\nCryptographic code is considered highly sensitive by many of our large customers.\nWe have some very big customers who put great value in the assurance of the crypto code used in their organization.\nBy restricting the coding to a handful of employees we can greatly reduce the (perceived) risk of malicious contributions.\n\nThis project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).\nFor more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or\ncontact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.\n\n\n","tools/CustomBuildTool/Properties/launchSettings.json":"{\n  \"profiles\": {\n    \"CustomBuildTool\": {\n      \"commandName\": \"Project\",\n      \"commandLineArgs\": \"-build-debug\"\n    },\n    \"Container (Dockerfile)\": {\n      \"commandName\": \"Docker\",\n      \"commandLineArgs\": \"-build-debug\"\n    }\n  }\n}","tools/CustomBuildTool/NativeMethods.json":"{\n  \"$schema\": \"https://aka.ms/CsWin32.schema.json\",\n  \"emitSingleFile\": true,\n  \"public\": true,\n  \"useSafeHandles\": true,\n  \"wideCharOnly\": true,\n  \"friendlyOverloads\": {\n    \"enabled\": false,\n    \"includePointerOverloads\": false\n  },\n  \"allowMarshaling\": false,\n  \"comInterop\": {\n    \"preserveSigMethods\": [ \"*\" ],\n    \"useComSourceGenerators\": true\n  },\n  \"className\": \"PInvoke\"\n}"},"items":[{"name":"settings.json","path":"tools/CustomBuildTool/.vscode/settings.json","rawUrl":"https://raw.githubusercontent.com/winsiderss/systeminformer/HEAD/tools/CustomBuildTool/.vscode/settings.json","title":".vscode Skill","category":"anthropic-skill","format":"json","content":"{\n    \"dotnet.defaultSolution\": \"CustomBuildTool.sln\"\n}","frontmatter":{"dotnet.defaultSolution":"CustomBuildTool.sln"},"isInternal":false,"tokens":16,"sizeBytes":55},{"name":"NativeMethods.json","path":"tools/CustomBuildTool/NativeMethods.json","rawUrl":"https://raw.githubusercontent.com/winsiderss/systeminformer/HEAD/tools/CustomBuildTool/NativeMethods.json","title":"CustomBuildTool Skill","category":"anthropic-skill","format":"json","content":"{\n  \"$schema\": \"https://aka.ms/CsWin32.schema.json\",\n  \"emitSingleFile\": true,\n  \"public\": true,\n  \"useSafeHandles\": true,\n  \"wideCharOnly\": true,\n  \"friendlyOverloads\": {\n    \"enabled\": false,\n    \"includePointerOverloads\": false\n  },\n  \"allowMarshaling\": false,\n  \"comInterop\": {\n    \"preserveSigMethods\": [ \"*\" ],\n    \"useComSourceGenerators\": true\n  },\n  \"className\": \"PInvoke\"\n}","frontmatter":{"$schema":"https://aka.ms/CsWin32.schema.json","emitSingleFile":true,"public":true,"useSafeHandles":true,"wideCharOnly":true,"friendlyOverloads":{"enabled":false,"includePointerOverloads":false},"allowMarshaling":false,"comInterop":{"preserveSigMethods":["*"],"useComSourceGenerators":true},"className":"PInvoke"},"isInternal":false,"tokens":115,"sizeBytes":383},{"name":"launchSettings.json","path":"tools/CustomBuildTool/Properties/launchSettings.json","rawUrl":"https://raw.githubusercontent.com/winsiderss/systeminformer/HEAD/tools/CustomBuildTool/Properties/launchSettings.json","title":"Properties Skill","category":"anthropic-skill","format":"json","content":"{\n  \"profiles\": {\n    \"CustomBuildTool\": {\n      \"commandName\": \"Project\",\n      \"commandLineArgs\": \"-build-debug\"\n    },\n    \"Container (Dockerfile)\": {\n      \"commandName\": \"Docker\",\n      \"commandLineArgs\": \"-build-debug\"\n    }\n  }\n}","frontmatter":{"profiles":{"CustomBuildTool":{"commandName":"Project","commandLineArgs":"-build-debug"},"Container (Dockerfile)":{"commandName":"Docker","commandLineArgs":"-build-debug"}}},"isInternal":false,"tokens":66,"sizeBytes":236},{"name":"README.md","path":"tools/thirdparty/SymCrypt/README.md","rawUrl":"https://raw.githubusercontent.com/winsiderss/systeminformer/HEAD/tools/thirdparty/SymCrypt/README.md","title":"SymCrypt Documentation","category":"plugin-manifest","format":"markdown","content":"# Introduction\nSymCrypt is the core cryptographic function library currently used by Windows.\n\n## History\nThe library was started in late 2006 with the first sources committed in Feb 2007.\nInitially the goal was limited to implement symmetric cryptographic operations, hence the name.\nStarting with Windows 8, it has been the primary crypto library for symmetric algorithms.\n\nIn 2015 we started the work of adding asymmetric algorithms to SymCrypt. Since the 1703 release of Windows 10,\nSymCrypt has been the primary crypto library for all algorithms in Windows.\n\n## Goals\nLike any engineering project, SymCrypt is a compromise between conflicting requirements:\n- Provide safe implementations of the cryptographic algorithms needed by Microsoft products.\n- Run on all CPU architectures supported by Windows.\n- Good performance.\n- Minimize maintenance cost.\n- Support FIPS 140 certification of products using SymCrypt.\n- Provide high assurance in the proper functionality of the library.\n\n# Cloning the Repo\nIn some of our Linux modules, SymCrypt uses [Jitterentropy](https://github.com/smuellerDD/jitterentropy-library)\nas a source of FIPS-certifiable entropy. To build these modules, you will need to ensure that the\njitterentropy-library submodule is also cloned. You can do this by running\n`git submodule update --init` after cloning.\n\nThe `unittest/SymCryptDependencies` submodule provides the RSA32 and msbignum implementations which are used as\nbenchmarks in the unit tests when compiled on Windows. Due to licensing restrictions, we cannot release these\nlibraries publicly, so this submodule will only be cloneable by Microsoft employees with access to our private\nAzure DevOps repository. If you are external to Microsoft, you can ignore this submodule. It is only used in\nthe unit tests and does not change the behavior of the SymCrypt product code.\n\n# Building\nThe easiest way to get started building SymCrypt is to use the Python build script, `scripts/build.py`. You\ncan run it with the `--help` argument to get help about which arguments are required and what each one does. For\ndetailed build instructions, including alternative ways to build, see [BUILD.md](BUILD.md).\n\n# Testing\nThe SymCrypt unit test runs extensive functional tests on the SymCrypt library. On Windows it also compares results\nagainst on other implementations such as the Windows APIs CNG and CAPI, and the older crypto libraries rsa32 and\nmsbignum, if they are available. It also provides detailed performance information.\n\nAfter a successful build, you can use the `scripts/test.py` helper script to run the unit tests.\n\n# Versioning and Servicing\nAs of version 101.0.0, SymCrypt uses the version scheme defined by the\n[Semantic Versioning 2.0.0](https://semver.org/spec/v2.0.0.html) specification. This means:\n\n- Major version changes introduce ABI and/or API breaking changes (including behavior changes)\n- Minor version changes introduce backwards compatible additional functionality or improvements, and/or bug fixes\n- Patch version changes introduce backwards compatible bug fixes\n\nThe initial open source release started at version 100 for compatibility with our previous\ninternal versioning scheme.\n\nRegarding servicing, our strong recommendation is that distro vendors and application developers regularly\nupdate to the latest version of SymCrypt and SymCrypt engine for both security fixes and \nfunctionality/performance improvements. We take care to maintain a stable API and ABI for SymCrypt and have\na suite of strong regression tests, and staying on the current version prevents the need for complex\nand potential riskier backports.\n\n# Security Bugs\nIf you believe you have found a problem that affects the security of this code, please do **NOT** create an issue\nor pull request, but instead email your comments to secure@microsoft.com. See [SECURITY.md](SECURITY.md) for more info.\n\n# Contribute\nWe love to receive comments and suggestions. Unfortunately we cannot accept external code contributions except in\nspecific circumstances from vetted partners with whom we have a pre-arranged agreement.\nCryptographic code is considered highly sensitive by many of our large customers.\nWe have some very big customers who put great value in the assurance of the crypto code used in their organization.\nBy restricting the coding to a handful of employees we can greatly reduce the (perceived) risk of malicious contributions.\n\nThis project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).\nFor more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or\ncontact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.\n\n\n","isInternal":false,"tokens":962,"sizeBytes":4756}],"systemPromptSnippet":"<yakaai_skills repo=\"winsiderss/systeminformer\">\n<!-- File: tools/CustomBuildTool/.vscode/settings.json (Tokens: ~16 | Category: anthropic-skill) -->\n{\n    \"dotnet.defaultSolution\": \"CustomBuildTool.sln\"\n}\n\n<!-- File: tools/CustomBuildTool/NativeMethods.json (Tokens: ~115 | Category: anthropic-skill) -->\n{\n  \"$schema\": \"https://aka.ms/CsWin32.schema.json\",\n  \"emitSingleFile\": true,\n  \"public\": true,\n  \"useSafeHandles\": true,\n  \"wideCharOnly\": true,\n  \"friendlyOverloads\": {\n    \"enabled\": false,\n    \"includePointerOverloads\": false\n  },\n  \"allowMarshaling\": false,\n  \"comInterop\": {\n    \"preserveSigMethods\": [ \"*\" ],\n    \"useComSourceGenerators\": true\n  },\n  \"className\": \"PInvoke\"\n}\n\n<!-- File: tools/CustomBuildTool/Properties/launchSettings.json (Tokens: ~66 | Category: anthropic-skill) -->\n{\n  \"profiles\": {\n    \"CustomBuildTool\": {\n      \"commandName\": \"Project\",\n      \"commandLineArgs\": \"-build-debug\"\n    },\n    \"Container (Dockerfile)\": {\n      \"commandName\": \"Docker\",\n      \"commandLineArgs\": \"-build-debug\"\n    }\n  }\n}\n\n<!-- File: tools/thirdparty/SymCrypt/README.md (Tokens: ~962 | Category: plugin-manifest) -->\n# Introduction\nSymCrypt is the core cryptographic function library currently used by Windows.\n\n## History\nThe library was started in late 2006 with the first sources committed in Feb 2007.\nInitially the goal was limited to implement symmetric cryptographic operations, hence the name.\nStarting with Windows 8, it has been the primary crypto library for symmetric algorithms.\n\nIn 2015 we started the work of adding asymmetric algorithms to SymCrypt. Since the 1703 release of Windows 10,\nSymCrypt has been the primary crypto library for all algorithms in Windows.\n\n## Goals\nLike any engineering project, SymCrypt is a compromise between conflicting requirements:\n- Provide safe implementations of the cryptographic algorithms needed by Microsoft products.\n- Run on all CPU architectures supported by Windows.\n- Good performance.\n- Minimize maintenance cost.\n- Support FIPS 140 certification of products using SymCrypt.\n- Provide high assurance in the proper functionality of the library.\n\n# Cloning the Repo\nIn some of our Linux modules, SymCrypt uses [Jitterentropy](https://github.com/smuellerDD/jitterentropy-library)\nas a source of FIPS-certifiable entropy. To build these modules, you will need to ensure that the\njitterentropy-library submodule is also cloned. You can do this by running\n`git submodule update --init` after cloning.\n\nThe `unittest/SymCryptDependencies` submodule provides the RSA32 and msbignum implementations which are used as\nbenchmarks in the unit tests when compiled on Windows. Due to licensing restrictions, we cannot release these\nlibraries publicly, so this submodule will only be cloneable by Microsoft employees with access to our private\nAzure DevOps repository. If you are external to Microsoft, you can ignore this submodule. It is only used in\nthe unit tests and does not change the behavior of the SymCrypt product code.\n\n# Building\nThe easiest way to get started building SymCrypt is to use the Python build script, `scripts/build.py`. You\ncan run it with the `--help` argument to get help about which arguments are required and what each one does. For\ndetailed build instructions, including alternative ways to build, see [BUILD.md](BUILD.md).\n\n# Testing\nThe SymCrypt unit test runs extensive functional tests on the SymCrypt library. On Windows it also compares results\nagainst on other implementations such as the Windows APIs CNG and CAPI, and the older crypto libraries rsa32 and\nmsbignum, if they are available. It also provides detailed performance information.\n\nAfter a successful build, you can use the `scripts/test.py` helper script to run the unit tests.\n\n# Versioning and Servicing\nAs of version 101.0.0, SymCrypt uses the version scheme defined by the\n[Semantic Versioning 2.0.0](https://semver.org/spec/v2.0.0.html) specification. This means:\n\n- Major version changes introduce ABI and/or API breaking changes (including behavior changes)\n- Minor version changes introduce backwards compatible additional functionality or improvements, and/or bug fixes\n- Patch version changes introduce backwards compatible bug fixes\n\nThe initial open source release started at version 100 for compatibility with our previous\ninternal versioning scheme.\n\nRegarding servicing, our strong recommendation is that distro vendors and application developers regularly\nupdate to the latest version of SymCrypt and SymCrypt engine for both security fixes and \nfunctionality/performance improvements. We take care to maintain a stable API and ABI for SymCrypt and have\na suite of strong regression tests, and staying on the current version prevents the need for complex\nand potential riskier backports.\n\n# Security Bugs\nIf you believe you have found a problem that affects the security of this code, please do **NOT** create an issue\nor pull request, but instead email your comments to secure@microsoft.com. See [SECURITY.md](SECURITY.md) for more info.\n\n# Contribute\nWe love to receive comments and suggestions. Unfortunately we cannot accept external code contributions except in\nspecific circumstances from vetted partners with whom we have a pre-arranged agreement.\nCryptographic code is considered highly sensitive by many of our large customers.\nWe have some very big customers who put great value in the assurance of the crypto code used in their organization.\nBy restricting the coding to a handful of employees we can greatly reduce the (perceived) risk of malicious contributions.\n\nThis project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).\nFor more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or\ncontact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.\n</yakaai_skills>"}