issue_owner_repo listlengths 2 2 | issue_body stringlengths 0 261k ⌀ | issue_title stringlengths 1 925 | issue_comments_url stringlengths 56 81 | issue_comments_count int64 0 2.5k | issue_created_at stringlengths 20 20 | issue_updated_at stringlengths 20 20 | issue_html_url stringlengths 37 62 | issue_github_id int64 387k 2.46B | issue_number int64 1 127k |
|---|---|---|---|---|---|---|---|---|---|
[
"chakra-core",
"ChakraCore"
] | At a minimum it could simply pull the current commit's metadata and report commit hash and commit date.
| ch.exe needs --version | https://api.github.com/repos/chakra-core/ChakraCore/issues/109/comments | 27 | 2016-01-14T21:11:22Z | 2017-02-09T23:52:31Z | https://github.com/chakra-core/ChakraCore/issues/109 | 126,748,968 | 109 |
[
"chakra-core",
"ChakraCore"
] | Many Windows applications such as AutoCAD have long embedded the Windows Script Host to allow scripting in VBScript, JavaScript, and other installed Windows Script languages, and there are a lot of system administration scripts written in JavaScript to run under WSH.
But Chakra has never been a Windows Script script engine since it was introduced in Internet Explorer 9. As a result, while IE 9-11 and Edge and now ChakraCore have leaped ahead in JavaScript support to ECMAScript 6th Edition, other Windows apps have to either adopt the new JSRT API which only came out with Chakra for IE 11, or stay stuck with JScript 5.8 and ECMAScript 3rd Edition. And adopting JSRT means either extra work to indefinitely support two embedded script subsystems, or dropping support for VBScript, perl, and other Windows Script languages.
So, I suggest the above in the title - make ChakraCore a Windows Script engine, either through internal code or a thin wrapper around JSRT that implements [the IActiveScript API](https://msdn.microsoft.com/library/xawadt95%28v=vs.94%29.aspx), and perhaps even give it the same COM ProgID as JScript 5.8 with a higher version number, so that apps can get access to Chakra when they ask for JScript.
This is big, and perhaps too big for a single work item, but I hope it can be considered nonetheless.
| Plug in ChakraCore to the Windows Script host so it/Chakra can replace JScript 5.8 [suggestion] | https://api.github.com/repos/chakra-core/ChakraCore/issues/108/comments | 11 | 2016-01-14T20:30:17Z | 2021-05-13T08:34:52Z | https://github.com/chakra-core/ChakraCore/issues/108 | 126,741,859 | 108 |
[
"chakra-core",
"ChakraCore"
] | Per ECMA262:
24.1.2.1ArrayBuffer( length )#
ArrayBuffer called with argument length performs the following steps:
1.If NewTarget is undefined, throw a TypeError exception.
2.Let numberLength be ? ToNumber(length).
3.Let byteLength be ToLength(numberLength).
4.If SameValueZero(numberLength, byteLength) is false, throw a RangeError exception.
5.Return ? AllocateArrayBuffer(NewTarget, byteLength).
When length == undefined, step 2 returns NaN while step 3 returns 0, therefore step 4 should throw a RangeError.
This behavior is not implemented in ChakraCore.
| "new ArrayBuffer()" should throw a RangeError | https://api.github.com/repos/chakra-core/ChakraCore/issues/105/comments | 9 | 2016-01-14T19:40:44Z | 2016-11-05T23:09:41Z | https://github.com/chakra-core/ChakraCore/issues/105 | 126,731,755 | 105 |
[
"chakra-core",
"ChakraCore"
] | Do you plan to implement `JsVariantToValue` and `JsValueToVariant` methods? In general, will there be added any possibility to embed custom .NET objects into JavaScript engine?
| Support of `JsVariantToValue` and `JsValueToVariant` methods | https://api.github.com/repos/chakra-core/ChakraCore/issues/104/comments | 3 | 2016-01-14T18:51:14Z | 2016-01-18T14:27:19Z | https://github.com/chakra-core/ChakraCore/issues/104 | 126,721,463 | 104 |
[
"chakra-core",
"ChakraCore"
] | Code of Conduct | https://api.github.com/repos/chakra-core/ChakraCore/issues/103/comments | 3 | 2016-01-14T17:41:02Z | 2016-01-20T18:07:19Z | https://github.com/chakra-core/ChakraCore/issues/103 | 126,708,437 | 103 | |
[
"chakra-core",
"ChakraCore"
] | 这三个文件：
\lib\common\Memory\PageAllocator.h
\lib\Runtime\Library\ArgumentsObject.h
\lib\Runtime\Library\MathLibrary.cpp
warning C4819: 该文件包含不能在当前代码页(936)中表示的字符。请将该文件保存为 Unicode 格式以防止数据丢失
需要修改上述三个文件的编码才能正确编译。
| Compiler Error under Windows 7 SP1 32-bit Chinese Simplified | https://api.github.com/repos/chakra-core/ChakraCore/issues/99/comments | 5 | 2016-01-14T07:09:32Z | 2016-02-02T19:44:30Z | https://github.com/chakra-core/ChakraCore/issues/99 | 126,595,002 | 99 |
[
"chakra-core",
"ChakraCore"
] | I was able to observe this in Edge 25.10586.0.0:
/[\ud800-\ud805]+/u.exec("\u{10000}\ud801\ud802") should return ["\ud801\ud802] but instead returns["\ud800"], which is the first half of "\u{10000}".
The spec requires the input string to be interpreted as a sequence of code points, i.e. surrogate pairs to be combined. So matching the lead surrogate of "\u{10000}" is incorrect.
A bit more reduced would be:
/\ud800+/u.exec("\u{10000}") should return null, but returns ["\ud800"] instead.
| [RegExp] Unicode-mode RegExp incorrectly matches lone surrogates | https://api.github.com/repos/chakra-core/ChakraCore/issues/98/comments | 2 | 2016-01-14T07:02:07Z | 2019-06-07T18:36:28Z | https://github.com/chakra-core/ChakraCore/issues/98 | 126,593,656 | 98 |
[
"chakra-core",
"ChakraCore"
] | I tried the x64-debug ch.exe to execute the following javascript code, but nothing was output. The expected output should be "Infinity".
``` javascript
function fact(n) {
if (n < 2)
{
return 1;
}
else
{
return n * fact(n-1);
}
}
print(fact(1000));
```
| A simple javascript factorial function does not produce expected results | https://api.github.com/repos/chakra-core/ChakraCore/issues/95/comments | 10 | 2016-01-14T03:02:22Z | 2016-01-14T19:48:02Z | https://github.com/chakra-core/ChakraCore/issues/95 | 126,567,556 | 95 |
[
"chakra-core",
"ChakraCore"
] | Re #90, it would be nice to allow ch.exe to work with Release builds of ChakraCore.dll.
| Enable ch.exe to work with Release builds of ChakraCore.dll | https://api.github.com/repos/chakra-core/ChakraCore/issues/93/comments | 1 | 2016-01-14T02:39:02Z | 2016-01-14T21:51:40Z | https://github.com/chakra-core/ChakraCore/issues/93 | 126,565,267 | 93 |
[
"chakra-core",
"ChakraCore"
] | Built x64_release Using Visual Studio 2015 Update 1. When running ch.exe from the command prompt it says:
```
Try 'ch.exe -?' for help
```
When issuing 'ch.exe -?', program reports error:
```
The binary chakracore.dll is not test enabled, please use chakracore.dll from debug/test flavor
```
| Building x64_release: ch.exe doesn't do anything | https://api.github.com/repos/chakra-core/ChakraCore/issues/90/comments | 7 | 2016-01-14T01:38:46Z | 2016-01-14T21:50:50Z | https://github.com/chakra-core/ChakraCore/issues/90 | 126,557,137 | 90 |
[
"chakra-core",
"ChakraCore"
] | Since Internet Explorer use Chakra, and in Internet Explorer one can new-up an ActiveXObject instance to access safe-COM objects, does that mean that this open source version of Chakra can do the same? If so, does that mean I can execute that type of code from within version of node that's bound to Chakra?
I want to be able to execute code that looks like this:
var xmlHttp = new ActiveXObject("Microsoft.XMLHTTP");
| ActiveX | https://api.github.com/repos/chakra-core/ChakraCore/issues/88/comments | 3 | 2016-01-14T01:24:51Z | 2016-01-14T19:17:45Z | https://github.com/chakra-core/ChakraCore/issues/88 | 126,555,420 | 88 |
[
"chakra-core",
"ChakraCore"
] | I didn't see this already so I hope it isn't a duplicate.
I also didn't see it in the roadmap.
I read the quick-start guide on embedding ChakraCore, but following this guidance will make it hard to keep an embedded version up to date.
https://github.com/Microsoft/ChakraCore/wiki/Embedding-ChakraCore
A better solution would be if MS created a NuGet package for ChakraCore and auto-published it from its build server.
---
# Maintainers' Update
@dilijev (added 2016-04-26 / last updated 2016-01-31):
Wiki: https://github.com/Microsoft/ChakraCore/wiki/NuGet-Packages
NuGet feed: https://www.nuget.org/packages/Microsoft.ChakraCore
MyGet feed: https://www.myget.org/feed/chakracore-preview/package/nuget/Microsoft.ChakraCore
## Work Items
- [x] Use build system to create and publish daily builds as NuGet packages to MyGet.org
- [x] Add link to MyGet feed to README and/or Wiki (@liminzhu) (#1253)
- [x] Create a NuGet.org feed to publish our official releases (once they are available)
- [x] _When available:_ Add NuGet.org feed link to README and/or Wiki (@liminzhu)
- [x] _When release 1.2 is finalized:_ Publish ChakraCore version 1.2 to NuGet.org
- [x] Include build number in preview package special version strings
- Format for preview packages: `Microsoft.ChakraCore.<major>.<minor>.<patch>-preview-<build1>-<build2>` (e.g. `Microsoft.ChakraCore.1.3.0-preview-00008-12345`). Commit hash is, as always, encoded in binary metadata.
- ~~Preview builds of multiple branches: e.g. `release/*` and `master`~~ (Infrastructure now exists but there's no compelling reason to publish preview builds of multiple release branches -- patch updates to already-released minor versions like 1.2 and 1.3 will be extremely minor so there's nothing meaningful to preview.)
- [x] Reorganize package layout to enable Visual C++ projects to take a dependency on native NuGet packages and automatically integrate the ChakraCore binaries into a project. (see https://docs.nuget.org/consume/support-for-native-projects) (#2266 by @pre10der89)
- [x] NuGet package spec (nuspec) consumable by .NET projects (#2266 by @pre10der89)
- [x] Publish preview package for .NET for validation (https://github.com/Microsoft/ChakraCore/issues/85#issuecomment-276537774)
- [x] Publish preview package for Native for validation (https://github.com/Microsoft/ChakraCore/issues/85#issuecomment-276537774)
- [x] Publish an updated NuGet package for Native projects which supports NuGet automation (as above). (See #2435)
- [x] Publish NuGet for .NET projects. (See #2345)
## Follow-up Items
Moved follow-up work items to #2578
/cc @digitalinfinity @boingoing | ChakraCore NuGet package | https://api.github.com/repos/chakra-core/ChakraCore/issues/85/comments | 26 | 2016-01-14T00:12:06Z | 2017-02-22T22:10:43Z | https://github.com/chakra-core/ChakraCore/issues/85 | 126,546,239 | 85 |
[
"chakra-core",
"ChakraCore"
] | http://up-for-grabs.net/ has a curated list of tasks which are simple enough to help the community get involved in open source projects.
Refer to instructions here for how to get our repo added to the list. https://github.com/up-for-grabs/up-for-grabs.net#add-your-project
Thanks to @RichiCoder1 on Gitter for suggesting this.
| Add ChakraCore to http://up-for-grabs.net/ | https://api.github.com/repos/chakra-core/ChakraCore/issues/83/comments | 6 | 2016-01-13T23:16:47Z | 2016-01-14T05:39:52Z | https://github.com/chakra-core/ChakraCore/issues/83 | 126,538,976 | 83 |
[
"chakra-core",
"ChakraCore"
] | Hi,
There's a small typo in the C++ code example at: https://github.com/Microsoft/ChakraCore/wiki/Embedding-ChakraCore
"CharkaCore.h" should be "ChakraCore.h".
Was just wondering why my VS2015 couldn't find any classes, functions etc. :)
Regards and many thanks for the Engine :+1:
| Small typo in Embedding Chakra Wiki: "CharkaCore.h" | https://api.github.com/repos/chakra-core/ChakraCore/issues/80/comments | 1 | 2016-01-13T22:23:29Z | 2016-03-22T21:42:29Z | https://github.com/chakra-core/ChakraCore/issues/80 | 126,530,046 | 80 |
[
"chakra-core",
"ChakraCore"
] | Build solutions is working great to produce ChakraCore.dll, but will there ever be an option to create a Java library so we can use this JS engine in our Java applications? Would love to see a portable version of Chakra (one that runs on OS X, Linux, etc.), similar to V8 and Mozilla's JS engines
| ChakraCore.jar | https://api.github.com/repos/chakra-core/ChakraCore/issues/79/comments | 9 | 2016-01-13T22:17:38Z | 2017-12-16T00:18:12Z | https://github.com/chakra-core/ChakraCore/issues/79 | 126,529,020 | 79 |
[
"chakra-core",
"ChakraCore"
] | Except where required for performance/API reasons the c++ code should follow the [C++ Core Guidelines](https://isocpp.github.io/CppCoreGuidelines/) and use the [Guidelines Support Library](https://github.com/Microsoft/GSL) to ensure safer code and reduce complexity and security risks
Related:[C++11 Language features allowed in Chrome](https://chromium-cpp.appspot.com/)
| C++ code should follow the C++ Core Guidelines | https://api.github.com/repos/chakra-core/ChakraCore/issues/78/comments | 10 | 2016-01-13T20:43:50Z | 2016-01-15T18:27:47Z | https://github.com/chakra-core/ChakraCore/issues/78 | 126,508,918 | 78 |
[
"chakra-core",
"ChakraCore"
] | There is no reason for Microsoft to align itself with the institution of MIT. The [ISC License](https://opensource.org/licenses/ISC) is a functionally equivalent license approved by the Free Software Foundation and is compatible with Node core's license. The ISC License is the preferred license of OpenBSD, among other projects.
| Change license to ISC | https://api.github.com/repos/chakra-core/ChakraCore/issues/76/comments | 13 | 2016-01-13T19:43:58Z | 2016-01-14T20:42:34Z | https://github.com/chakra-core/ChakraCore/issues/76 | 126,497,503 | 76 |
[
"chakra-core",
"ChakraCore"
] | In page https://github.com/Microsoft/ChakraCore/wiki/Building-ChakraCore, there is a typo in below step. (thtough->through)
Clone ChakraCore thtough git clone https://github.com/Microsoft/ChakraCore.git
| Typo in wiki page build chakracore | https://api.github.com/repos/chakra-core/ChakraCore/issues/75/comments | 1 | 2016-01-13T19:14:24Z | 2016-03-22T21:42:03Z | https://github.com/chakra-core/ChakraCore/issues/75 | 126,491,309 | 75 |
[
"chakra-core",
"ChakraCore"
] | Visiting http://dotnet-ci.cloudapp.net/job/Microsoft_ChakraCore/job/Microsoft_ChakraCore_x86_release/ or any of the other links results in a 404. Also, the images in the Build Status area are missing.
| Build URLs in README.md are broken | https://api.github.com/repos/chakra-core/ChakraCore/issues/70/comments | 4 | 2016-01-13T18:22:55Z | 2016-01-13T18:38:48Z | https://github.com/chakra-core/ChakraCore/issues/70 | 126,481,406 | 70 |
[
"chakra-core",
"ChakraCore"
] | I was looking over the code of conduct, out of curiousity and noticed some odd language:
> We will prioritize marginalized people's safety over marginalized people's comfort.
I assume this is a typo, based on https://github.com/todogroup/opencodeofconduct/blob/gh-pages/index.md:
> Our open source community prioritizes marginalized people’s safety over privileged people’s comfort.
cheers
| Typo in CODE_OF_CONDUCT.md | https://api.github.com/repos/chakra-core/ChakraCore/issues/66/comments | 1 | 2016-01-13T18:14:38Z | 2016-03-22T21:41:35Z | https://github.com/chakra-core/ChakraCore/issues/66 | 126,479,721 | 66 |
[
"chakra-core",
"ChakraCore"
] | See Luke Wagner's reasoning [here](http://discourse.wicg.io/t/request-for-comments-switching-resizing-heaps-in-asm-js/641/22).
"While this feature works without issue or slowdown in FF/Edge, the change-heap function interferes with the generic closure analysis that allows V8/JSC to detect and optimize the immutability of the heap view variables [11]. In V8, this causes a drastic performance penalty (see issue 39075). If that was the end of the story, I think it'd make sense to hold out until optimizations improve (e.g., on V8 is planning to do full asm.js optimizations3). However, WebAssembly will have a simpler and more direct form of resizing6 along with cross-browser support. Due to the above V8 issue, I don't think many people are using asm.js heap resizing (ALLOW_MEMORY_GROWTH is off by default in Emscripten and recommended against), so to simplify engines, I'd like to remove support for the change-heap function from SpiderMonkey and have suggested to Chakra folks that they do the same. Of course, Emscripten can still support ALLOW_MEMORY_GROWTH by simply emitting almost-but-not-asm"
| Remove change-heap support in asm.js | https://api.github.com/repos/chakra-core/ChakraCore/issues/65/comments | 2 | 2016-01-13T17:57:02Z | 2017-06-02T02:15:36Z | https://github.com/chakra-core/ChakraCore/issues/65 | 126,476,412 | 65 |
[
"chakra-core",
"ChakraCore"
] | ChakraCore should provide APIs to debug JavaScript
| Provide JavaScript debugging support (API) in ChakraCore | https://api.github.com/repos/chakra-core/ChakraCore/issues/61/comments | 3 | 2016-01-13T00:33:41Z | 2016-06-14T21:36:29Z | https://github.com/chakra-core/ChakraCore/issues/61 | 126,311,709 | 61 |
[
"chakra-core",
"ChakraCore"
] | We probably don't need es6\es6_stable.js and friends anymore - can we remove them?
akroshg commented on Nov 30 2015
Agreed.
Should we also remove all stable flags from the .xml files?
tcare commented on Nov 30 2015
We could, but if we turn a feature off by default (e.g. due to spec change) then we would have to add them back again for that test. That has been fairly rare, so I'm ok with removing the flags.
ianwjhalliday commented on Nov 30 2015
There is still value in the idea of validating the flags so that when a new one is added we have to pay attention to its default to prevent accidentally introducing features too early. However, as we saw previously with the async feature snafu earlier, the current test does not make it obvious enough for us to catch such a mistake.
I recommend that if we spend time here changing things we should take a stab at improving the test itself after reducing it down to all that is needed.
Specific improvements I'd like to see are:
- don't use `-verbose` to print out the flag information; use something like `-DumpEsFlags` instead
- currently this reliance on `-verbose` pollutes other uses of `-verbose`, like when looking at verbose bailout trace and dump
- get rid of `-es6` and `-es6all`; instead introduce `-esall` to turn on off-by-default language features
- perhaps also a `-esexperimental` to turn on all the experimental features
- beautify the flag dump information into a table showing the feature flag and its default setting (`off`, `experimental`, `on`)
I don't think we care about testing the semantics for specifying the switches multiple times (e.g. the `-es6 -es6-` test), nor do we care about seeing the current state (as opposed to the default) of each switch.
| Remove ES6 flag baselines | https://api.github.com/repos/chakra-core/ChakraCore/issues/58/comments | 1 | 2016-01-12T22:00:31Z | 2017-05-25T21:19:39Z | https://github.com/chakra-core/ChakraCore/issues/58 | 126,287,328 | 58 |
[
"chakra-core",
"ChakraCore"
] | Refactor netci.groovy to reduce code duplication. | https://api.github.com/repos/chakra-core/ChakraCore/issues/50/comments | 0 | 2016-01-12T01:52:57Z | 2016-01-22T18:23:40Z | https://github.com/chakra-core/ChakraCore/issues/50 | 126,079,228 | 50 | |
[
"chakra-core",
"ChakraCore"
] | This will make the contents of the root of our project more legible, and effectively bring the `README` into view sooner on the main page of the project.
It will require modifications to most of those scripts and to the `netci.groovy` script itself.
The build checks will break on the PR for this change because the Jenkins task definitions will be out of sync with the actual locations of the files, so we will need to accept the change despite the breaks and quickly react to breaks following that change.
| Move jenkins.*.* scripts into a jenkins directory off the project root. | https://api.github.com/repos/chakra-core/ChakraCore/issues/48/comments | 11 | 2016-01-12T01:23:04Z | 2016-03-11T06:51:56Z | https://github.com/chakra-core/ChakraCore/issues/48 | 126,075,983 | 48 |
[
"chakra-core",
"ChakraCore"
] | We are adding a bunch of new configurations with #18 and #42. With this, I'm wondering if we can include slow tests in some configuration? Right now seems like we are arbitrarily excluding a number of tests.
| Include slow tests in some configuration | https://api.github.com/repos/chakra-core/ChakraCore/issues/46/comments | 6 | 2016-01-11T22:41:40Z | 2016-01-16T01:24:04Z | https://github.com/chakra-core/ChakraCore/issues/46 | 126,054,067 | 46 |
[
"chakra-core",
"ChakraCore"
] | Adapted from test262
https://github.com/tc39/test262/blob/master/test/language/statements/class/name-binding/in-extends-expression-assigned.js
```
var x = (class x extends x {}); // expected: ReferenceError, actual: TypeError
```
The error seen looks like the following:
```
TypeError: Function is not a constructor
at Global code (E:\dev\debugging\class\repro.js:1:1)
```
Details about the expected behavior can be found in [ECMAScript 2015 14.5.14](http://www.ecma-international.org/ecma-262/6.0/index.html#sec-runtime-semantics-classdefinitionevaluation).
**UPDATE:** See [ES 2016 14.5.14](https://tc39.github.io/ecma262/2016/#sec-runtime-semantics-classdefinitionevaluation) and [ES 2017 14.5.13](https://tc39.github.io/ecma262/#sec-runtime-semantics-bindingclassdeclarationevaluation).
There is a scoping issue with the extends clause that is causing x to appear to be of an invalid type, rather than causing an error because of the attempt to reference the type which is being defined.
The following should also produce a `ReferenceError` when `eval("x")` is evaluated as the `extends` clause.
```
var x = (class x extends eval("x") {}); // expected: ReferenceError, actual: TypeError
```
See bug [4310932](https://microsoft.visualstudio.com/web/wi.aspx?pcguid=cb55739e-4afe-46a3-970f-1b49d8ee7564&id=4310932)
| Class name in extends clause should be ReferenceError | https://api.github.com/repos/chakra-core/ChakraCore/issues/36/comments | 5 | 2016-01-07T22:54:16Z | 2016-07-05T21:52:15Z | https://github.com/chakra-core/ChakraCore/issues/36 | 125,503,580 | 36 |
[
"chakra-core",
"ChakraCore"
] | Chakra implements [LCG](https://en.wikipedia.org/wiki/Linear_congruential_generator) algorithm for Math.random. Firefox has switched to [XorShift128+](http://vigna.di.unimi.it/ftp/papers/xorshiftplus.pdf). Chrome used to implement MWC1616 and they have switched to xorshift128+ as well. This is a request to update Chakra Math.random implementation to use xorshift128+. Xorshift128+ is an improvement over LCG even though it still is not cryptographically secure. The same algorithm across all browsers serves well on interoperability story.
http://jandemooij.nl/blog/2015/11/30/testing-math-random-crushing-the-browser/
https://bugzilla.mozilla.org/show_bug.cgi?id=322529
http://v8project.blogspot.com/2015/12/theres-mathrandom-and-then-theres.html
| Update Math.random to use xorshift128+ | https://api.github.com/repos/chakra-core/ChakraCore/issues/31/comments | 5 | 2016-01-07T17:17:09Z | 2016-02-02T18:00:24Z | https://github.com/chakra-core/ChakraCore/issues/31 | 125,441,818 | 31 |
[
"chakra-core",
"ChakraCore"
] | As per ES spec [22.2.4.1](http://tc39.github.io/ecma262/#sec-typedarray)
We should be loading super from the current function [[prototype]] slot. Instead we always assume super is %TypedArray%. Similarly, we do not pass new.target into %TypedArray% since we do not properly call Construct abstract operation. We need some refactoring in TypedArray constructors to support this behavior.
``` javascript
Uint8Array.__proto__ = Math.sin
new Uint8Array(64);
```
Expected: TypeError
Actual: No Error
Duplicate OS bug [50260238](https://microsoft.visualstudio.com/web/wi.aspx?pcguid=cb55739e-4afe-46a3-970f-1b49d8ee7564&id=5026038)
| TypedArray constructors do not perform proper super-call to %TypedArray% | https://api.github.com/repos/chakra-core/ChakraCore/issues/29/comments | 2 | 2016-01-07T01:24:40Z | 2016-11-05T23:15:35Z | https://github.com/chakra-core/ChakraCore/issues/29 | 125,301,531 | 29 |
[
"chakra-core",
"ChakraCore"
] | Test case
``` javascript
var f = arguments => arguments; // shouldn't be a syntax error
print(f(0)); // should print 0
```
Similar behavior for _eval_ in place of _arguments_
This also affects _yield_. Looks like the bug is because we are treating arrow parameters as always in strict mode.
Refer duplicate OS bug [5042642](https://microsoft.visualstudio.com/web/wi.aspx?pcguid=cb55739e-4afe-46a3-970f-1b49d8ee7564&id=5042642)
| arguments and eval should be allowed as parameter names of arrow functions in non-strict mode | https://api.github.com/repos/chakra-core/ChakraCore/issues/28/comments | 1 | 2016-01-07T01:24:00Z | 2016-02-02T19:40:12Z | https://github.com/chakra-core/ChakraCore/issues/28 | 125,301,456 | 28 |
[
"chakra-core",
"ChakraCore"
] | Following should parse
``` javascript
var x = 10;
({x = 10} = {});
```
Actual: Syntax error
Refer OS bug [3887967](https://microsoft.visualstudio.com/web/wi.aspx?pcguid=cb55739e-4afe-46a3-970f-1b49d8ee7564&id=3887967)
| Object destructuring issue: Initializer on shorthand should not throw syntax error | https://api.github.com/repos/chakra-core/ChakraCore/issues/27/comments | 5 | 2016-01-07T01:22:26Z | 2016-02-25T23:12:33Z | https://github.com/chakra-core/ChakraCore/issues/27 | 125,301,295 | 27 |
[
"chakra-core",
"ChakraCore"
] | Lowerer::Lower ([Lower.cpp](https://github.com/Microsoft/ChakraCore/blob/master/lib/Backend/Lower.cpp)) doesn't generate any fast path for loading super and super constructor. It just delegates to C++ helper. Generating a simple fast path will improve the performance of jit code for constructors with super call.
``` C++
case Js::OpCode::LdSuper:
instrPrev = m_lowererMD.LowerLdSuper(instr, IR::HelperLdSuper);
break;
case Js::OpCode::LdSuperCtor:
instrPrev = m_lowererMD.LowerLdSuper(instr, IR::HelperLdSuperCtor);
break;
```
Refer OS bug [5244353](https://microsoft.visualstudio.com/web/wi.aspx?pcguid=cb55739e-4afe-46a3-970f-1b49d8ee7564&id=5244353)
| Generate fast path for both LdSuper and LdSuperCtor | https://api.github.com/repos/chakra-core/ChakraCore/issues/26/comments | 0 | 2016-01-07T01:21:20Z | 2016-02-25T23:32:53Z | https://github.com/chakra-core/ChakraCore/issues/26 | 125,301,163 | 26 |
[
"chakra-core",
"ChakraCore"
] | Following test case is failing in [kangax](https://kangax.github.io/compat-table/es6/)
``` javascript
var passed = false;
new function f() {
passed = (new.target === f);
}();
try {
Function("new.target = function(){};");
} catch(e) {
return passed;
}
```
| Assignment to new.target should be an early error | https://api.github.com/repos/chakra-core/ChakraCore/issues/25/comments | 3 | 2016-01-07T01:20:16Z | 2016-03-26T02:40:54Z | https://github.com/chakra-core/ChakraCore/issues/25 | 125,301,056 | 25 |
[
"chakra-core",
"ChakraCore"
] | As per exponentiation stage [3 spec](http://rwaldron.github.io/exponentiation-operator/#unary-operators) -5**2 should be an early error. This is a spec update from [September TC39 meeting](https://esdiscuss.org/topic/september-tc39-meeting-notes).
| Exponentiation operator should throw early syntax error for unary negation without parens | https://api.github.com/repos/chakra-core/ChakraCore/issues/24/comments | 2 | 2016-01-07T01:19:34Z | 2016-03-08T18:44:29Z | https://github.com/chakra-core/ChakraCore/issues/24 | 125,300,987 | 24 |
[
"chakra-core",
"ChakraCore"
] | Array.prototype.includes ([spec](https://github.com/tc39/Array.prototype.includes)) is in stage 4 of ES2016 spec. This needs to be enabled by default for ChakraCore and Edge.
This built-in is currently under -ES7Builtins flag and can be enabled through experimental flag.
Note Array.prototype.includes should be added to @@unscopables (See raw [TC39 notes](http://oksoclap.com/p/nov-17-2015))
| Enable Array.prototype.includes by default | https://api.github.com/repos/chakra-core/ChakraCore/issues/23/comments | 1 | 2016-01-07T01:19:02Z | 2016-03-10T23:16:08Z | https://github.com/chakra-core/ChakraCore/issues/23 | 125,300,925 | 23 |
[
"chakra-core",
"ChakraCore"
] | Following test should should return true.
``` javascript
var arr = [1,2,3];
var iterableObj = {
[Symbol.iterator]: ()=> {
return {
next: () => {
return {
value: arr.shift(),
done: arr.length == 0
};
}
};
}
};
var arr = new Uint8Array(iterableObj);
print(arr);
```
Expected: 1,2
Actual: TypeError
See duplicate OS bug [5027123](https://microsoft.visualstudio.com/web/wi.aspx?pcguid=cb55739e-4afe-46a3-970f-1b49d8ee7564&id=5027123)
I believe following [kangax](https://kangax.github.io/compat-table/es6/#test-typed_arrays_constructors_accept_generic_iterables) test case is dupe of this too:
``` javascript
(function(){
var constructors = [
'Int8Array',
'Uint8Array',
'Uint8ClampedArray',
'Int16Array',
'Uint16Array',
'Int32Array',
'Uint32Array',
'Float32Array',
'Float64Array'
];
for(var i = 0; i < constructors.length; i++){
var arr = new global[constructors[i]](__createIterableObject([1, 2, 3]));
if(arr.length !== 3 || arr[0] !== 1 || arr[1] !== 2 || arr[2] !== 3)return false;
}
return true;
})();
```
| Typed array constructors should accept generic iterables | https://api.github.com/repos/chakra-core/ChakraCore/issues/22/comments | 3 | 2016-01-07T01:18:06Z | 2016-02-02T16:42:54Z | https://github.com/chakra-core/ChakraCore/issues/22 | 125,300,841 | 22 |
[
"chakra-core",
"ChakraCore"
] | This is a [kangax](http://kangax.github.io/compat-table/es6/) [test case](https://kangax.github.io/compat-table/es6/#test-String.prototype_HTML_methods)
``` javascript
function foo(){
return "𐐘".toLowerCase() === "𐑀" && "𐑀".toUpperCase() === "𐐘";
}
print(foo());
```
Expected: true
Actual: false
| String.prototype.toLowerCase and String.prorotype.toUpperCase built-ins should support unicode | https://api.github.com/repos/chakra-core/ChakraCore/issues/21/comments | 1 | 2016-01-07T01:17:23Z | 2016-02-08T18:56:17Z | https://github.com/chakra-core/ChakraCore/issues/21 | 125,300,758 | 21 |
[
"chakra-core",
"ChakraCore"
] | ES [spec](http://tc39.github.io/ecma262/#sec-html-like-comments) has detailed semantics of HTML style comments.
Test case
``` javascript
print((function(){
--> A comment
<!-- Another comment
var a = 3; <!-- Another comment
return a === 3;
})());
```
Expected: true
Actual: Syntax error
| Support HTML-style comments | https://api.github.com/repos/chakra-core/ChakraCore/issues/20/comments | 0 | 2016-01-07T01:16:38Z | 2016-03-02T00:37:40Z | https://github.com/chakra-core/ChakraCore/issues/20 | 125,300,674 | 20 |
[
"chakra-core",
"ChakraCore"
] | @tcare has suggested adding an auto-code-review service via chakrabot account for this type of issue rather than blocking PRs on non-functional issues.
Details:
We don't want to block builds by having an extra check for style. What we would like to have instead is an auto code-review bot that will make comments about that sort of thing, and which the author has the freedom to ignore if necessary. Not all such style changes are worth making, and it's difficult to make a good logic for style that should always be applied.
For anything that would potentially be a build-breaking check (which would require almost unanimous agreement on the team), I would prioritize like this based on likelihood of consensus:
1. Tabs
2. Trailing whitespace
3. Blank line at end of file
4. Other style (very unlikely to get unanimous approval)
We already have some necessary style checks as build-breaking checks (where necessary pertains to environment compatibility or legal requirements):
- [EOL Check] EOL characters must be checked into git as `\n` and not `\r\n` for platform compatibility.
- [Copyright Check] The Copyright header on each file must match the header required by Microsoft legal.
---
Labeled as "Accepting PRs" because maybe the community knows of a tool we could deploy to help us with this. It might not be a change that makes it into this repo's source but it might still be helpful.
| Add auto code-review checks: tabs, trailing whitespace, etc. | https://api.github.com/repos/chakra-core/ChakraCore/issues/12/comments | 3 | 2016-01-06T19:47:47Z | 2016-05-03T21:20:47Z | https://github.com/chakra-core/ChakraCore/issues/12 | 125,248,563 | 12 |
[
"chakra-core",
"ChakraCore"
] | Include support for exceptions for files that should not contain the Microsoft copyright notice for various reasons (e.g. would be rendered in markdown, format of file doesn't support comments, included in this repo under a different license, etc.)
This should run as a separate Jenkins CI task from the already existing tasks to make it immediately clear what the issue is.
Also provide a script to easily fix up files that do not have the notice properly displayed.
| [Continuous Integration] Add check for Microsoft copyright headers in committed files | https://api.github.com/repos/chakra-core/ChakraCore/issues/11/comments | 1 | 2016-01-06T19:46:58Z | 2016-01-12T01:07:33Z | https://github.com/chakra-core/ChakraCore/issues/11 | 125,248,424 | 11 |
[
"chakra-core",
"ChakraCore"
] | Add additional build tasks which will only run once per day but will test additional scenarios.
Daily task for each of [ {x86,x64,arm} x {debug,test,release} ] which are done for every commit to master and every pull request. These tasks use Windows Server 2012 R2 + VS 2015 (the default configuration of windows build machines).
Additionally, daily tasks for [ {x86,x64} x {debug,test,release} ] running on Windows 7 with VS 2013 (our earliest supported build configuration).
| [Continuous Integration] Jenkins Daily Build Tasks | https://api.github.com/repos/chakra-core/ChakraCore/issues/10/comments | 0 | 2016-01-06T19:45:42Z | 2016-01-09T05:17:24Z | https://github.com/chakra-core/ChakraCore/issues/10 | 125,248,177 | 10 |
[
"chakra-core",
"ChakraCore"
] | Search for IR_VIEWER macro etc in the code. Make this tool work with the ch.exe binary.
| Revive IR Viewer | https://api.github.com/repos/chakra-core/ChakraCore/issues/9/comments | 1 | 2016-01-06T19:44:44Z | 2016-05-03T21:18:49Z | https://github.com/chakra-core/ChakraCore/issues/9 | 125,248,014 | 9 |
[
"chakra-core",
"ChakraCore"
] | When an OutOfMemory error occurred in ch.exe, the program crashed without logging an error message.
The exception in this particular case is thrown within the ArrayBuffer::ArrayBuffer constructor, but it is handled by code within ch.exe and it seems to be swallowed up without logging a message before the process dies.
The call stack that catches the OOM exception is here:
```
> ChakraCore.dll!ContextAPIWrapper<0,_JsErrorCode <lambda>(Js::ScriptContext *) >(RunScriptCore::__l2::_JsErrorCode <lambda>(Js::ScriptContext *) fn) Line 155 C++
ChakraCore.dll!RunScriptCore(const wchar_t * script, unsigned long sourceContext, const wchar_t * sourceUrl, bool parseOnly, void * * result) Line 2450 C++
ChakraCore.dll!JsRunScript(const wchar_t * script, unsigned long sourceContext, const wchar_t * sourceUrl, void * * result) Line 2493 C++
ch.exe!ChakraRTInterface::JsRunScript(const wchar_t * script, unsigned long sourceContext, const wchar_t * sourceUrl, void * * result) Line 178 C++
ch.exe!RunScript(const wchar_t * fileName, const wchar_t * fileContents, unsigned char * bcBuffer, wchar_t * fullPath) Line 283 C++
ch.exe!ExecuteTest(const wchar_t * fileName) Line 429 C++
ch.exe!ExecuteTestWithMemoryCheck(wchar_t * fileName) Line 462 C++
ch.exe!StaticThreadProc(void * lpParam) Line 484 C++
ucrtbased.dll!551b8968() Unknown
[Frames below may be incorrect and/or missing, no symbols loaded for ucrtbased.dll]
ucrtbased.dll!551b867b() Unknown
kernel32.dll!762338f4() Unknown
ntdll.dll!77ae56c3() Unknown
ntdll.dll!77ae568e() Unknown
```
```
catch (Js::JavascriptExceptionObject * exceptionObject)
{
scriptContext->GetThreadContext()->SetRecordedException(exceptionObject);
return JsErrorScriptException;
}
```
A useful error message might look like:
```
JavascriptError: Out of memory
at Global code (...\path\to\blah.js:2:1)
```
Try running the following test case which will eventually force an OOM (on a 32-bit process):
``` js
print("hello");
var buffer = [];
for (var i = 0; ; ++i) {
print(i);
buffer[i] = new ArrayBuffer(1<<30);
}
print("world");
```
Note: on a 64-bit process you'll just end up using up all your system's memory.
| Allocation failed silently in some AsmJs tests | https://api.github.com/repos/chakra-core/ChakraCore/issues/8/comments | 4 | 2016-01-06T19:19:49Z | 2016-02-02T19:45:00Z | https://github.com/chakra-core/ChakraCore/issues/8 | 125,242,661 | 8 |
[
"chakra-core",
"ChakraCore"
] | As per [this](http://tc39.github.io/ecma262/#sec-functiondeclarations-in-ifstatement-statement-clauses) section of ECMA spec, chakra should throw syntax error for below code, but it accepts it without errors.
``` javascript
(function() { "use strict"; if (true) function f() { } })()
```
| Chakra doesn't throw SyntaxError if function is declared in statement context | https://api.github.com/repos/chakra-core/ChakraCore/issues/7/comments | 5 | 2016-01-06T18:49:31Z | 2016-01-20T21:52:01Z | https://github.com/chakra-core/ChakraCore/issues/7 | 125,237,416 | 7 |
[
"chakra-core",
"ChakraCore"
] | Here's my reasoning:
- switches were provided for allowing disabling unstable features for engineering infrastructure and RI
- **old features are now stable and any bugs in them are not going to cause us to disable the feature**
- I cannot think of any reason else why we would want to disable a given feature
- oldest switches do not necessarily even work anymore due to future changes requiring the older changes
- e.g. let/const changed how we defer parse in a way that other features have taken a dependency on
- old unused switches are thus now useless visual cruft
Switches that I believe are reasonable to remove with no risk at this time:
- __proto__
- Map
- Set
- WeakMap
- ES6WeakSet
- DefineGetterSetter
- LetConst
- ES6Lambda
- ES6Math
- ES6Object
- ES6Number
- ES6String
Switches that I think are reasonable to remove but there might still be low risk in the feature having bugs or causing issues:
- ES6Iterators
- ES6NumericLiterals
- ES6Promise
- ES6StringTemplate
- ES6Symbol
- ES6Unscopables
| Remove oldest ES6 feature switches | https://api.github.com/repos/chakra-core/ChakraCore/issues/6/comments | 6 | 2016-01-06T18:25:10Z | 2018-02-24T03:04:54Z | https://github.com/chakra-core/ChakraCore/issues/6 | 125,233,166 | 6 |
[
"chakra-core",
"ChakraCore"
] | Looks like some state is not changed correctly on debugger detach, so when reattaching debugger after the profiling completes, the asm.js->js frame conversion still happens.
| performance tab crashes in f12 on pages with asm.js | https://api.github.com/repos/chakra-core/ChakraCore/issues/1/comments | 0 | 2016-01-05T20:05:42Z | 2016-01-09T01:15:31Z | https://github.com/chakra-core/ChakraCore/issues/1 | 125,040,301 | 1 |
[
"weidai11",
"cryptopp"
] | ### Crypto++ Issue Report
some of the static functions could have a better definition... | Poor naming convention 4 "x" n of functions | https://api.github.com/repos/weidai11/cryptopp/issues/1287/comments | 0 | 2024-08-08T20:42:30Z | 2024-08-08T20:42:30Z | https://github.com/weidai11/cryptopp/issues/1287 | 2,456,591,731 | 1,287 |
[
"weidai11",
"cryptopp"
] | Why the http://www.cryptopp.com is not accessible? | cryptopp.com is not working | https://api.github.com/repos/weidai11/cryptopp/issues/1286/comments | 0 | 2024-08-02T10:15:32Z | 2024-08-02T10:50:43Z | https://github.com/weidai11/cryptopp/issues/1286 | 2,444,633,450 | 1,286 |
[
"weidai11",
"cryptopp"
] | I see that expected assertion failure was reported at least twice:
* #1281
* #1273
Can a message be added that this test may deliberately fail an assertion to avoid users being alerted? | Can test in debug print a message that it is about to deliberately fail an assertion? | https://api.github.com/repos/weidai11/cryptopp/issues/1285/comments | 0 | 2024-08-01T11:09:41Z | 2024-08-01T11:09:41Z | https://github.com/weidai11/cryptopp/issues/1285 | 2,442,173,359 | 1,285 |
[
"weidai11",
"cryptopp"
] | This site can’t be reachedwww.cryptopp.com took too long to respond.
http://www.cryptopp.com/
For 7 days+ | (http://www.cryptopp.com/) This site can’t be reachedwww.cryptopp.com took too long to respond. | https://api.github.com/repos/weidai11/cryptopp/issues/1283/comments | 0 | 2024-07-22T08:49:03Z | 2024-07-22T12:50:31Z | https://github.com/weidai11/cryptopp/issues/1283 | 2,422,310,948 | 1,283 |
[
"weidai11",
"cryptopp"
] | HTTP and HTTPS are down for cryptopp.com and www.cryptopp.com .
| www.cryptopp.com website offline | https://api.github.com/repos/weidai11/cryptopp/issues/1282/comments | 4 | 2024-07-18T15:18:43Z | 2024-08-08T20:43:24Z | https://github.com/weidai11/cryptopp/issues/1282 | 2,416,711,797 | 1,282 |
[
"weidai11",
"cryptopp"
] | Hi, first, thank you for maintaining this great repo!
There is a problem when running `cryptest.exe v` in Windows, specifically Github windows workflows, not all assertions pass.
I've made a [fork](https://github.com/baderouaich/cryptopp-windows-ci) with windows workflow action so you guys can check it out.
### Crypto++ Issue Report
* State the operating system and version:
Github workflows
Microsoft Windows Server 2022
10.0.20348
Datacenter
* State the version of the Crypto++ library:
master (also fails with 8.9.0, 8.8.0 in a separate project)
* State how you built the library:
MSBuild Visual Studio 17 2022
using this [workflow](https://github.com/baderouaich/cryptopp-windows-ci/blob/master/.github/workflows/c-cpp.yml)
* Show a typical command line (the output of the compiler for cryptlib.cpp):
Please find the cryptest compilation result [here](https://github.com/baderouaich/cryptopp-windows-ci/actions/runs/9927861096/job/27423362901) in the `Build cyrptest Solution` step
* Show the link command (the output of the linker for libcryptopp.so or cryptest.exe):
You can fine the cryptest.exe v result [here](https://github.com/baderouaich/cryptopp-windows-ci/actions/runs/9927861096/job/27423362901) in the `Run cyrptest.exe` step
* Show the exact error message you are receiving (copy and paste it); or
* Clearly state the undesired behavior (and state the expected behavior)
31 assertions did not pass for example:
`Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\integer.cpp(4455): CryptoPP::a_times_b_mod_c`
`Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\integer.cpp(4464): CryptoPP::a_exp_b_mod_c`
`Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\misc.cpp(50): CryptoPP::BytePtr`
`Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\pwdbased.h(246): CryptoPP::PKCS5_PBKDF2_HMAC<class CryptoPP::SHA256>::DeriveKey`
and more
I can confirm that this problem only occurs on the Github windows workflows, it works fine in my windows machine.
<details>
<summary>cyrptest.exe -v output:</summary>
```text
Win32\Output\Debug\cryptest.exe v
shell: C:\Windows\system32\cmd.EXE /D /E:ON /V:OFF /S /C "CALL "{0}""
Using seed: 1720959419
Testing Settings...
passed: Your machine is little endian.
passed: Your machine has 32-bit words.
passed: Your machine has 32-bit pointers.
passed: Library version (library): 890, header version (app): 890
passed: sizeof(byte) == 1
passed: sizeof(word16) == 2
passed: sizeof(word32) == 4
passed: sizeof(word64) == 8
passed: sizeof(hword) == 2, sizeof(word) == 4, sizeof(dword) == 8
passed: cacheLineSize == 64
hasSSE2 == 1, hasSSSE3 == 1, hasSSE4.1 == 1, hasSSE4.2 == 1, hasAVX == 1, hasAVX2 == 1, hasAESNI == 1, hasCLMUL == 1, hasRDRAND == 1, hasRDSEED == 1, hasSHA == 1, isP4 == 0
Testing operating system provided nonblocking random number generator...
passed: 10240 generated bytes compressed to 10245 bytes by DEFLATE
passed: IncorporateEntropy with 128 bytes
passed: GenerateWord32 and Crop
passed: DiscardBytes with 1024 bytes
Testing RandomPool generator...
passed: 10240 generated bytes compressed to 10245 bytes by DEFLATE
passed: IncorporateEntropy with 128 bytes
passed: GenerateWord32 and Crop
passed: DiscardBytes with 1024 bytes
Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\integer.cpp(4455): CryptoPP::a_times_b_mod_c
Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\integer.cpp(4464): CryptoPP::a_exp_b_mod_c
Testing AutoSeeded RandomPool generator...
passed: 10240 generated bytes compressed to 10245 bytes by DEFLATE
passed: IncorporateEntropy with 128 bytes
passed: GenerateWord32 and Crop
passed: DiscardBytes with 1024 bytes
Testing OldRandomPool generator...
passed: 10240 generated bytes compressed to 10245 bytes by DEFLATE
passed: IncorporateEntropy with 128 bytes
passed: GenerateWord32 and Crop
passed: DiscardBytes with 1024 bytes
passed: Expected sequence from PGP-style RandomPool (circa 2007)
Testing AutoSeeded X917 generator...
passed: 10240 generated bytes compressed to 10245 bytes by DEFLATE
passed: IncorporateEntropy with 128 bytes
passed: GenerateWord32 and Crop
passed: DiscardBytes with 1024 bytes
Testing Mersenne Twister...
passed: 10240 generated bytes compressed to 10245 bytes by DEFLATE
passed: IncorporateEntropy with 128 bytes
passed: GenerateWord32 and Crop
passed: DiscardBytes with 1024 bytes
passed: Expected sequence from MT19937
Testing Padlock RNG generator...
Padlock RNG generator not available, skipping test.
Testing RDRAND generator...
passed: 10240 generated bytes compressed to 10245 bytes by DEFLATE
passed: IncorporateEntropy with 128 bytes
passed: GenerateWord32 and Crop
passed: DiscardBytes with 1024 bytes
passed: Maurer Randomness Test returned value 0.998627
Testing RDSEED generator...
passed: 10240 generated bytes compressed to 10245 bytes by DEFLATE
passed: IncorporateEntropy with 128 bytes
passed: GenerateWord32 and Crop
passed: DiscardBytes with 1024 bytes
passed: Maurer Randomness Test returned value 0.999551
Testing SecBlock...
passed: Zeroized byte array
passed: Zeroized word32 array
passed: Zeroized word64 array
passed: Assign byte
passed: Assign word32
passed: Assign word64
passed: Append byte
passed: Append word32
passed: Append word64
Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\integer.cpp(4464): CryptoPP::a_exp_b_mod_c
passed: Integer DivideByZero
passed: Integer RandomNumberNotFound
passed: Carmichael pseudo-primes
passed: Squaring operations
passed: GCD operations
passed: InverseMod operations
passed: Divide operations
passed: Power2 operations
passed: Exponentiation operations
passed: Randomize of various bit lengths
Testing Integer bit operations...
passed: Bitwise AND over 32-bits to 1024-bits
passed: Bitwise OR over 32-bits to 1024-bits
passed: Bitwise XOR over 32-bits to 1024-bits
Testing PolynomialMod2 bit operations...
passed: 1 shifted over range [0,129]
passed: 0xffffffff shifted over range [0,129]
passed: random values shifted over range [0,129]
Testing RoundUpToMultipleOf/RoundDownToMultipleOf...
passed: RoundUpToMultipleOf, byte, no overflow
passed: RoundUpToMultipleOf, byte, no overflow
passed: RoundUpToMultipleOf, byte, no overflow
passed: RoundUpToMultipleOf, byte, no overflow
passed: RoundUpToMultipleOf, byte, no overflow
passed: RoundUpToMultipleOf, byte, overflow
passed: RoundUpToMultipleOf, word16, no overflow
passed: RoundUpToMultipleOf, word16, no overflow
passed: RoundUpToMultipleOf, word16, no overflow
passed: RoundUpToMultipleOf, word16, no overflow
passed: RoundUpToMultipleOf, word16, no overflow
passed: RoundUpToMultipleOf, word16, overflow
passed: RoundUpToMultipleOf, word32, no overflow
passed: RoundUpToMultipleOf, word32, no overflow
passed: RoundUpToMultipleOf, word32, no overflow
passed: RoundUpToMultipleOf, word32, no overflow
passed: RoundUpToMultipleOf, word32, no overflow
passed: RoundUpToMultipleOf, word32, overflow
passed: RoundUpToMultipleOf, word64, no overflow
passed: RoundUpToMultipleOf, word64, no overflow
passed: RoundUpToMultipleOf, word64, no overflow
passed: RoundUpToMultipleOf, word64, no overflow
passed: RoundUpToMultipleOf, word64, no overflow
passed: RoundUpToMultipleOf, word64, overflow
Testing Huffman codes...
passed: GenerateCodeLengths
passed: HuffmanDecoder decode
Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\misc.cpp(50): CryptoPP::BytePtr
Testing ASN.1 parser...
passed: accept BIT_STRING 030100
Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\misc.cpp(50): CryptoPP::BytePtr
passed: reject BIT_STRING 030108
passed: accept BIT_STRING 03020043
passed: reject BIT_STRING 03020843
passed: reject BIT_STRING 037F0043
passed: accept BIT_STRING 03810100
Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\misc.cpp(50): CryptoPP::BytePtr
passed: reject BIT_STRING 03810108
passed: accept BIT_STRING 0381020043
passed: reject BIT_STRING 0381020843
passed: reject BIT_STRING 0381FF0043
passed: accept BIT_STRING 038200020043
passed: reject BIT_STRING 038200020843
passed: reject BIT_STRING 0382FFFF0043
passed: accept BIT_STRING 03830000020043
passed: reject BIT_STRING 03830000020843
passed: reject BIT_STRING 0383FFFFFF0043
passed: accept BIT_STRING 0384000000020043
passed: reject BIT_STRING 0384000000020843
passed: reject BIT_STRING 0384FFFFFFFF0043
Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\misc.cpp(50): CryptoPP::BytePtr
Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\misc.cpp(50): CryptoPP::BytePtr
passed: accept OCTET_STRING 0400
passed: accept OCTET_STRING 040143
passed: reject OCTET_STRING 040243
passed: reject OCTET_STRING 047F43
passed: accept OCTET_STRING 048100
passed: accept OCTET_STRING 04810143
passed: reject OCTET_STRING 04810243
passed: reject OCTET_STRING 0481FF43
Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\misc.cpp(50): CryptoPP::BytePtr
passed: accept OCTET_STRING 04820000
passed: accept OCTET_STRING 0482000143
passed: reject OCTET_STRING 0482000243
passed: reject OCTET_STRING 0482FFFF43
Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\misc.cpp(50): CryptoPP::BytePtr
passed: accept OCTET_STRING 0483000000
passed: accept OCTET_STRING 048300000143
passed: reject OCTET_STRING 048300000243
passed: reject OCTET_STRING 0483FFFFFF43
passed: accept OCTET_STRING 048400000000
Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\misc.h(444): CryptoPP::BytePtr
passed: accept OCTET_STRING 04840000000143
passed: reject OCTET_STRING 04840000000243
passed: reject OCTET_STRING 0484FFFFFFFF43
passed: accept UTF8_STRING 0C00
Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\misc.h(444): CryptoPP::BytePtr
passed: accept UTF8_STRING 0C0143
passed: reject UTF8_STRING 0C0243
passed: reject UTF8_STRING 0C7F43
passed: accept UTF8_STRING 0C8100
Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\misc.h(444): CryptoPP::BytePtr
passed: accept UTF8_STRING 0C810143
passed: reject UTF8_STRING 0C810243
passed: reject UTF8_STRING 0C81FF43
passed: accept UTF8_STRING 0C820000
Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\misc.h(444): CryptoPP::BytePtr
passed: accept UTF8_STRING 0C82000143
passed: reject UTF8_STRING 0C82000243
passed: reject UTF8_STRING 0C82FFFF43
passed: accept UTF8_STRING 0C83000000
Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\misc.h(444): CryptoPP::BytePtr
passed: accept UTF8_STRING 0C8300000143
passed: reject UTF8_STRING 0C8300000243
passed: reject UTF8_STRING 0C83FFFFFF43
passed: accept UTF8_STRING 0C8400000000
Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\misc.h(444): CryptoPP::BytePtr
passed: accept UTF8_STRING 0C840000000143
passed: reject UTF8_STRING 0C840000000243
passed: reject UTF8_STRING 0C84FFFFFFFF43
passed: accept PRINTABLE_STRING 1300
Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\misc.h(444): CryptoPP::BytePtr
passed: accept PRINTABLE_STRING 130143
passed: reject PRINTABLE_STRING 130243
passed: reject PRINTABLE_STRING 137F43
Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\misc.h(444): CryptoPP::BytePtr
passed: accept PRINTABLE_STRING 138100
passed: accept PRINTABLE_STRING 13810143
passed: reject PRINTABLE_STRING 13810243
passed: reject PRINTABLE_STRING 1381FF43
passed: accept PRINTABLE_STRING 13820000
Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\misc.h(444): CryptoPP::BytePtr
passed: accept PRINTABLE_STRING 1382000143
passed: reject PRINTABLE_STRING 1382000243
passed: reject PRINTABLE_STRING 1382FFFF43
Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\misc.h(444): CryptoPP::BytePtr
passed: accept PRINTABLE_STRING 1383000000
passed: accept PRINTABLE_STRING 138300000143
passed: reject PRINTABLE_STRING 138300000243
passed: reject PRINTABLE_STRING 1383FFFFFF43
Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\misc.h(444): CryptoPP::BytePtr
passed: accept PRINTABLE_STRING 138400000000
passed: accept PRINTABLE_STRING 13840000000143
passed: reject PRINTABLE_STRING 13840000000243
passed: reject PRINTABLE_STRING 1384FFFFFFFF43
Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\misc.h(444): CryptoPP::BytePtr
passed: accept IA5_STRING 1600
passed: accept IA5_STRING 160143
passed: reject IA5_STRING 160243
passed: reject IA5_STRING 167F43
passed: accept IA5_STRING 168100
Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\misc.h(444): CryptoPP::BytePtr
passed: accept IA5_STRING 16810143
passed: reject IA5_STRING 16810243
passed: reject IA5_STRING 1681FF43
passed: accept IA5_STRING 16820000
Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\misc.h(444): CryptoPP::BytePtr
passed: accept IA5_STRING 1682000143
passed: reject IA5_STRING 1682000243
passed: reject IA5_STRING 1682FFFF43
passed: accept IA5_STRING 1683000000
Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\misc.h(444): CryptoPP::BytePtr
passed: accept IA5_STRING 168300000143
passed: reject IA5_STRING 168300000243
passed: reject IA5_STRING 1683FFFFFF43
passed: accept IA5_STRING 168400000000
passed: accept IA5_STRING 16840000000143
passed: reject IA5_STRING 16840000000243
passed: reject IA5_STRING 1684FFFFFFFF43
passed: reject INTEGER 0200
passed: accept INTEGER 020143
passed: reject INTEGER 020243
passed: reject INTEGER 027F43
passed: reject INTEGER 028100
passed: accept INTEGER 02810143
passed: reject INTEGER 02810243
passed: reject INTEGER 0281FF43
passed: reject INTEGER 02820000
passed: accept INTEGER 0282000143
passed: reject INTEGER 0282000243
passed: reject INTEGER 0282FFFF43
passed: reject INTEGER 0283000000
passed: accept INTEGER 028300000143
passed: reject INTEGER 028300000243
passed: reject INTEGER 0283FFFFFF43
passed: reject INTEGER 028400000000
passed: accept INTEGER 02840000000143
passed: reject INTEGER 02840000000243
passed: reject INTEGER 0284FFFFFFFF43
Testing ASN.1 functions...
passed DEREncodeOctetString
passed BERDecodeOctetString
passed DEREncodeTextString
passed DEREncodeTextString
passed DEREncodeDate
passed BERDecodeDate
Base64, Base64URL, Base32 and Base16 coding validation suite running...
passed: Hex Encoding
passed: Hex Decoding
passed: Base32 Encoding
passed: Base32 Decoding
passed: Base64 Encoding
passed: Base64 Decoding
passed: Base64 URL Encoding
passed: Base64 URL Decoding
Custom encoder validation running...
passed: Encode and decode
passed: 0-length message
Testing Compressors and Decompressors...
passed: filenames, filetimes and comments
passed: 64 zips and unzips
passed: 64 deflates and inflates
passed: 64 zlib decompress and compress
Information Dispersal and Secret Sharing...
passed: 64 information dispersals
passed: 64 secret sharings
Testing Default Encryptors and Decryptors...
passed: cross-platform decryption with MAC of binary file
passed: 64 default encryptions and decryptions
passed: 64 default encryptions and decryptions with MAC
passed: 64 legacy encryptions and decryptions
passed: 64 legacy encryptions and decryptions with MAC
Testing curve25519 Key Agreements...
passed 64 key agreements
passed x25519 load and save
passed x25519 encoding and decoding
passed x25519 private key byte buffer construction
passed x25519 private key Integer construction
passed x25519 public key byte buffer construction
passed x25519 public key Integer construction
passed x25519 byte buffer and Integer consistency
Testing ed25519 Signatures...
passed 64 public keys
passed 64 signatures
passed 64 verifications
passed 64 streams
passed RFC 8032 test vectors
passed RFC 5208 and 5958 key loads
CRC-32 validation suite running...
passed 00000000 ""
passed 43beb7e8 "a"
passed c2412435 "abc"
passed 7f9d1520 "message digest"
passed bd50274c "abcdefghijklmnopqrstuvwxyz"
passed d2e6c21f "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789"
passed 724aa97c "12345678901234567890123456789012345678901234567890123456789012345678901234567890"
passed 2639f4cb "123456789"
CRC-32C validation suite running...
passed 00000000 ""
passed 3043d0c1 "a"
passed b73f4b36 "abc"
passed d079bd02 "message digest"
passed 25efe69e "abcdefghijklmnopqrstuvwxyz"
passed 7dd545a2 "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789"
passed 81677a47 "12345678901234567890123456789012345678901234567890123456789012345678901234567890"
passed 839206e3 "123456789"
Adler-32 validation suite running...
passed 00000001 ""
passed 00620062 "a"
passed 024d0127 "abc"
passed 29750586 "message digest"
passed 90860b20 "abcdefghijklmnopqrstuvwxyz"
passed 8adb150c "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789"
passed 15d870f9 "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa" repeated 15625 times
MD2 validation suite running...
passed 8350e5a3e24c153df2275c9f80692773 ""
passed 32ec01ec4a6dac72c0ab96fb34c0b5d1 "a"
passed da853b0d3f88d99b30283a69e6ded6bb "abc"
passed ab4f496bfb2a530b219ff33031fe06b0 "message digest"
passed 4e8ddff3650292ab5a4108c3aa47940b "abcdefghijklmnopqrstuvwxyz"
passed da33def2a42df13975352846c30338cd "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789"
passed d5976f79d83d3a0dc9806c3c66f3efd8 "12345678901234567890123456789012345678901234567890123456789012345678901234567890"
MD4 validation suite running...
passed 31d6cfe0d16ae931b73c59d7e0c089c0 ""
passed bde52cb31de33e46245e05fbdbd6fb24 "a"
passed a448017aaf21d8525fc10ae87aa6729d "abc"
passed d9130a8164549fe818874806e1c7014b "message digest"
passed d79e1c308aa5bbcdeea8ed63df412da9 "abcdefghijklmnopqrstuvwxyz"
passed 043f8582f241db351ce627e153e7f0e4 "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789"
passed e33b4ddc9c38f2199c3e7b164fcc0536 "12345678901234567890123456789012345678901234567890123456789012345678901234567890"
MD5 validation suite running...
passed d41d8cd98f00b204e9800998ecf8427e ""
passed 0cc175b9c0f1b6a831c399e269772661 "a"
passed 900150983cd24fb0d6963f7d28e17f72 "abc"
passed f96b697d7cb7938d525a2f31aaf161d0 "message digest"
passed c3fcd3d76192e4007dfb496cca67e13b "abcdefghijklmnopqrstuvwxyz"
passed d174ab98d277d9f5a5611c2c9f419d9f "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789"
passed 57edf4a22be3c955ac49da2e2107b67a "12345678901234567890123456789012345678901234567890123456789012345678901234567890"
SHA validation suite running...
Testing MessageDigest algorithm SHA-1.
...
Testing MessageDigest algorithm SHA-224.
...
Testing MessageDigest algorithm SHA-256.
...
Testing MessageDigest algorithm SHA-384.
...
Testing MessageDigest algorithm SHA-512.
...
Tests complete. Total tests = 15. Failed tests = 0.
Keccak validation suite running...
Testing MessageDigest algorithm Keccak-224.
.......
Testing MessageDigest algorithm Keccak-256.
.......
Testing MessageDigest algorithm Keccak-384.
.......
Testing MessageDigest algorithm Keccak-512.
......................................................................................................................................................................................................................................................................
Tests complete. Total tests = 283. Failed tests = 0.
SHA-3 validation suite running...
Testing FileList algorithm SHA3 FIPS 202 collection.
Testing MessageDigest algorithm SHA3-224.
.....................................................................................................................................................................................................................................................
Testing MessageDigest algorithm SHA3-256.
.............................................................................................................................................................................................................................................
Testing MessageDigest algorithm SHA3-384.
.............................................................................................................................................................................................................
Testing MessageDigest algorithm SHA3-512.
.............................................................................................................................................................................
Tests complete. Total tests = 860. Failed tests = 0.
SHAKE validation suite running...
Testing MessageDigest algorithm SHAKE-128.
......................................................................................................................................................
Testing MessageDigest algorithm SHAKE-256.
......................................................................................................................................................
Tests complete. Total tests = 300. Failed tests = 0.
SHAKE XOF validation suite running...
passed SHAKE XOF message digests
LSH validation suite running...
Testing FileList algorithm LSH test vectors.
Testing MessageDigest algorithm LSH-224.
...................................................................................................................................................
Testing MessageDigest algorithm LSH-256.
...................................................................................................................................................
Testing MessageDigest algorithm LSH-384.
...................................................................................................................................................
Testing MessageDigest algorithm LSH-512.
...................................................................................................................................................
Testing MessageDigest algorithm LSH-512-256.
...................................................................................................................................................
Tests complete. Total tests = 735. Failed tests = 0.
Testing NIST Hash DRBGs...
passed Hash_DRBG SHA1/128/440 (COUNT=0, E=16, N=8)
passed Hash_DRBG SHA1/128/440 (COUNT=1, E=16, N=8)
passed Hash_DRBG SHA1/128/440 (C0UNT=0, E=16, N=8, A=16)
passed Hash_DRBG SHA1/128/440 (C0UNT=1, E=16, N=8, A=16)
passed Hash_DRBG SHA1/128/440 (C0UNT=0, E=16, N=8, A=0, P=16)
passed Hash_DRBG SHA1/128/440 (C0UNT=1, E=16, N=8, A=0, P=16)
passed Hash_DRBG SHA1/128/440 (C0UNT=0, E=16, N=8, A=16, P=16)
passed Hash_DRBG SHA1/128/440 (C0UNT=1, E=16, N=8, A=16, P=16)
passed Hash_DRBG SHA256/128/440 (C0UNT=0, E=32, N=16, A=32, P=32)
passed Hash_DRBG SHA256/128/440 (C0UNT=1, E=32, N=16, A=32, P=32)
passed Hash_DRBG SHA512/256/888 (C0UNT=0, E=32, N=16, A=32, P=32)
passed Hash_DRBG SHA512/256/888 (C0UNT=1, E=32, N=16, A=32, P=32)
Testing NIST HMAC DRBGs...
passed HMAC_DRBG SHA1/128/440 (COUNT=0, E=16, N=8)
passed HMAC_DRBG SHA1/128/440 (COUNT=1, E=16, N=8)
passed HMAC_DRBG SHA1/128/440 (COUNT=0, E=16, N=8, A=16)
passed HMAC_DRBG SHA1/128/440 (COUNT=1, E=16, N=8, A=16)
Tiger validation suite running...
passed 3293ac630c13f0245f92bbb1766e16167a4e58492dde73f3 ""
passed 77befbef2e7ef8ab2ec8f93bf587a7fc613e247f5f247809 "a"
passed 2aab1484e8c158f2bfb8c5ff41b57a525129131c957b5f93 "abc"
passed dd00230799f5009fec6debc838bb6a27df2b9d6f110c7937 "Tiger"
passed d981f8cb78201a950dcf3048751e441c517fca1aa55a29f6 "message digest"
passed 8dcea680a17583ee502ba38a3c368651890ffbccdc49a8cc "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789"
passed f71c8583902afb879edfe610f82c0d4786a3a534504486b5 "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+-"
passed 48ceeb6308b87d46e95d656112cdf18d97915f9765658957 "ABCDEFGHIJKLMNOPQRSTUVWXYZ=abcdefghijklmnopqrstuvwxyz+0123456789"
passed 8a866829040a410c729ad23f5ada711603b3cdd357e4c15e "Tiger - A Fast New Hash Function, by Ross Anderson and Eli Biham"
passed ce55a6afd591f5ebac547ff84f89227f9331dab0b611c889 "Tiger - A Fast New Hash Function, by Ross Anderson and Eli Biham, proceedings of Fast Software Encryption 3, Cambridge."
passed 631abdd103eb9a3d245b6dfd4d77b257fc7439501d1568dd "Tiger - A Fast New Hash Function, by Ross Anderson and Eli Biham, proceedings of Fast Software Encryption 3, Cambridge, 1996."
passed c54034e5b43eb8005848a7e0ae6aac76e4ff590ae715fd25 "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+-ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+-"
RIPEMD-128 validation suite running...
passed cdf26213a150dc3ecb610f18f6b38b46 ""
passed 86be7afa339d0fc7cfc785e72f578d33 "a"
passed c14a12199c66e4ba84636b0f69144c77 "abc"
passed 9e327b3d6e523062afc1132d7df9d1b8 "message digest"
passed fd2aa607f71dc8f510714922b371834e "abcdefghijklmnopqrstuvwxyz"
passed a1aa0689d0fafa2ddc22e88b49133a06 "abcdbcdecdefdefgefghfghighijhijkijkljklmklmnlmnomnopnopq"
passed d1e959eb179c911faea4624c60c5c702 "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789"
passed 3f45ef194732c2dbb2c4a2c769795fa3 "12345678901234567890123456789012345678901234567890123456789012345678901234567890"
passed 4a7f5723f954eba1216c9d8f6320431f "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa" repeated 15625 times
RIPEMD-160 validation suite running...
passed 9c1185a5c5e9fc54612808977ee8f548b2258d31 ""
passed 0bdc9d2d256b3ee9daae347be6f4dc835a467ffe "a"
passed 8eb208f7e05d987a9b044a8e98c6b087f15a0bfc "abc"
passed 5d0689ef49d2fae572b881b123a85ffa21595f36 "message digest"
passed f71c27109c692c1b56bbdceb5b9d2865b3708dbc "abcdefghijklmnopqrstuvwxyz"
passed 12a053384a9c0c88e405a06c27dcf49ada62eb2b "abcdbcdecdefdefgefghfghighijhijkijkljklmklmnlmnomnopnopq"
passed b0e20b6e3116640286ed3a87a5713079b21f5189 "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789"
passed 9b752e45573d4b39f4dbd3323cab82bf63326bfb "12345678901234567890123456789012345678901234567890123456789012345678901234567890"
passed 52783243c1697bdbe16d37f97f68f08325dc1528 "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa" repeated 15625 times
RIPEMD-256 validation suite running...
passed 02ba4c4e5f8ecd1877fc52d64d30e37a2d9774fb1e5d026380ae0168e3c5522d ""
passed f9333e45d857f5d90a91bab70a1eba0cfb1be4b0783c9acfcd883a9134692925 "a"
passed afbd6e228b9d8cbbcef5ca2d03e6dba10ac0bc7dcbe4680e1e42d2e975459b65 "abc"
passed 87e971759a1ce47a514d5c914c392c9018c7c46bc14465554afcdf54a5070c0e "message digest"
passed 649d3034751ea216776bf9a18acc81bc7896118a5197968782dd1fd97d8d5133 "abcdefghijklmnopqrstuvwxyz"
passed 3843045583aac6c8c8d9128573e7a9809afb2a0f34ccc36ea9e72f16f6368e3f "abcdbcdecdefdefgefghfghighijhijkijkljklmklmnlmnomnopnopq"
passed 5740a408ac16b720b84424ae931cbb1fe363d1d0bf4017f1a89f7ea6de77a0b8 "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789"
passed 06fdcc7a409548aaf91368c06a6275b553e3f099bf0ea4edfd6778df89a890dd "12345678901234567890123456789012345678901234567890123456789012345678901234567890"
passed ac953744e10e31514c150d4d8d7b677342e33399788296e43ae4850ce4f97978 "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa" repeated 15625 times
RIPEMD-320 validation suite running...
passed 22d65d5661536cdc75c1fdf5c6de7b41b9f27325ebc61e8557177d705a0ec880151c3a32a00899b8 ""
passed ce78850638f92658a5a585097579926dda667a5716562cfcf6fbe77f63542f99b04705d6970dff5d "a"
passed de4c01b3054f8930a79d09ae738e92301e5a17085beffdc1b8d116713e74f82fa942d64cdbc4682d "abc"
passed 3a8e28502ed45d422f68844f9dd316e7b98533fa3f2a91d29f84d425c88d6b4eff727df66a7c0197 "message digest"
passed cabdb1810b92470a2093aa6bce05952c28348cf43ff60841975166bb40ed234004b8824463e6b009 "abcdefghijklmnopqrstuvwxyz"
passed d034a7950cf722021ba4b84df769a5de2060e259df4c9bb4a4268c0e935bbc7470a969c9d072a1ac "abcdbcdecdefdefgefghfghighijhijkijkljklmklmnlmnomnopnopq"
passed ed544940c86d67f250d232c30b7b3e5770e0c60c8cb9a4cafe3b11388af9920e1b99230b843c86a4 "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789"
passed 557888af5f6d8ed62ab66945c6d2a0a47ecd5341e915eb8fea1d0524955f825dc717e4a008ab2d42 "12345678901234567890123456789012345678901234567890123456789012345678901234567890"
passed bdee37f4371e20646b8b0d862dda16292ae36f40965e8c8509e63d1dbddecc503e2b63eb9245bb66 "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa" repeated 15625 times
Panama validation suite running...
Testing MessageDigest algorithm Panama-LE.
...
Testing MessageDigest algorithm Panama-BE.
...
Testing MAC algorithm Panama-LE.
....
Testing MAC algorithm Panama-BE.
....
Testing SymmetricCipher algorithm Panama-LE.
...
Testing SymmetricCipher algorithm Panama-BE.
...
Tests complete. Total tests = 20. Failed tests = 0.
Whirlpool validation suite running...
Testing MessageDigest algorithm Whirlpool.
.........
Tests complete. Total tests = 9. Failed tests = 0.
Testing MessageDigest algorithm SM3.
.............................................................
Tests complete. Total tests = 61. Failed tests = 0.
BLAKE2s validation suite running...
passed algorithm name
passed 65 hashes and keyed hashes
BLAKE2b validation suite running...
passed algorithm name
passed 65 hashes and keyed hashes
Poly1305 validation suite running...
passed algorithm name
passed 12 message authentication codes
SipHash validation suite running...
passed SipHash-2-4 algorithm name
passed SipHash-2-4 64-bit digest size
passed SipHash-2-4 128-bit digest size
passed SipHash-4-8 algorithm name
passed SipHash-4-8 64-bit digest size
passed SipHash-4-8 128-bit digest size
passed SipHash-2-4 64-bit MAC
passed SipHash-2-4 128-bit MAC
passed SipHash-4-8 64-bit MAC
passed SipHash-4-8 128-bit MAC
Testing MAC algorithm HMAC(MD5).
........
Testing MAC algorithm HMAC(SHA-1).
........
Testing MAC algorithm HMAC(RIPEMD-160).
........
Testing MAC algorithm HMAC(SHA-224).
.......
Testing MAC algorithm HMAC(SHA-256).
.......
Testing MAC algorithm HMAC(SHA-384).
.......
Testing MAC algorithm HMAC(SHA-512).
.......
Tests complete. Total tests = 52. Failed tests = 0.
Two-Track-MAC validation suite running...
passed 2dec8ed4a0fd712ed9fbf2ab466ec2df21215e4a ""
passed 5893e3e6e306704dd77ad6e6ed432cde321a7756 "a"
passed 70bfd1029797a5c16da5b557a1f0b2779b78497e "abc"
passed 8289f4f19ffe4f2af737de4bd71c829d93a972fa "message digest"
passed 2186ca09c5533198b7371f245273504ca92bae60 "abcdefghijklmnopqrstuvwxyz"
passed 8a7bf77aef62a2578497a27c0d6518a429e7c14d "abcdbcdecdefdefgefghfghighijhijkijkljklmklmnlmnomnopnopq"
passed 54bac392a886806d169556fcbb6789b54fb364fb "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789"
passed 0ced2c9f8f0d9d03981ab5c8184bac43dd54c484 "12345678901234567890123456789012345678901234567890123456789012345678901234567890"
PKCS #12 PBKDF validation suite running...
passed 01 1 0073006D006500670000 0A58CF64530D823F 8AAAE6297B6CB04642AB5B077851284EB7128F1A2A7FBCA3
passed 02 1 0073006D006500670000 0A58CF64530D823F 79993DFE048D3B76
passed 01 1 0073006D006500670000 642B99AB44FB4B1F F3A95FEC48D7711E985CFE67908C5AB79FA3D7C5CAA5D966
passed 02 1 0073006D006500670000 642B99AB44FB4B1F C0A38D64A79BEA1D
passed 03 1 0073006D006500670000 3D83C0E4546AC140 8D967D88F6CAA9D714800AB3D48051D63F73A312
passed 01 1000 007100750065006500670000 05DEC959ACFF72F7 ED2034E36328830FF09DF1E1A07DD357185DAC0D4F9EB3D4
passed 02 1000 007100750065006500670000 05DEC959ACFF72F7 11DEDAD7758D4860
passed 01 1000 007100750065006500670000 1682C0FC5B3F7EC5 483DD6E919D7DE2E8E648BA8F862F3FBFBDC2BCB2C02957F
passed 02 1000 007100750065006500670000 1682C0FC5B3F7EC5 9D461D1B00355C50
passed 03 1000 007100750065006500670000 263216FCC2FAB31C 5EC4C7A80DF652294C3925B6489A7AB857C83476
PKCS #5 PBKDF2 validation suite running...
passed 00 5 70617373776f7264 1234567878563412 D1DAA78615F287E6
passed 00 500 416C6C206E2D656E746974696573206D75737420636F6D6D756E69636174652077697468206F74686572206E2d656E74697469657320766961206E2D3120656E746974656568656568656573 1234567878563412 6A8970BF68C92CAEA84A8DF28510858607126380CC47AB2D
RFC 5869 HKDF(SHA-1) validation suite running...
passed 0b0b0b0b0b0b0b0b0b0b0b 000102030405060708090a0b0c f0f1f2f3f4f5f6f7f8f9 085A01EA1B10F36933068B56EFA5AD81A4F14B822F5B091568A9CDD4F155FDA2C22E422478D305F3F896
passed 000102030405060708090a0b0c0d0e0f 101112131415161718191a1b1c1d1e1f 202122232425262728292a2b2c2d2e2f 303132333435363738393a3b3c3d3e3f 404142434445464748494a4b4c4d4e4f 606162636465666768696a6b6c6d6e6f 707172737475767778797a7b7c7d7e7f 808182838485868788898a8b8c8d8e8f 909192939495969798999a9b9c9d9e9f a0a1a2a3a4a5a6a7a8a9aaabacadaeaf b0b1b2b3b4b5b6b7b8b9babbbcbdbebf c0c1c2c3c4c5c6c7c8c9cacbcccdcecf d0d1d2d3d4d5d6d7d8d9dadbdcdddedf e0e1e2e3e4e5e6e7e8e9eaebecedeeef f0f1f2f3f4f5f6f7f8f9fafbfcfdfeff 0BD770A74D1160F7C9F12CD5912A06EBFF6ADCAE899D92191FE4305673BA2FFE8FA3F1A4E5AD79F3F334B3B202B2173C486EA37CE3D397ED034C7F9DFEB15C5E927336D0441F4C4300E2CFF0D0900B52D3B4
passed 0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b <0-LEN SALT> <0-LEN INFO> 0AC1AF7002B3D761D1E55298DA9D0506B9AE52057220A306E07B6B87E8DF21D0EA00033DE03984D34918
passed 0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c <NO SALT> <0-LEN INFO> 2C91117204D745F3500D636A62F64F0AB3BAE548AA53D423B0D1F27EBBA6F5E5673A081D70CCE7ACFC48
RFC 5869 HKDF(SHA-256) validation suite running...
passed 0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b 000102030405060708090a0b0c f0f1f2f3f4f5f6f7f8f9 3CB25F25FAACD57A90434F64D0362F2A2D2D0A90CF1A5A4C5DB02D56ECC4C5BF34007208D5B887185865
passed 000102030405060708090a0b0c0d0e0f 101112131415161718191a1b1c1d1e1f 202122232425262728292a2b2c2d2e2f 303132333435363738393a3b3c3d3e3f 404142434445464748494a4b4c4d4e4f 606162636465666768696a6b6c6d6e6f 707172737475767778797a7b7c7d7e7f 808182838485868788898a8b8c8d8e8f 909192939495969798999a9b9c9d9e9f a0a1a2a3a4a5a6a7a8a9aaabacadaeaf b0b1b2b3b4b5b6b7b8b9babbbcbdbebf c0c1c2c3c4c5c6c7c8c9cacbcccdcecf d0d1d2d3d4d5d6d7d8d9dadbdcdddedf e0e1e2e3e4e5e6e7e8e9eaebecedeeef f0f1f2f3f4f5f6f7f8f9fafbfcfdfeff B11E398DC80327A1C8E7F78C596A49344F012EDA2D4EFAD8A050CC4C19AFA97C59045A99CAC7827271CB41C65E590E09DA3275600C2F09B8367793A9ACA3DB71CC30C58179EC3E87C14C01D5C1F3434F1D87
passed 0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b <0-LEN SALT> <0-LEN INFO> 8DA4E775A563C18F715F802A063C5A31B8A11F5C5EE1879EC3454E5F3C738D2D9D201395FAA4B61A96C8
RFC 5869 HKDF(SHA-512) validation suite running...
passed 0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b 000102030405060708090a0b0c f0f1f2f3f4f5f6f7f8f9 832390086CDA71FB47625BB5CEB168E4C8E26A1A16ED34D9FC7FE92C1481579338DA362CB8D9F925D7CB
passed 000102030405060708090a0b0c0d0e0f 101112131415161718191a1b1c1d1e1f 202122232425262728292a2b2c2d2e2f 303132333435363738393a3b3c3d3e3f 404142434445464748494a4b4c4d4e4f 606162636465666768696a6b6c6d6e6f 707172737475767778797a7b7c7d7e7f 808182838485868788898a8b8c8d8e8f 909192939495969798999a9b9c9d9e9f a0a1a2a3a4a5a6a7a8a9aaabacadaeaf b0b1b2b3b4b5b6b7b8b9babbbcbdbebf c0c1c2c3c4c5c6c7c8c9cacbcccdcecf d0d1d2d3d4d5d6d7d8d9dadbdcdddedf e0e1e2e3e4e5e6e7e8e9eaebecedeeef f0f1f2f3f4f5f6f7f8f9fafbfcfdfeff CE6C97192805B346E6161E821ED165673B84F400A2B514B2FE23D84CD189DDF1B695B48CBD1C8388441137B3CE28F16AA64BA33BA466B24DF6CFCB021ECFF235F6A2056CE3AF1DE44D572097A8505D9E7A93
passed 0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b <0-LEN SALT> <0-LEN INFO> F5FA02B18298A72A8C23898A8703472C6EB179DC204C03425C970E3B164BF90FFF22D04836D0E2343BAC
passed 0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c <NO SALT> <0-LEN INFO> 1407D46013D98BC6DECEFCFEE55F0F90B0C7F63D68EB1A80EAF07E953CFC0A3A5240A155D6E4DAA965BB
RFC 5869 HKDF(Whirlpool) validation suite running...
passed 0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b 000102030405060708090a0b0c f0f1f2f3f4f5f6f7f8f9 0D29F74CCD8640F44B0DD9638111C1B5766EFED752AF358109E2E7C9CD4A28EF2F90B2AD461FBA0744D4
passed 000102030405060708090a0b0c0d0e0f 101112131415161718191a1b1c1d1e1f 202122232425262728292a2b2c2d2e2f 303132333435363738393a3b3c3d3e3f 404142434445464748494a4b4c4d4e4f 606162636465666768696a6b6c6d6e6f 707172737475767778797a7b7c7d7e7f 808182838485868788898a8b8c8d8e8f 909192939495969798999a9b9c9d9e9f a0a1a2a3a4a5a6a7a8a9aaabacadaeaf b0b1b2b3b4b5b6b7b8b9babbbcbdbebf c0c1c2c3c4c5c6c7c8c9cacbcccdcecf d0d1d2d3d4d5d6d7d8d9dadbdcdddedf e0e1e2e3e4e5e6e7e8e9eaebecedeeef f0f1f2f3f4f5f6f7f8f9fafbfcfdfeff 4EBE4FE2DCCEC42661699500BE279A993FED90351E19373B3926FAA3A410700B2BBF77E254CF1451AE6068D64A0904D966F4FF25498445A501B88F50D21E3A68A890E09445DC5886DD00E7F4F7C58A512170
Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\scrypt.cpp(262): CryptoPP::Scrypt::DeriveKey
Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\scrypt.cpp(285): CryptoPP::Scrypt::DeriveKey
Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\pwdbased.h(246): CryptoPP::PKCS5_PBKDF2_HMAC<class CryptoPP::SHA256>::DeriveKey
passed 0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b <0-LEN SALT> <0-LEN INFO> 110632D0F7AEFAC31771FC66C22BB3462614B81E4B04BA7F2B662E0BD694F56458615F9A9CB56C57ECF2
passed 0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c <NO SALT> <0-LEN INFO> 4089286EBFB23DD8A02F0C9DAA35D538EB09CD0A8CBAB203F39083AA3E0BD313E6F91E64F21A187510B0
RFC 7914 Scrypt validation suite running...
Assertion failed: D:\a\cryptopp-windows-ci\cryptopp-windows-ci\pwdbased.h(246): CryptoPP::PKCS5_PBKDF2_HMAC<class CryptoPP::SHA256>::DeriveKey
passed "" "" 16 1 1 77D6576238657B203B19CA42C18A0497F16B4844E3074AE8DFDFFA3FEDE21442FCD0069DED0948F8326A753A0FC81F17E8D3E0FB2E0D3628CF35E20C38D18906
passed password NaCl 1024 8 16 FDBABE1C9D3472007856E7190D01E9FE7C6AD7CBC8237830E77376634B3731622EAF30D92E22A3886FF109279D9830DAC727AFB94A83EE6D8360CBDFA2CC0640
passed pleaseletmein SodiumChloride 16384 8 1 7023BDCB3AFD7348461C06CD81FD38EBFDA8FBBA904F8E3EA9B543F6545DA1F2D5432955613F0FCF62D49705242A9AF9E61E85DC0D651E40DFCF017B45575887
DES validation suite running...
passed 0101010101010101 95F8A5E5DD31D900 8000000000000000
passed 0101010101010101 DD7F121CA5015619 4000000000000000
passed 0101010101010101 2E8653104F3834EA 2000000000000000
passed 0101010101010101 4BD388FF6CD81D4F 1000000000000000
passed 0101010101010101 20B9E767B2FB1456 0800000000000000
passed 0101010101010101 55579380D77138EF 0400000000000000
passed 0101010101010101 6CC5DEFAAF04512F 0200000000000000
passed 0101010101010101 0D9F279BA5D87260 0100000000000000
passed 0101010101010101 D9031B0271BD5A0A 0080000000000000
passed 0101010101010101 424250B37C3DD951 0040000000000000
passed 0101010101010101 B8061B7ECD9A21E5 0020000000000000
passed 0101010101010101 F15D0F286B65BD28 0010000000000000
passed 0101010101010101 ADD0CC8D6E5DEBA1 0008000000000000
passed 0101010101010101 E6D5F82752AD63D1 0004000000000000
passed 0101010101010101 ECBFE3BD3F591A5E 0002000000000000
passed 0101010101010101 F356834379D165CD 0001000000000000
passed 0101010101010101 2B9F982F20037FA9 0000800000000000
passed 0101010101010101 889DE068A16F0BE6 0000400000000000
passed 0101010101010101 E19E275D846A1298 0000200000000000
passed 0101010101010101 329A8ED523D71AEC 0000100000000000
passed 0101010101010101 E7FCE22557D23C97 0000080000000000
passed 0101010101010101 12A9F5817FF2D65D 0000040000000000
passed 0101010101010101 A484C3AD38DC9C19 0000020000000000
passed 0101010101010101 FBE00A8A1EF8AD72 0000010000000000
passed 0101010101010101 750D079407521363 0000008000000000
passed 0101010101010101 64FEED9C724C2FAF 0000004000000000
passed 0101010101010101 F02B263B328E2B60 0000002000000000
passed 0101010101010101 9D64555A9A10B852 0000001000000000
passed 0101010101010101 D106FF0BED5255D7 0000000800000000
passed 0101010101010101 E1652C6B138C64A5 0000000400000000
passed 0101010101010101 E428581186EC8F46 0000000200000000
passed 0101010101010101 AEB5F5EDE22D1A36 0000000100000000
passed 0101010101010101 E943D7568AEC0C5C 0000000080000000
passed 0101010101010101 DF98C8276F54B04B 0000000040000000
passed 0101010101010101 B160E4680F6C696F 0000000020000000
passed 0101010101010101 FA0752B07D9C4AB8 0000000010000000
passed 0101010101010101 CA3A2B036DBC8502 0000000008000000
passed 0101010101010101 5E0905517BB59BCF 0000000004000000
passed 0101010101010101 814EEB3B91D90726 0000000002000000
passed 0101010101010101 4D49DB1532919C9F 0000000001000000
passed 0101010101010101 25EB5FC3F8CF0621 0000000000800000
passed 0101010101010101 AB6A20C0620D1C6F 0000000000400000
passed 0101010101010101 79E90DBC98F92CCA 0000000000200000
passed 0101010101010101 866ECEDD8072BB0E 0000000000100000
passed 0101010101010101 8B54536F2F3E64A8 0000000000080000
passed 0101010101010101 EA51D3975595B86B 0000000000040000
passed 0101010101010101 CAFFC6AC4542DE31 0000000000020000
passed 0101010101010101 8DD45A2DDF90796C 0000000000010000
passed 0101010101010101 1029D55E880EC2D0 0000000000008000
passed 0101010101010101 5D86CB23639DBEA9 0000000000004000
passed 0101010101010101 1D1CA853AE7C0C5F 0000000000002000
passed 0101010101010101 CE332329248F3228 0000000000001000
passed 0101010101010101 8405D1ABE24FB942 0000000000000800
passed 0101010101010101 E643D78090CA4207 0000000000000400
passed 0101010101010101 48221B9937748A23 0000000000000200
passed 0101010101010101 DD7C0BBD61FAFD54 0000000000000100
passed 0101010101010101 2FBC291A570DB5C4 0000000000000080
passed 0101010101010101 E07C30D7E4E26E12 0000000000000040
passed 0101010101010101 0953E2258E8E90A1 0000000000000020
passed 0101010101010101 5B711BC4CEEBF2EE 0000000000000010
passed 0101010101010101 CC083F1E6D9E85F6 0000000000000008
passed 0101010101010101 D2FD8867D50D2DFE 0000000000000004
passed 0101010101010101 06E7EA22CE92708F 0000000000000002
passed 0101010101010101 166B40B44ABA4BD6 0000000000000001
passed 8001010101010101 0000000000000000 95A8D72813DAA94D
passed 4001010101010101 0000000000000000 0EEC1487DD8C26D5
passed 2001010101010101 0000000000000000 7AD16FFB79C45926
passed 1001010101010101 0000000000000000 D3746294CA6A6CF3
passed 0801010101010101 0000000000000000 809F5F873C1FD761
passed 0401010101010101 0000000000000000 C02FAFFEC989D1FC
passed 0201010101010101 0000000000000000 4615AA1D33E72F10
passed 0180010101010101 0000000000000000 2055123350C00858
passed 0140010101010101 0000000000000000 DF3B99D6577397C8
passed 0120010101010101 0000000000000000 31FE17369B5288C9
passed 0110010101010101 0000000000000000 DFDD3CC64DAE1642
passed 0108010101010101 0000000000000000 178C83CE2B399D94
passed 0104010101010101 0000000000000000 50F636324A9B7F80
passed 0102010101010101 0000000000000000 A8468EE3BC18F06D
passed 0101800101010101 0000000000000000 A2DC9E92FD3CDE92
passed 0101400101010101 0000000000000000 CAC09F797D031287
passed 0101200101010101 0000000000000000 90BA680B22AEB525
passed 0101100101010101 0000000000000000 CE7A24F350E280B6
passed 0101080101010101 0000000000000000 882BFF0AA01A0B87
passed 0101040101010101 0000000000000000 25610288924511C2
passed 0101020101010101 0000000000000000 C71516C29C75D170
passed 0101018001010101 0000000000000000 5199C29A52C9F059
passed 0101014001010101 0000000000000000 C22F0A294A71F29F
passed 0101012001010101 0000000000000000 EE371483714C02EA
passed 0101011001010101 0000000000000000 A81FBD448F9E522F
passed 0101010801010101 0000000000000000 4F644C92E192DFED
passed 0101010401010101 0000000000000000 1AFA9A66A6DF92AE
passed 0101010201010101 0000000000000000 B3C1CC715CB879D8
passed 0101010180010101 0000000000000000 19D032E64AB0BD8B
passed 0101010140010101 0000000000000000 3CFAA7A7DC8720DC
passed 0101010120010101 0000000000000000 B7265F7F447AC6F3
passed 0101010110010101 0000000000000000 9DB73B3C0D163F54
passed 0101010108010101 0000000000000000 8181B65BABF4A975
passed 0101010104010101 0000000000000000 93C9B64042EAA240
passed 0101010102010101 0000000000000000 5570530829705592
passed 0101010101800101 0000000000000000 8638809E878787A0
passed 0101010101400101 0000000000000000 41B9A79AF79AC208
passed 0101010101200101 0000000000000000 7A9BE42F2009A892
passed 0101010101100101 0000000000000000 29038D56BA6D2745
passed 0101010101080101 0000000000000000 5495C6ABF1E5DF51
passed 0101010101040101 0000000000000000 AE13DBD561488933
passed 0101010101020101 0000000000000000 024D1FFA8904E389
passed 0101010101018001 0000000000000000 D1399712F99BF02E
passed 0101010101014001 0000000000000000 14C1D7C1CFFEC79E
passed 0101010101012001 0000000000000000 1DE5279DAE3BED6F
passed 0101010101011001 0000000000000000 E941A33F85501303
passed 0101010101010801 0000000000000000 DA99DBBC9A03F379
passed 0101010101010401 0000000000000000 B7FC92F91D8E92E9
passed 0101010101010201 0000000000000000 AE8E5CAA3CA04E85
passed 0101010101010180 0000000000000000 9CC62DF43B6EED74
passed 0101010101010140 0000000000000000 D863DBB5C59A91A0
passed 0101010101010120 0000000000000000 A1AB2190545B91D7
passed 0101010101010110 0000000000000000 0875041E64C570F7
passed 0101010101010108 0000000000000000 5A594528BEBEF1CC
passed 0101010101010104 0000000000000000 FCDB3291DE21F0C0
passed 0101010101010102 0000000000000000 869EFD7F9F265A09
passed 1046913489980131 0000000000000000 88D55E54F54C97B4
passed 1007103489988020 0000000000000000 0C0CC00C83EA48FD
passed 10071034C8980120 0000000000000000 83BC8EF3A6570183
passed 1046103489988020 0000000000000000 DF725DCAD94EA2E9
passed 1086911519190101 0000000000000000 E652B53B550BE8B0
passed 1086911519580101 0000000000000000 AF527120C485CBB0
passed 5107B01519580101 0000000000000000 0F04CE393DB926D5
passed 1007B01519190101 0000000000000000 C9F00FFC74079067
passed 3107915498080101 0000000000000000 7CFD82A593252B4E
passed 3107919498080101 0000000000000000 CB49A2F9E91363E3
passed 10079115B9080140 0000000000000000 00B588BE70D23F56
passed 3107911598090140 0000000000000000 406A9A6AB43399AE
passed 1007D01589980101 0000000000000000 6CB773611DCA9ADA
passed 9107911589980101 0000000000000000 67FD21C17DBB5D70
passed 9107D01589190101 0000000000000000 9592CB4110430787
passed 1007D01598980120 0000000000000000 A6B7FF68A318DDD3
passed 1007940498190101 0000000000000000 4D102196C914CA16
passed 0107910491190401 0000000000000000 2DFA9F4573594965
passed 0107910491190101 0000000000000000 B46604816C0E0774
passed 0107940491190401 0000000000000000 6E7E6221A4F34E87
passed 19079210981A0101 0000000000000000 AA85E74643233199
passed 1007911998190801 0000000000000000 2E5A19DB4D1962D6
passed 10079119981A0801 0000000000000000 23A866A809D30894
passed 1007921098190101 0000000000000000 D812D961F017D320
passed 100791159819010B 0000000000000000 055605816E58608F
passed 1004801598190101 0000000000000000 ABD88E8B1B7716F1
passed 1004801598190102 0000000000000000 537AC95BE69DA1E1
passed 1004801598190108 0000000000000000 AED0F6AE3C25CDD8
passed 1002911598100104 0000000000000000 B3E35A5EE53E7B8D
passed 1002911598190104 0000000000000000 61C79C71921A2EF8
passed 1002911598100201 0000000000000000 E2F5728F0995013C
passed 1002911698100101 0000000000000000 1AEAC39A61F0A464
passed 7CA110454A1A6E57 01A1D6D039776742 690F5B0D9A26939B
passed 0131D9619DC1376E 5CD54CA83DEF57DA 7A389D10354BD271
passed 07A1133E4A0B2686 0248D43806F67172 868EBB51CAB4599A
passed 3849674C2602319E 51454B582DDF440A 7178876E01F19B2A
passed 04B915BA43FEB5B6 42FD443059577FA2 AF37FB421F8C4095
passed 0113B970FD34F2CE 059B5E0851CF143A 86A560F10EC6D85B
passed 0170F175468FB5E6 0756D8E0774761D2 0CD3DA020021DC09
passed 43297FAD38E373FE 762514B829BF486A EA676B2CB7DB2B7A
passed 07A7137045DA2A16 3BDD119049372802 DFD64A815CAF1A0F
passed 04689104C2FD3B2F 26955F6835AF609A 5C513C9C4886C088
passed 37D06BB516CB7546 164D5E404F275232 0A2AEEAE3FF4AB77
passed 1F08260D1AC2465E 6B056E18759F5CCA EF1BF03E5DFA575A
passed 584023641ABA6176 004BD6EF09176062 88BF0DB6D70DEE56
passed 025816164629B007 480D39006EE762F2 A1F9915541020B56
passed 49793EBC79B3258F 437540C8698F3CFA 6FBF1CAFCFFD0556
passed 4FB05E1515AB73A7 072D43A077075292 2F22E49BAB7CA1AC
passed 49E95D6D4CA229BF 02FE55778117F12A 5A6B612CC26CCE4A
passed 018310DC409B26D6 1D9D5C5018F728C2 5F4C038ED12B2E41
passed 1C587F1C13924FEF 305532286D6F295A 63FAC0D034D9F793
Testing EDE2, EDE3, and XEX3 variants...
passed 0123456789ABCDEFFEDCBA9876543210 0123456789ABCDE7 7F1D0A77826B8AFF
passed 0123456789ABCDEFFEDCBA987654321089ABCDEF01234567 0123456789ABCDE7 DE0B7C06AE5E0ED5
passed 0123456789ABCDEF01010101010101011011121314151617 94DBE082549A14EF 9011121314151617
Testing DES modes...
passed ECB encryption
passed ECB decryption
passed CBC encryption with no padding
passed CBC decryption with no padding
passed CBC mode IV generation
passed CBC encryption with PKCS #7 padding
passed CBC decryption with PKCS #7 padding
passed CBC encryption with one-and-zeros padding
passed CBC decryption with one-and-zeros padding
passed CBC encryption with zeros padding
passed CBC decryption with zeros padding
passed CBC encryption with ciphertext stealing (CTS)
passed CBC decryption with ciphertext stealing (CTS)
passed CBC CTS IV generation
passed CBC encryption with ciphertext and IV stealing
passed CBC decryption with ciphertext and IV stealing
passed CFB encryption
passed CFB decryption
passed CFB mode IV generation
passed CFB (8-bit feedback) encryption
passed CFB (8-bit feedback) decryption
passed CFB (8-bit feedback) IV generation
passed OFB encryption
passed OFB decryption
passed OFB IV generation
passed Counter Mode encryption
passed Counter Mode decryption
passed Counter Mode IV generation
passed CBC MAC
passed DMAC
IDEA validation suite running...
passed 00010002000300040005000600070008 0000000100020003 11FBED2B01986DE5
passed 00010002000300040005000600070008 0102030405060708 540E5FEA18C2F8B1
passed 00010002000300040005000600070008 0019324B647D96AF 9F0A0AB6E10CED78
passed 00010002000300040005000600070008 F5202D5B9C671B08 CF18FD7355E2C5C5
passed 00010002000300040005000600070008 FAE6D2BEAA96826E 85DF52005608193D
passed 00010002000300040005000600070008 0A141E28323C4650 2F7DE750212FB734
passed 00010002000300040005000600070008 050A0F14191E2328 7B7314925DE59C09
passed 0005000A000F00140019001E00230028 0102030405060708 3EC04780BEFF6E20
passed 3A984E2000195DB32EE501C8C47CEA60 0102030405060708 97BCD8200780DA86
passed 006400C8012C019001F4025802BC0320 05320A6414C819FA 65BE87E7A2538AED
passed 9D4075C103BC322AFB03E7BE6AB30006 0808080808080808 F5DB1AC45E5EF9F9
SAFER validation suite running...
passed 0000000000000000 0000000000000000 032808C90EE7AB7F
passed 0000000000000000 0102030405060708 7D28038633B92EB4
passed 0102030405060708 1011121314151617 71E5CF7F083A59C5
passed 0102030405060708 18191A1B1C1D1E1F 356F702CC7FA8161
passed 08070605040302010807060504030201 5051525354555657 38E64DBF6E0F896E
passed 08070605040302010807060504030201 58595A5B5C5D5E5F 7D8F014A902480FE
passed 01020304050607080807060504030201 6061626364656667 113511C22E7936DF
passed 01020304050607080807060504030201 68696A6B6C6D6E6F 9EEB2D17C0581437
passed 0000000000000001 7071727374757677 9ABE2C85BE2D7614
passed 0000000000000001 78797A7B7C7D7E7F EBC4A9C6C25CF215
passed 0102030405060708 8081828384858687 54E72BA2D744C566
passed 0102030405060708 88898A8B8C8D8E8F 57F55D0F7EB6F8FE
passed 00000000000000010000000000000001 9091929394959697 9EAA4DF1E0EFF445
passed 00000000000000010000000000000001 98999A9B9C9D9E9F 4CC14838399E532D
passed 01020304050607080000000000000000 A0A1A2A3A4A5A6A7 41246B65F1DC6AFA
passed 00000000000000000102030405060708 A0A1A2A3A4A5A6A7 5CBD77B03626FE3B
RC2 validation suite running...
passed 0000000000000000 0000000000000000 EBB773F993278EFF
passed FFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFF 278B27E42E2F0D49
passed 3000000000000000 1000000000000001 30649EDF9BE7D2C2
passed 88 0000000000000000 61A8A244ADACCCF0
passed 88BCA90E90875A 0000000000000000 6CCF4308974C267F
passed 88BCA90E90875A7F0F79C384627BAFB2 0000000000000000 1A807D272BBE5DB1
passed 88BCA90E90875A7F0F79C384627BAFB2 0000000000000000 2269552AB0F85CA6
passed 88BCA90E90875A7F0F79C384627BAFB216F80A6F85920584C42FCEB0BE255DAF1E 0000000000000000 5B78D3A43DFFF1F1
ARC4 validation suite running...
passed Test 0
passed Test 1
passed Test 2
passed Test 3
passed Test 4
RC5 validation suite running...
passed: Algorithm key lengths
passed 00000000000000000000000000000000 0000000000000000 21A5DBEE154B8F6D
passed 915F4619BE41B2516355A50110A9CE91 21A5DBEE154B8F6D F7C013AC5B2B8952
passed 783348E75AEB0F2FD7B169BB8DC16787 F7C013AC5B2B8952 2F42B3B70369FC92
passed DC49DB1375A5584F6485B413B5F12BAF 2F42B3B70369FC92 65C178B284D197CC
passed 5269F149D41BA0152497574D7F153125 65C178B284D197CC EB44E415DA319824
Blowfish validation suite running...
passed: Algorithm key lengths
passed "abcdefghijklmnopqrstuvwxyz" 424C4F5746495348 324ED0FEF413A203
passed "Who is John Galt?" FEDCBA9876543210 CC91732B8022F684
3-WAY validation suite running...
passed: Algorithm key lengths
passed 000000000000000000000000 000000010000000100000001 4059C76E83AE9DC4AD21ECF7
passed 000000060000000500000004 000000030000000200000001 D2F05B5ED6144138CAB920CD
passed DEF01234456789ABBCDEF012 234567899ABCDEF001234567 0AA55DBB9CDDDB6D7CDB76B2
passed D2F05B5ED6144138CAB920CD 4059C76E83AE9DC4AD21ECF7 478EA8716B13F17C15B155ED
GOST validation suite running...
passed: Algorithm key lengths
passed BE5EC2006CFF9DCF52354959F1FF0CBFE95061B5A648C10387069C25997C0672 0DF82802B741A292 07F9027DF7F7DF89
passed B385272AC8D72A5A8B344BC80363AC4D09BF58F41F540624CBCB8FDCF55307D7 1354EE9C0A11CD4C 4FB50536F960A7B1
passed AEE02F609A35660E4097E546FD3026B032CD107C7D459977ADF489BEF2652262 6693D492C4B0CC39 670034AC0FA811B5
passed 320E9D8422165D58911DFC7D8BBB1F81B0ECD924023BF94D9DF7DCF7801240E0 99E2D13080928D79 8118FF9D3B3CFE7D
passed C9F703BBBFC63691BFA3B7B87EA8FD5E8E8EF384EF733F1A61AEF68C8FFA265F D1E787749C72814C A083826A790D3E0C
passed 728FEE32F04B4C654AD7F607D71C660C2C2670D7C999713233149A1C0C17A1F0 D4C05323A4F7A7B5 4D1F2E6B0D9DE2CE
passed 35FC96402209500FCFDEF5352D1ABB038FE33FC0D9D58512E56370B22BAA133B 8742D9A05F6A3AF6 2F3BB84879D11E52
passed D416F630BE65B7FE150656183370E07018234EE5DA3D89C4CE9152A03E5BFB77 F86506DA04E41CB8 96F0A5C77A04F5CE
SHARK validation suite running...
passed: Algorithm key lengths
passed 00000000000000000000000000000000 0000000000000000 214BCF4E7716420A
passed 000102030405060708090A0B0C0D0E0F 0000000000000000 C76C696289898137
passed 000102030405060708090A0B0C0D0E0F C76C696289898137 077A4A59FAEEEA4D
passed 915F4619BE41B2516355A50110A9CE91 21A5DBEE154B8F6D 6FF33B98F448E95A
passed 783348E75AEB0F2FD7B169BB8DC16787 F7C013AC5B2B8952 E5E554ABE9CED2D2
passed DC49DB1375A5584F6485B413B5F12BAF 2F42B3B70369FC92 9AE068313F343A7A
passed 5269F149D41BA0152497574D7F153125 65C178B284D197CC D3F111A282F17F29
CAST-128 validation suite running...
passed: Algorithm key lengths
passed 0123456712345678234567893456789A 0123456789ABCDEF 238B4FE5847E44B2
passed 01234567123456782345 0123456789ABCDEF EB6A711A2C02271B
passed 0123456712 0123456789ABCDEF 7AC816D16E9B302E
CAST-256 validation suite running...
passed: Algorithm key lengths
passed 2342BB9EFA38542C0AF75647F29F615D 00000000000000000000000000000000 C842A08972B43D20836C91D1B7530F6B
passed 2342BB9EFA38542CBED0AC83940AC298BAC77A7717942863 00000000000000000000000000000000 1B386C0210DCADCBDD0E41AA08A7A7E8
passed 2342BB9EFA38542CBED0AC83940AC2988D7C47CE264908461CC1B5137AE6B604 00000000000000000000000000000000 4F6A2038286897B9C9870136553317FA
Square validation suite running...
passed: Algorithm key lengths
passed 00000000000000000000000000000000 00000000000000000000000000000000 3C00428F8ABBC0B84F057CC19C26F8CF
passed 000102030405060708090A0B0C0D0E0F 00000000000000000000000000000000 FF596FA668BFC3014200AE01E2BBA0A0
passed 000102030405060708090A0B0C0D0E0F 000102030405060708090A0B0C0D0E0F 7C3491D94994E70F0EC2E7A5CCB5A14F
passed 000102030405060708090A0B0C0D0E0F C76C696289898137077A4A59FAEEEA4D 88C6FF4B92604C6E66656B02DDAF9F40
passed 915F4619BE41B2516355A50110A9CE91 21A5DBEE154B8F6D6FF33B98F448E95A 3388801F66E7FCC0BCE522A23A4F0C7F
passed 783348E75AEB0F2FD7B169BB8DC16787 F7C013AC5B2B8952E5E554ABE9CED2D2 A1C0E9215141343DEC2B556942C92BDE
passed DC49DB1375A5584F6485B413B5F12BAF 2F42B3B70369FC929AE068313F343A7A 3FBE6811B998CDF3E50ABDE2F3C075E3
passed 5269F149D41BA0152497574D7F153125 65C178B284D197CCD3F111A282F17F29 D7B7209E0879744C782809B6D2E0B1B0
SKIPJACK validation suite running...
passed: Algorithm key lengths
passed 11223344556677889900 AABBCCDD00112233 00D3127AE2CA8725
SEAL validation suite running...
passed
RC6 validation suite running...
passed: Algorithm key lengths
passed 00000000000000000000000000000000 00000000000000000000000000000000 8FC3A53656B1F778C129DF4E9848A41E
passed 0123456789ABCDEF0112233445566778 02132435465768798A9BACBDCEDFE0F1 524E192F4715C6231F51F6367EA43F18
passed 000000000000000000000000000000000000000000000000 00000000000000000000000000000000 6CD61BCB190B30384E8A3F168690AE82
passed 0123456789ABCDEF0112233445566778899AABBCCDDEEFF0 02132435465768798A9BACBDCEDFE0F1 688329D019E505041E52E92AF95291D4
passed 0000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000 8F5FBD0510D15FA893FA3FDA6E857EC2
passed 0123456789ABCDEF0112233445566778899AABBCCDDEEFF01032547698BADCFE 02132435465768798A9BACBDCEDFE0F1 C8241816F0D7E48920AD16A1674E5D48
MARS validation suite running...
passed: Algorithm key lengths
passed 00000000000000000000000000000000 00000000000000000000000000000000 DCC07B8DFB0738D6E30A22DFCF27E886
passed 00000000000000000000000000000000 DCC07B8DFB0738D6E30A22DFCF27E886 33CAFFBDDC7F1DDA0F9C15FA2F30E2FF
passed CB14A1776ABBC1CDAFE7243DEF2CEA02 F94512A9B42D034EC4792204D708A69B 225DA2CB64B73F79069F21A5E3CB8522
passed 86EDF4DA31824CABEF6A4637C40B0BAB 4DF955AD5B398D66408D620A2B27E1A9 A4B737340AE6D2CAFD930BA97D86129F
passed 000000000000000000000000000000000000000000000000 AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA 97778747D60E425C2B4202599DB856FB
passed D158860838874D9500000000000000000000000000000000 93A953A82C10411DD158860838874D95 4FA0E5F64893131712F01408D233E9F7
passed 791739A58B04581A93A953A82C10411DD158860838874D95 6761C42D3E6142D2A84FBFADB383158F F706BC0FD97E28B6F1AF4E17D8755FFF
passed 0000000000000000000000000000000000000000000000000000000000000000 62E45B4CF3477F1DD65063729D9ABA8F 0F4B897EA014D21FBC20F1054A42F719
passed FBA167983E7AEF22317CE28C02AAE1A3E8E5CC3CEDBEA82A99DBC39AD65E7227 1344ABA4D3C44708A8A72116D4F49384 458335D95EA42A9F4DCCD41AECC2390D
Rijndael (AES) validation suite running...
passed: Algorithm key lengths
passed 000102030405060708090A0B0C0D0E0F 000102030405060708090A0B0C0D0E0F 0A940BB5416EF045F1C39458C653EA5A
passed 00010203050607080A0B0C0D0F101112 506812A45F08C889B97F5980038B8359 D8F532538289EF7D06B506A4FD5BE9C9
passed 14151617191A1B1C1E1F202123242526 5C6D71CA30DE8B8B00549984D2EC7D4B 59AB30F4D4EE6E4FF9907EF65B1FB68C
passed 28292A2B2D2E2F30323334353738393A 53F3F4C64F8616E4E7C56199F48F21F6 BF1ED2FCB2AF3FD41443B56D85025CB1
passed 00010203050607080A0B0C0D0F10111214151617191A1B1C 2D33EEF2C0430A8A9EBF45E809C40BB6 DFF4945E0336DF4C1C56BC700EFF837F
passed 1E1F20212324252628292A2B2D2E2F30323334353738393A 6AA375D1FA155A61FB72353E0A5A8756 B6FDDEF4752765E347D5D2DC196D1252
passed 3C3D3E3F41424344464748494B4C4D4E5051525355565758 BC3736518B9490DCB8ED60EB26758ED4 D23684E3D963B3AFCF1A114ACA90CBD6
passed 00010203050607080A0B0C0D0F10111214151617191A1B1C1E1F202123242526 834EADFCCAC7E1B30664B1ABA44815AB 1946DABF6A03A2A2C3D0B05080AED6FC
passed 28292A2B2D2E2F30323334353738393A3C3D3E3F41424344464748494B4C4D4E D9DC4DBA3021B05D67C0518F72B62BF1 5ED301D747D3CC715445EBDEC62F2FB4
Testing SymmetricCipher algorithm AES/ECB.
........
Testing SymmetricCipher algorithm AES/CBC.
................
Testing SymmetricCipher algorithm AES/CFB.
.....................
Testing SymmetricCipher algorithm AES/OFB.
............
Testing SymmetricCipher algorithm AES/CTR.
.......................................
Testing SymmetricCipher algorithm AES/XTS.
................
Tests complete. Total tests = 112. Failed tests = 0.
Twofish validation suite running...
passed: Algorithm key lengths
passed 00000000000000000000000000000000 00000000000000000000000000000000 9F589F5CF6122C32B6BFEC2F2AE8C35A
passed 00000000000000000000000000000000 9F589F5CF6122C32B6BFEC2F2AE8C35A D491DB16E7B1C39E86CB086B789F5419
passed 9F589F5CF6122C32B6BFEC2F2AE8C35A D491DB16E7B1C39E86CB086B789F5419 019F9809DE1711858FAAC3A3BA20FBC3
passed D491DB16E7B1C39E86CB086B789F5419 019F9809DE1711858FAAC3A3BA20FBC3 6363977DE839486297E661C6C9D668EB
passed 000000000000000000000000000000000000000000000000 00000000000000000000000000000000 EFA71F788965BD4453F860178FC19101
passed EFA71F788965BD4453F860178FC191010000000000000000 88B2B2706B105E36B446BB6D731A1E88 39DA69D6BA4997D585B6DC073CA341B2
passed 88B2B2706B105E36B446BB6D731A1E88EFA71F788965BD44 39DA69D6BA4997D585B6DC073CA341B2 182B02D81497EA45F9DAACDC29193A65
passed 0000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000 57FF739D4DC92C1BD7FC01700CC8216F
passed D43BB7556EA32E46F2A282B7D45B4E0D57FF739D4DC92C1BD7FC01700CC8216F 90AFE91BB288544F2C32DC239B2635E6 6CB4561C40BF0A9705931CB6D408E7FA
Serpent validation suite running...
passed: Algorithm key lengths
passed 00000000000000000000000000000000 D29D576FCEA3A3A7ED9099F29273D78E B2288B968AE8B08648D1CE9606FD992D
passed 00000000000000000000000000000000 D29D576FCEA3A3A7ED9099F26D8C2871 563A8403FF5309D62370B1DCF5A11EDD
passed FFEEDDCCBBAA99887766554433221100 1032547698BADCFEEFCDAB8967452301 D5BAA00A4BB9D8A7C981C8DC90D89D92
passed FFEEDDCCBBAA99887766554433221100 145F0B8B663176B95DCAB7E9DCD5CC24 1032547698BADCFEEFCDAB8967452301
passed 80000000000000000000000000000000 00000000000000000000000000000000 264E5481EFF42A4606ABDA06C0BFDA3D
passed 000000000000000000000000000000000000000000000000 D29D576FCEABA3A7ED9899F2927BD78E 130E353E1037C22405E8FAEFB2C3C3E9
passed 8899AABBCCDDEEFFFFEEDDCCBBAA99887766554433221100 1032547698BADCFEEFCDAB8967452301 DA860842B720802BF404A4C71034879A
passed 8899AABBCCDDEEFFFFEEDDCCBBAA99887766554433221100 B2696BD0D98C17953E4239225D27202C 1032547698BADCFEEFCDAB8967452301
passed 000102030405060708090A0B0C0D0E0F1011121314151617 4528CACCB954D450655E8CFD71CBFAC7 00112233445566778899AABBCCDDEEFF
passed 0000000000000000000000000000000000000000000000000000000000000000 92074732D84E1841A013A0034C52BF50 81C4EB7B8AD9A8D0F2AA5D7BD626B560
passed 00112233445566778899AABBCCDDEEFFFFEEDDCCBBAA99887766554433221100 1032547698BADCFEEFCDAB8967452301 93DF9A3CAFE387BD999EEBE393A17FCA
passed 000102030405060708090A0B0C0D0E0F101112131415161718191A1B1C1D1E1F 3DA46FFA6F4D6F30CD258333E5A61369 00112233445566778899AABBCCDDEEFF
SHACAL-2 validation suite running...
passed: Algorithm key lengths
passed 80000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000 361AB6322FA9E7A7BB23818D839E01BDDAFDF47305426EDD297AEDB9F6202BAE
passed 00000000000000000000000000000001 0000000000000000000000000000000000000000000000000000000000000000 7308AEC23D25A231B26448AFE78D5047804C5011B9B5F95C16DF2670551F0001
passed 00000000000000000000000000000000 8000000000000000000000000000000000000000000000000000000000000000 2CAE7C0460EE2FC3200923A1B6C2ABEEA746C8B44F6C3FB941BD3AF02A3E6E3E
passed 00000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000001 45D43E9288738C5AD1A683D8DE59CEDD22D666A2B7078EB1301B532A272D570B
passed 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000 7CA51614425C3BA8CE54DD2FC2020AE7B6E574D198136D0FAE7E26CCBF0BE7A6
passed 01010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101 0101010101010101010101010101010101010101010101010101010101010101 C4B7C6A9738C77EE28F7E685C8358E0AF88FB6D23955EE6DF49FE3F5DA16F826
passed 02020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202 0202020202020202020202020202020202020202020202020202020202020202 CD108DD9EC1000B79C75AA3DCC88F913E6F52773853035A5C44F3245B134CBFF
passed 04040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404 0404040404040404040404040404040404040404040404040404040404040404 6AA777340200C1B65AB25193A8BB267C233DAC7E1B3C523D406FC5B567B7B586
passed 08080808080808080808080808080808080808080808080808080808080808080808080808080808080808080808080808080808080808080808080808080808 0808080808080808080808080808080808080808080808080808080808080808 A23BE32D37FA4054EC45D6A9CC643AF9124EDAA4AD9ABC7FAAB449D39D11B128
passed 10101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010 1010101010101010101010101010101010101010101010101010101010101010 F64819DFBEBE0A6DB650E7072CE28EA606586418B317785FF0AD44212A84C82C
passed 20202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020 2020202020202020202020202020202020202020202020202020202020202020 E267D6113C27170A3EE6DF496E801A6131BBD3444365D7C03791E25610F1A0E4
passed 40404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040404040 4040404040404040404040404040404040404040404040404040404040404040 C97909916EE86FFDCE8A92903046109B53F788A53039434DF1A394DAD6F697A2
passed 80808080808080808080808080808080808080808080808080808080808080808080808080808080808080808080808080808080808080808080808080808080 8080808080808080808080808080808080808080808080808080808080808080 C3C1CD5F3060B3EC4E6ABC0818B68449E1750FB482368C8F3305270E16F98735
passed FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF 0598127BAF11706F77402000D730C54A0B84C868A98C6CA4D7F3C0FA06A78B7A
ARIA validation suite running...
passed: Algorithm key lengths
passed 0123456789ABCDEFFEDCBA9876543210 0123456789ABCDEFFEDCBA9876543210 7DC1917AE0D38FAE8D4A7D1959AEF27C
passed 80000000000000000000000000000000 00000000000000000000000000000000 4ABA3055788204D82F4539D81BC9384B
passed 00000000000000000000000000000001 00000000000000000000000000000000 5FA57C3B2E71144C3E5E1E9BE4F0FE7E
passed 00000000000000000000000000000000 80000000000000000000000000000000 92E51E737DABB6BFD0EABC8D32224F77
passed 00000000000000000000000000000000 00000000000000000000000000000001 B426E1A441F6DBFC2B2D2412D0066D20
passed 00000000000000000000000000000000 00000000000000000000000000000000 4B40A63C7F0171EE3CDDA4363FBFAE75
passed 01010101010101010101010101010101 01010101010101010101010101010101 CCE5D964A71D7A5E93986BCA572BB050
passed 02020202020202020202020202020202 02020202020202020202020202020202 A04100328F459F6AAE8EBAB3B5FE90A8
passed 04040404040404040404040404040404 04040404040404040404040404040404 BFE5C38FE204ADC614A321786CDCA08E
passed 08080808080808080808080808080808 08080808080808080808080808080808 95A3371D4879057FAEB2E573CCE8A7F5
passed 10101010101010101010101010101010 10101010101010101010101010101010 80AF7861CA5855FBED523345D36619EC
passed 20202020202020202020202020202020 20202020202020202020202020202020 82E9D82550AECD0E0BB1B63E4B30CEC3
passed 40404040404040404040404040404040 40404040404040404040404040404040 C80C04BA36ED0DA52B3E6CB430617FAC
passed 80808080808080808080808080808080 80808080808080808080808080808080 41305D0632AC493419B04F3BCDBA6AE4
passed FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF B99D80EF798362ACEB9E960AAE7EECC2
passed 0123456789ABCDEFFEDCBA98765432100011223344556677 0123456789ABCDEFFEDCBA9876543210 6DC2DBDAC3C563E522F5A75942B8AFAC
passed 800000000000000000000000000000000000000000000000 00000000000000000000000000000000 F9BA9C6E7E3C86FAE4BEB607F387548E
passed 000000000000000000000000000000000000000000000001 00000000000000000000000000000000 5BC2C08F01C0CDC2F983073CBE9194D2
passed 000000000000000000000000000000000000000000000000 80000000000000000000000000000000 AE56BF59874ED4DBD7B905878894ADEE
passed 000000000000000000000000000000000000000000000000 00000000000000000000000000000001 D53236B0CDE20C26F57675A7405A9F98
passed 000000000000000000000000000000000000000000000000 00000000000000000000000000000000 D5526B5E6A1E3DF23AD8ECAF20F281D0
passed 010101010101010101010101010101010101010101010101 01010101010101010101010101010101 6E4C91AB71707075F375FFB7B3D27328
passed 020202020202020202020202020202020202020202020202 02020202020202020202020202020202 D686D2A6F3BBBC5E703528FD4B1DBA8F
passed 040404040404040404040404040404040404040404040404 04040404040404040404040404040404 ADE1730DA6F15693FD9F063DFC8EC4D1
passed 080808080808080808080808080808080808080808080808 08080808080808080808080808080808 6A3FCA9070151FF14142B1700BE075EB
passed 101010101010101010101010101010101010101010101010 10101010101010101010101010101010 773EC2820CCD29CA650DEA05E04CEB80
passed 202020202020202020202020202020202020202020202020 20202020202020202020202020202020 531A8B8F5F1228E16B57E5365A1FB02B
passed 404040404040404040404040404040404040404040404040 40404040404040404040404040404040 C0166DB2A70DF611921E7F0AB0E0F15D
passed 808080808080808080808080808080808080808080808080 80808080808080808080808080808080 70F3361D505A220B1C2328EBE32ED731
passed FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF F275975CCC163ED53AA0510443239638
passed 0123456789ABCDEFFEDCBA987654321000112233445566778899AABBCCDDEEFF 0123456789ABCDEFFEDCBA9876543210 2F4792014AE2D9B812ADBAC663DC762B
passed 8000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000 9250C9771F5A5A8612400AA917491263
passed 0000000000000000000000000000000000000000000000000000000000000001 00000000000000000000000000000000 1A6AED07EC57E4373E988BFBB396406F
passed 0000000000000000000000000000000000000000000000000000000000000000 80000000000000000000000000000000 209ACF63CE6DFB56B1F9821DDBFE86E3
passed 0000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000001 678FFFFDCE3177605F9320FEC4D30B5E
passed 0000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000 C20857DD9106DDDE286EC59FA98D77CC
passed 0101010101010101010101010101010101010101010101010101010101010101 01010101010101010101010101010101 15C28D4EC27D8BEDDD8E6B3745A9A261
passed 0202020202020202020202020202020202020202020202020202020202020202 02020202020202020202020202020202 5279DA1773C078835D506B25FED6513E
passed 0404040404040404040404040404040404040404040404040404040404040404 04040404040404040404040404040404 7AED38F56F62FC75F7DB88F7E59D0B02
passed 0808080808080808080808080808080808080808080808080808080808080808 08080808080808080808080808080808 6EB3C2BC1AC20926E860E688786DB872
passed 1010101010101010101010101010101010101010101010101010101010101010 10101010101010101010101010101010 54A8718B4DD1A03B1A4ED06C30B9E6AB
passed 2020202020202020202020202020202020202020202020202020202020202020 20202020202020202020202020202020 A876FA5538F926B373702DABF33025B6
passed 4040404040404040404040404040404040404040404040404040404040404040 40404040404040404040404040404040 B71AB43F56E09592E69E315E7CD06E8A
passed 8080808080808080808080808080808080808080808080808080808080808080 80808080808080808080808080808080 E975FB1435D92A0CF3E1A2487774D699
passed FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF 6C833E3962286C0DE0395446ED30F646
CHAM validation suite running...
Testing SymmetricCipher algorithm CHAM-64/ECB.
....................
Testing SymmetricCipher algorithm CHAM-128/ECB.
........................................
Testing SymmetricCipher algorithm CHAM-64/CTR.
..............................
Testing SymmetricCipher algorithm CHAM-128/CTR.
............................................................
Tests complete. Total tests = 150. Failed tests = 0.
HIGHT validation suite running...
Testing SymmetricCipher algorithm HIGHT/ECB.
..............................
Testing SymmetricCipher algorithm HIGHT/CBC.
................
Testing SymmetricCipher algorithm HIGHT/CTR.
............................................................................................................................................................
Tests complete. Total tests = 202. Failed tests = 0.
LEA validation suite running...
Testing SymmetricCipher algorithm LEA-128/ECB.
............................................................
Testing SymmetricCipher algorithm LEA-128/CTR.
..........................................................................................
Testing SymmetricCipher algorithm LEA-128/CBC.
............................................................
Tests complete. Total tests = 210. Failed tests = 0.
SIMECK validation suite running...
Testing SymmetricCipher algorithm SIMECK-32/ECB.
....................
Testing SymmetricCipher algorithm SIMECK-32/CTR.
..............................
Testing SymmetricCipher algorithm SIMECK-64/ECB.
....................
Testing SymmetricCipher algorithm SIMECK-64/CTR.
..............................
Tests complete. Total tests = 100. Failed tests = 0.
SIMON validation suite running...
Testing SymmetricCipher algorithm SIMON-64/ECB.
................................
Testing SymmetricCipher algorithm SIMON-64/CBC.
............................
Testing SymmetricCipher algorithm SIMON-64/CTR.
..........................................
Testing SymmetricCipher algorithm SIMON-128/ECB.
................................................
Testing SymmetricCipher algorithm SIMON-128/CBC.
..........................................
Testing SymmetricCipher algorithm SIMON-128/CTR.
...............................................................
Tests complete. Total tests = 255. Failed tests = 0.
SPECK validation suite running...
Testing SymmetricCipher algorithm SPECK-64/ECB.
................................
Testing SymmetricCipher algorithm SPECK-64/CBC.
............................
Testing SymmetricCipher algorithm SPECK-64/CTR.
..........................................
Testing SymmetricCipher algorithm SPECK-128/ECB.
................................................
Testing SymmetricCipher algorithm SPECK-128/CBC.
..........................................
Testing SymmetricCipher algorithm SPECK-128/CTR.
...............................................................
Tests complete. Total tests = 255. Failed tests = 0.
Camellia validation suite running...
passed: Algorithm key lengths
passed 0123456789ABCDEFFEDCBA9876543210 0123456789ABCDEFFEDCBA9876543210 67673138549669730857065648EABE43
passed 80000000000000000000000000000000 00000000000000000000000000000000 6C227F749319A3AA7DA235A9BBA05A2C
passed 00000000000000000000000000000001 00000000000000000000000000000000 41E0E6DC2DDEC65D8B8120E60977B82D
passed 00000000000000000000000000000000 80000000000000000000000000000000 07923A39EB0A817D1C4D87BDB82D1F1C
passed 00000000000000000000000000000000 00000000000000000000000000000001 F5574ACC3148DFCB9015200631024DF9
passed 00000000000000000000000000000000 00000000000000000000000000000000 3D028025B156327C17F762C1F2CBCA71
passed 01010101010101010101010101010101 01010101010101010101010101010101 637084CB1120D6F25DB618893040AA27
passed 02020202020202020202020202020202 02020202020202020202020202020202 612834AAC9EF906BAEAA076E1C75179D
passed 04040404040404040404040404040404 04040404040404040404040404040404 B24FAF8A579E4EFE986571FB2F68B5B4
passed 08080808080808080808080808080808 08080808080808080808080808080808 3E5CAFBB70545AABB1109293A1C44C14
passed 10101010101010101010101010101010 10101010101010101010101010101010 E1FA5FD3F40B766BBE3DF469AF41B420
passed 20202020202020202020202020202020 20202020202020202020202020202020 7E724027BB2F591C63254D936FCC4B43
passed 40404040404040404040404040404040 40404040404040404040404040404040 538ADCBE104A3483B3C2A3D8CE72FBD6
passed 80808080808080808080808080808080 80808080808080808080808080808080 AA7627F70F6B54C217C3EF232D362459
passed FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF 25DD9EB9DD67FBC6E8431F56F4FBE651
passed 0123456789ABCDEFFEDCBA98765432100011223344556677 0123456789ABCDEFFEDCBA9876543210 B4993401B3E996F84EE5CEE7D79B09B9
passed 800000000000000000000000000000000000000000000000 00000000000000000000000000000000 1B6220D365C2176C1D41A5826520FCA1
passed 000000000000000000000000000000000000000000000001 00000000000000000000000000000000 E37577F71E0E643C4D3F55219ABA1394
passed 000000000000000000000000000000000000000000000000 80000000000000000000000000000000 3EB6CC5618EFC98455B5992050D474E7
passed 000000000000000000000000000000000000000000000000 00000000000000000000000000000001 BA9AE89FDDCE4B51131E17C4D65CE587
passed 000000000000000000000000000000000000000000000000 00000000000000000000000000000000 56E1E129CA5C02C7F9AC6AFDEF86ADC3
passed 010101010101010101010101010101010101010101010101 01010101010101010101010101010101 8F764397C10BE84BA876CEEFA4225BFF
passed 020202020202020202020202020202020202020202020202 02020202020202020202020202020202 60B00674BFD444D07B5A19851E6151CD
passed 040404040404040404040404040404040404040404040404 04040404040404040404040404040404 81B26FF4F6B4377CC555873504B3A38B
passed 080808080808080808080808080808080808080808080808 08080808080808080808080808080808 A2AA1C6693DC2B70D75C9B39B9B214D0
passed 101010101010101010101010101010101010101010101010 10101010101010101010101010101010 A907BFDAEEF8C81D05855235E8D3BE08
passed 202020202020202020202020202020202020202020202020 20202020202020202020202020202020 87F8EA30332036F17CEAC0097CE33BC1
passed 404040404040404040404040404040404040404040404040 40404040404040404040404040404040 A2C32EA499E41A248565253BACC11E3B
passed 808080808080808080808080808080808080808080808080 80808080808080808080808080808080 F602BA7F515B082983B8F7A27F92408F
passed FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF 3F8D5676F51CE23DC3BDB627F8B3883E
passed 0123456789ABCDEFFEDCBA987654321000112233445566778899AABBCCDDEEFF 0123456789ABCDEFFEDCBA9876543210 9ACC237DFF16D76C20EF7C919E3A7509
passed 8000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000 2136FABDA091DFB5171B94B8EFBB5D08
passed 0000000000000000000000000000000000000000000000000000000000000001 00000000000000000000000000000000 AFCD38B195E0A736304E89B9AE3019D3
passed 0000000000000000000000000000000000000000000000000000000000000000 80000000000000000000000000000000 B0C6B88AEA518AB09E847248E91B1B9D
passed 0000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000001 9CDB269B5D293BC5DB9C55B057D9B591
passed 0000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000 396154111ADEFC500CF6E5C99038BC17
passed 0101010101010101010101010101010101010101010101010101010101010101 01010101010101010101010101010101 438D0C2E7E86869B56EBA23B66086A01
passed 0202020202020202020202020202020202020202020202020202020202020202 02020202020202020202020202020202 D4F553BFA794F55EF3B7A578629F6DEA
passed 0404040404040404040404040404040404040404040404040404040404040404 04040404040404040404040404040404 5E858730ABC9823A93CA4CAB67F0B423
passed 0808080808080808080808080808080808080808080808080808080808080808 08080808080808080808080808080808 F9A9C1540AE1B314DBEDF9A49054DC9D
passed 1010101010101010101010101010101010101010101010101010101010101010 10101010101010101010101010101010 6693FC130669F194F81E8D175194DDA2
passed 2020202020202020202020202020202020202020202020202020202020202020 20202020202020202020202020202020 F3E1FDA6B9C8314799F4654C29F1C690
passed 4040404040404040404040404040404040404040404040404040404040404040 40404040404040404040404040404040 4A30476F1141FBF303ED63FCD3CB0536
passed 8080808080808080808080808080808080808080808080808080808080808080 80808080808080808080808080808080 0C765AA494E048FC8BB23139F2124CB6
passed FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF 4F05F28CA23EEAE205B67B1C95CD5280
Salsa validation suite running...
Testing SymmetricCipher algorithm Salsa20.
........................................
Testing SymmetricCipher algorithm XSalsa20.
................................................................................................................................................................................................
Tests complete. Total tests = 232. Failed tests = 0.
ChaCha validation suite running...
Testing SymmetricCipher algorithm ChaCha.
.....................................................................................................................
Tests complete. Total tests = 117. Failed tests = 0.
ChaCha-TLS validation suite running...
Testing SymmetricCipher algorithm ChaChaTLS.
.......................................
Tests complete. Total tests = 39. Failed tests = 0.
Sosemanuk validation suite running...
Testing SymmetricCipher algorithm Sosemanuk.
....
Tests complete. Total tests = 4. Failed tests = 0.
Rabbit validation suite running...
Testing SymmetricCipher algorithm Rabbit.
......................................................................................................................................................................................................................................................................................................................................................................................................
Testing SymmetricCipher algorithm RabbitWithIV.
......................................................................................................................................................................................................................................................................................................................................................................................................
Tests complete. Total tests = 780. Failed tests = 0.
HC-128 validation suite running...
Testing SymmetricCipher algorithm HC-128.
................................................................................................................................................................................................................................................
Tests complete. Total tests = 240. Failed tests = 0.
HC-256 validation suite running...
Testing SymmetricCipher algorithm HC-256.
...................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
Tests complete. Total tests = 867. Failed tests = 0.
Testing SymmetricCipher algorithm SEED/ECB.
........
Tests complete. Total tests = 8. Failed tests = 0.
Testing SymmetricCipher algorithm Threefish-256(256)/ECB.
....
Testing SymmetricCipher algorithm Threefish-512(512)/ECB.
............
Testing SymmetricCipher algorithm Threefish-1024(1024)/ECB.
....
Tests complete. Total tests = 20. Failed tests = 0.
Testing SymmetricCipher algorithm Kalyna-128/ECB.
....
Testing SymmetricCipher algorithm Kalyna-256/ECB.
....
Testing SymmetricCipher algorithm Kalyna-512/ECB.
..
Testing SymmetricCipher algorithm Kalyna-128/CBC.
....
Testing SymmetricCipher algorithm Kalyna-256/CBC.
....
Testing SymmetricCipher algorithm Kalyna-512/CBC.
..
Tests complete. Total tests = 20. Failed tests = 0.
Testing SymmetricCipher algorithm SM4/ECB.
..........................................
Testing SymmetricCipher algorithm SM4/CBC.
............................................................
Tests complete. Total tests = 102. Failed tests = 0.
VMAC validation suite running...
Testing MAC algorithm VMAC(AES)-64.
...........
Testing MAC algorithm VMAC(AES)-128.
...........
Tests complete. Total tests = 22. Failed tests = 0.
AES/CCM validation suite running...
Testing AuthenticatedSymmetricCipher algorithm AES/CCM.
..................................
Tests complete. Total tests = 34. Failed tests = 0.
AES/GCM validation suite running...
2K tables:
Testing AuthenticatedSymmetricCipher algorithm AES/GCM.
......................
Tests complete. Total tests = 22. Failed tests = 0.
64K tables:
Testing AuthenticatedSymmetricCipher algorithm AES/GCM.
......................
Tests complete. Total tests = 22. Failed tests = 0.
AES/XTS validation suite running...
Testing SymmetricCipher algorithm AES/XTS.
........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
Tests complete. Total tests = 1000. Failed tests = 0.
CMAC validation suite running...
Testing MAC algorithm CMAC(AES).
.....
Testing MAC algorithm CMAC(DES-EDE3).
....
Tests complete. Total tests = 9. Failed tests = 0.
Testing AuthenticatedSymmetricCipher algorithm AES/EAX.
............
Tests complete. Total tests = 12. Failed tests = 0.
BlumBlumShub validation suite running...
passed 49ea2cfdb01064a0bbb92af101dac18a94f7b7ce
passed 2af101dac18a94f7b7ce
passed 744548aeacb70edfafd7d50e8e2983756b2746a1
DH validation suite running...
passed simple key agreement domain parameters validation
passed simple key agreement
x25519 validation suite running...
passed simple key agreement domain parameters validation
passed simple key agreement
passed checking invalid signature
passed brainpoolP512r1 using SHA-512
passed signature key validation
passed signature and verification
passed checking invalid signature
ESIGN validation suite running...
passed signature key validation
passed signature and verification
passed checking invalid signature
passed verification check against test vector
Generating signature key from seed...
passed signature key validation
passed signature and verification
passed checking invalid signature
x25519 validation suite running...
passed simple key agreement domain parameters validation
passed simple key agreement
ed25519 validation suite running...
passed signature key validation
passed signature and verification
passed checking invalid signature
passed verification check against test vector
Testing NaCl library functions...
passed crypto_box, crypto_box_beforenm, crypto_box_afternm
passed crypto_box_open, crypto_box_open_afternm
passed crypto_box_keypair pairwise consistency
passed crypto_sign, crypto_sign_open, crypto_sign_keypair
passed crypto_sign_keypair pairwise consistency
All tests passed!
Seed used was 1720959419
Test started at Sun Jul 14 12:16:59 2024
Test ended at Sun Jul 14 12:19:01 2024
```
</details> | Some cryptest assertions didn't pass on Windows | https://api.github.com/repos/weidai11/cryptopp/issues/1281/comments | 0 | 2024-07-14T12:09:25Z | 2024-07-18T16:49:47Z | https://github.com/weidai11/cryptopp/issues/1281 | 2,407,406,115 | 1,281 |
[
"weidai11",
"cryptopp"
] | While developing support for an external app that uses the HC-256 cipher, I noticed inconsistencies with the `CryptoPP::HC256` algorithm's output. Further digging showed that when either the key or IV contain non-repeating bytes (e.g. not just all `00` or `36`...), the output does not match that of other libraries, or the original reference library.
I have tested against BouncyCastle and the [original `hc256.c` ECRYPT source](https://www.ecrypt.eu.org/stream/p3ciphers/hc/hc256_p3source.zip) (which I had to use instead of CryptoPP for this project).
Compiled CryptoPP 8.9.0 using Visual Studio (x64) on Windows 10.
I have found the problem seems to be with the endian flip happening with the key and IV at these two locations. Such an endian flip is not present in BouncyCastle or `hc256.c`.
https://github.com/weidai11/cryptopp/blob/60f81a77e0c9a0e7ffc1ca1bc438ddfa2e43b78e/hc256.cpp#L107-L111
https://github.com/weidai11/cryptopp/blob/60f81a77e0c9a0e7ffc1ca1bc438ddfa2e43b78e/hc256.cpp#L135-L139
If I replace the loop bodies with these respective changes, the unit output matches that of BouncyCastle and `hc256.c`.
```c++
m_key[i >> 2] |= ((word32)userKey[i] << (8 * (i & 0x3)));
...
m_iv[i >> 2] |= ((word32)iv[i] << (8 * (i & 0x3)));
```
Here is a test program that uses a BouncyCastle test vector to show the mismatch. The code throws an assertion with CryptoPP 8.9.0, and passes with the above changes.
```c++
#include <cryptopp/hc256.h>
int main()
{
auto key = std::vector<uint8_t>{
0x00, 0x53, 0xA6, 0xF9, 0x4C, 0x9F, 0xF2, 0x45, 0x98, 0xEB, 0x3E, 0x91, 0xE4, 0x37, 0x8A, 0xDD,
0x30, 0x83, 0xD6, 0x29, 0x7C, 0xCF, 0x22, 0x75, 0xC8, 0x1B, 0x6E, 0xC1, 0x14, 0x67, 0xBA, 0x0D
};
auto iv = std::vector<uint8_t>{
0x0D, 0x74, 0xDB, 0x42, 0xA9, 0x10, 0x77, 0xDE, 0x45, 0xAC, 0x13, 0x7A, 0xE1, 0x48, 0xAF, 0x16,
0x7D, 0xE4, 0x4B, 0xB2, 0x19, 0x80, 0xE7, 0x4E, 0xB5, 0x1C, 0x83, 0xEA, 0x51, 0xB8, 0x1F, 0x86
};
auto buffer = std::vector<uint8_t>(0x40, 0x00);
// BouncyCastle Set 6, vector# 0
// https://github.com/bcgit/bc-java/blob/0520ebcd3291d6d3176ea25c571f1c7e0a963847/core/src/test/java/org/bouncycastle/crypto/test/HCFamilyTest.java#L104-L112
// https://github.com/bcgit/bc-csharp/blob/f5432325fbeadade37ec2542a44b3702395c7650/crypto/test/data/hc256/hc256/ecrypt_HC-256_256K_256IV.txt#L3151-L3159
auto expected = std::vector<uint8_t>{
0x23, 0xD9, 0xE7, 0x0A, 0x45, 0xEB, 0x01, 0x27, 0x88, 0x4D, 0x66, 0xD9, 0xF6, 0xF2, 0x3C, 0x01,
0xD1, 0xF8, 0x8A, 0xFD, 0x62, 0x92, 0x70, 0x12, 0x72, 0x47, 0x25, 0x6C, 0x1F, 0xFF, 0x91, 0xE9,
0x1A, 0x79, 0x7B, 0xD9, 0x8A, 0xDD, 0x23, 0xAE, 0x15, 0xBE, 0xE6, 0xEE, 0xA3, 0xCE, 0xFD, 0xBF,
0xA3, 0xED, 0x6D, 0x22, 0xD9, 0xC4, 0xF4, 0x59, 0xDB, 0x10, 0xC4, 0x0C, 0xDF, 0x4F, 0x4D, 0xFF
};
CryptoPP::HC256::Encryption hc256;
hc256.SetKeyWithIV(key.data(), key.size(), iv.data(), iv.size());
hc256.ProcessData(buffer.data(), buffer.data(), buffer.size());
CRYPTOPP_ASSERT(CRYPTOPP_VERSION >= 890);
CRYPTOPP_ASSERT(memcmp(buffer.data(), expected.data(), buffer.size()) == 0);
}
```
Furthermore, [the sample on the wiki](https://www.cryptopp.com/wiki/HC-128#HC-256) is not decryptable with BouncyCastle.
```
Key: CBCBA550FE1A5C34E0C4D6A14D056A08032EA11CF700BD7B9D409B68DC47B9B7
IV: 2E58581CFD129ACE30BD1F86739C713A867550A3DD6D9E0886F63C01B6F9531F
Plain: HC-256 stream cipher test
CryptoPP Cipher: 957BD81955B68A34A4C151D73F89E837945C364CE5B2942CC2
BouncyCastle Cipher: 3531AD8ADC1DEFED1C9D3B705D8B9E87063D1D05E40C19ADB2
```
The `CryptoPP::HC128` algorithm appears fine; it also does not do endian flipping of the key and IV, instead explicitly using `GetUserKey(LITTLE_ENDIAN_ORDER ...)`. | HC-256 Inconsistent with Other Libraries | https://api.github.com/repos/weidai11/cryptopp/issues/1280/comments | 7 | 2024-06-27T15:42:00Z | 2024-08-09T13:30:56Z | https://github.com/weidai11/cryptopp/issues/1280 | 2,378,500,043 | 1,280 |
[
"weidai11",
"cryptopp"
] | OS: Windows 10 19045.4529 x64
Crypto++ version: on commit ([Guard use of ModularSquareRoot (GH](https://github.com/weidai11/cryptopp/commit/9aa07aebbdc62461c3ac32f958d7c3ab89ff6f73) https://github.com/weidai11/cryptopp/issues/1249[)](https://github.com/weidai11/cryptopp/commit/9aa07aebbdc62461c3ac32f958d7c3ab89ff6f73)
Compiler: MSVC 17.9.34607.119 (x86)
Code:
```c++
struct KeyPair {
std::string publicKey, privateKey;
};
// size if 1024, 2048 or 4096
inline KeyPair GenerateRsaKeyPair(const unsigned int size)
{
KeyPair rsaKeyPair;
CryptoPP::AutoSeededRandomPool asrp;
CryptoPP::RSA::PrivateKey rsaPrivateKey;
// next line causes debug break
rsaPrivateKey.GenerateRandomWithKeySize(asrp, size);
CryptoPP::RSA::PublicKey rsaPublicKey(rsaPrivateKey);
CryptoPP::StringSink rawPrivateKeySink(rsaKeyPair.privateKey);
rsaPrivateKey.DEREncode(rawPrivateKeySink);
CryptoPP::StringSink rawPublicKeySink(rsaKeyPair.publicKey);
rsaPublicKey.DEREncode(rawPublicKeySink);
return rsaKeyPair;
}
```
When i debug my application, this function calls debug break here:
```c++
// nbtheory.cpp:526
Integer CRT(const Integer &xp, const Integer &p, const Integer &xq, const Integer &q, const Integer &u)
{
// Callers must ensure p and q are prime, GH #1249
CRYPTOPP_ASSERT(IsPrime(p) && IsPrime(q));
// isn't operator overloading great?
return p * (u * (xq-xp) % q) + xp;
/*
Integer t1 = xq-xp;
cout << hex << t1 << endl;
Integer t2 = u * t1;
cout << hex << t2 << endl;
Integer t3 = t2 % q;
cout << hex << t3 << endl;
Integer t4 = p * t3;
cout << hex << t4 << endl;
Integer t5 = t4 + xp;
cout << hex << t5 << endl;
return t5;
*/
}
```
`AutoSeededX917RNG<CryptoPP::AES> asrp;` doesn't work too.
Expected behavior: `rsaPrivateKey.GenerateRandomWithKeySize` doesn't cause debug break.
Thanks! | GenerateRandomWithKeySize calls debug break | https://api.github.com/repos/weidai11/cryptopp/issues/1279/comments | 1 | 2024-06-23T15:47:06Z | 2024-06-23T16:13:01Z | https://github.com/weidai11/cryptopp/issues/1279 | 2,368,646,631 | 1,279 |
[
"weidai11",
"cryptopp"
] | When we compile a universal binary (x86_64 + arm64) on an Intel macOS, a warning message shows, but compilation and validation tests succeed. Is this a deeper problem or just a flag validation problem? Anyway, this compilation should succeed without warnings.
Command:
```shell
CXXFLAGS="-DNDEBUG -g2 -O3 -stdlib=libc++ -arch x86_64 -arch arm64" make -j 4
```
Message:
```shell
Using testing flags: -DNDEBUG -g2 -O3 -stdlib=libc++ -arch x86_64 -arch arm64
Running make again to see what failed
error: unknown target CPU 'armv8-a'
note: valid target CPU values are: nocona, core2, penryn, bonnell, atom, silvermont, slm, goldmont, goldmont-plus, tremont, nehalem, corei7, westmere, sandybridge, corei7-avx, ivybridge, core-avx-i, haswell, core-avx2, broadwell, skylake, skylake-avx512, skx, cascadelake, cooperlake, cannonlake, icelake-client, rocketlake, icelake-server, tigerlake, sapphirerapids, alderlake, knl, knm, k8, athlon64, athlon-fx, opteron, k8-sse3, athlon64-sse3, opteron-sse3, amdfam10, barcelona, btver1, btver2, bdver1, bdver2, bdver3, bdver4, znver1, znver2, znver3, x86-64, x86-64-v2, x86-64-v3, x86-64-v4
c++ -DCRYPTOPP_DISABLE_ASM -fPIC -pthread -fno-common -pipe -DNDEBUG -g2 -O3 -stdlib=libc++ -arch x86_64 -arch arm64 -c cryptlib.cpp
...
```
OS: macOS 12.7.5
CPU: 1.6 GHz Dual-Core Intel Core i5
Compiler: Apple clang version 14.0.0 (clang-1400.0.29.202)
Version: master, most recent commit on Apr 25, 2024
| Warning when compiling universal binary (x86_64 + arm64) on macOS | https://api.github.com/repos/weidai11/cryptopp/issues/1277/comments | 0 | 2024-05-31T15:17:08Z | 2024-05-31T15:45:29Z | https://github.com/weidai11/cryptopp/issues/1277 | 2,328,074,512 | 1,277 |
[
"weidai11",
"cryptopp"
] | I have tried to compile the library in a Windows environment but I have not succeeded, so far I have tried several ways but it gives me an error, any suggestions on how I can do it, thanks in advance, I have Windows 11 and Qt creator installed, precisely to use it in I want to compile the library in that environment.
| How can I compile for windows with mingw? | https://api.github.com/repos/weidai11/cryptopp/issues/1276/comments | 1 | 2024-05-25T16:49:28Z | 2024-06-10T14:01:03Z | https://github.com/weidai11/cryptopp/issues/1276 | 2,317,133,527 | 1,276 |
[
"weidai11",
"cryptopp"
] | Maybe already reported, just FYI.
With stringop-overflow warning enabled, I get one (only one) warning when building 8.9.0:
esign.cpp: In member function ‘virtual void CryptoPP::InvertibleESIGNFunction::GenerateRandom(CryptoPP::RandomNumberGenerator&, const CryptoPP::NameValuePairs&)’:
esign.cpp:115:28: warning: ‘void* memcpy(void*, const void*, size_t)’ specified bound 18446744073709551612 exceeds maximum object size 9223372036854775807 [-Wstringop-overflow=]
115 | std::memcpy(seed + 4, seedParam.begin(), seedParam.size());
| ~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
esign.cpp:115:28: warning: ‘void* memcpy(void*, const void*, size_t)’ specified bound 18446744073709551612 exceeds maximum object size 9223372036854775807 [-Wstringop-overflow=]
Thanks!
Vincent
| Warning in esign.cpp with 8.9.0 and gcc-14.1 | https://api.github.com/repos/weidai11/cryptopp/issues/1275/comments | 0 | 2024-05-08T17:12:29Z | 2024-05-08T17:12:29Z | https://github.com/weidai11/cryptopp/issues/1275 | 2,286,068,394 | 1,275 |
[
"weidai11",
"cryptopp"
] | > Assertion failed:integer.cpp(3049):Integer
When I use cryptopp library to encrypt and decrypt, this problem occured suddenly. | Assertion failed: integer.cpp(3049):Integer | https://api.github.com/repos/weidai11/cryptopp/issues/1273/comments | 1 | 2024-04-19T09:41:59Z | 2024-04-19T12:34:19Z | https://github.com/weidai11/cryptopp/issues/1273 | 2,252,548,473 | 1,273 |
[
"weidai11",
"cryptopp"
] | ### Crypto++ Issue Report
**Compilation issue with clang on X86**
ILNS_9CipherDirE0ENS_8Rijndael3EncEEES9_EEEE[_ZTVN8CryptoPP13AlgorithmImplINS_20ConcretePolicyHolderINS_5EmptyENS_22AdditiveCipherTemplateINS_20AbstractPolicyHolderINS_28AdditiveCipherAbstractPolicyENS_14CTR_ModePolicyEEEEES5_EENS_36CipherModeFinalTemplate_CipherHolderINS_16BlockCipherFinalILNS_9CipherDirE0ENS_8Rijndael3EncEEES9_EEEE]+0x150): undefined reference to `non-virtual thunk to CryptoPP::AdditiveCipherTemplate<CryptoPP::AbstractPolicyHolder<CryptoPP::AdditiveCipherAbstractPolicy, CryptoPP::CTR_ModePolicy> >::AlgorithmProvider() const'
/usr/bin/ld: ../../../lib/libsequencerapi.a(CryptoRNG.cpp.o): in function `CryptoPP::Hash_DRBG<CryptoPP::SHA512, 32u, 111u>::AlgorithmProvider() const':
/local/mnt/workspace/client_clang/sources/third_party/crypto++/inc/../src/drbg.h:236: undefined reference to `CryptoPP::SHA512::AlgorithmProvider() const'
| Compilation issue with clang on X86 | https://api.github.com/repos/weidai11/cryptopp/issues/1272/comments | 0 | 2024-04-15T16:45:19Z | 2024-04-15T16:45:19Z | https://github.com/weidai11/cryptopp/issues/1272 | 2,244,157,717 | 1,272 |
[
"weidai11",
"cryptopp"
] | gpg: Signature made Sun 01 Oct 2023 12:53:50 PM EDT
gpg: using RSA key B8CC19802062211A508B2F5CCE0586AF1F8E37BD
gpg: Good signature from "Jeffrey Walton (Crypto++ Release) <noloader@gmail.com>" [expired]
gpg: Note: This key has expired!
Primary key fingerprint: B8CC 1980 2062 211A 508B 2F5C CE05 86AF 1F8E 37BD | PGP signing key has expired | https://api.github.com/repos/weidai11/cryptopp/issues/1271/comments | 0 | 2024-04-11T13:38:36Z | 2024-04-11T13:38:36Z | https://github.com/weidai11/cryptopp/issues/1271 | 2,237,751,945 | 1,271 |
[
"weidai11",
"cryptopp"
] | # Problem
I am using Donna Functions to generate two key pair and generate shared key for both side with function [`curve25519_mult`](https://github.com/weidai11/cryptopp/blob/782057f5f18fbdad2bd2b291fb1ec558a8ab8225/donna.h#L57) .But the key generated twice is not the same.
- I searched through the Internet for answer,not solved.
- I checked my own code,no bug found.
- I tested signing and verification.They are OK.
What is the problem with the code below?
# Environment
- system and version (Windows 10 Professional x64)
- version of the Crypto++ library (Crypto++ 8.90, Master)
- built the library by Visual Studio 2022
# Code
```c++
#include <donna.h>
#include <osrng.h>
#include <cassert>
int main()
{
static CryptoPP::AutoSeededRandomPool prng;
//Generate random private keys
unsigned char private_key1[32],private_key2[32];
prng.GenerateBlock(private_key1, 32);
prng.GenerateBlock(private_key2, 32);
//Generate public keys
unsigned char public_key1[32],public_key2[32];
CryptoPP::Donna::ed25519_publickey(public_key1, private_key1);
CryptoPP::Donna::ed25519_publickey(public_key2, private_key2);
//Generate shared key
unsigned char shared_secret1[32],shared_secret2[32];
CryptoPP::Donna::curve25519_mult(shared_secret1, private_key1, publicKey2);
CryptoPP::Donna::curve25519_mult(shared_secret2, private_key2, publicKey1);
//Assertion failed!
assert(::memcmp(shared_secret1,shared_secret2,32) == 0);
}
``` | [x25519] donna function `curve25519_mult` generated different shared key | https://api.github.com/repos/weidai11/cryptopp/issues/1270/comments | 1 | 2024-04-08T05:15:25Z | 2024-04-08T07:38:27Z | https://github.com/weidai11/cryptopp/issues/1270 | 2,230,277,955 | 1,270 |
[
"weidai11",
"cryptopp"
] | I typically never use Crypto++, but I had to yesterday, and I then experienced a strange behavior that I felt I had to somehow report. Having read your [security policy](https://github.com/weidai11/cryptopp/security/policy), I decided that the appropriate course of action was to open an issue here.
### Background
I used the default Crypto++ package provided by [Ubuntu 20.04.6 LTS (Focal Fossa)](https://releases.ubuntu.com/focal/) running on a computer with a 64-bit Intel CPU.
More specifically, Crypto++ was installed on the machine via <code>apt</code> as follows:
```console
$ sudo apt update && sudo apt upgrade
(..)
$ sudo apt install libcrypto++-dev
(..)
libcrypto++-dev is already the newest version (5.6.4-9build1).
```
The package version 5.6.4 leads me to think that it installs the (old) v5.6.4 release of Crypto++ from [this GitHub repository](https://github.com/weidai11/cryptopp), although it is not entirely clear from the metadata for the package.
### The issue
When using Crypto++ as provided by the above package, it seems <code>ECP::ScalarMultiply()</code> may miscompute. Specifically, it seems to miscompute if the scalar is on [2, 32), i.e. of bit length less than or equal to 5. This would appear to be related to the difference in behavior induced by the branching on [this line](https://github.com/weidai11/cryptopp/blob/782057f5f18fbdad2bd2b291fb1ec558a8ab8225/ecp.cpp#L387) in the source code for Crypto++.
To exemplify, I obtain the below result:
```console
$ g++ main.cpp -lcryptopp -o test
$ ./test
Q1.x = 33306590390930540189669946118275349837741820479536661896440526521039379673897.
Q1.y = 51671163428562425671907826722938384860953039014408454870632045822359784767650.
>> Q1 is *NOT* as expected.
>> Q1 is *NOT* on E.
Q2.x = 33898744863829483362161709717034397769364896634277352921440311777960767108802.
Q2.y = 23483645583050324501141112153509270605088748325709409281081826839369927198174.
>> Q2 is as expected.
>> Q2 is on E.
>> T1 is equal to T2 for d = 1.
>> T1 is *NOT* equal to T2 for d = 2.
>> T1 is *NOT* equal to T2 for d = 3.
>> T1 is *NOT* equal to T2 for d = 4.
>> T1 is *NOT* equal to T2 for d = 5.
>> T1 is *NOT* equal to T2 for d = 6.
>> T1 is *NOT* equal to T2 for d = 7.
>> T1 is *NOT* equal to T2 for d = 8.
>> T1 is *NOT* equal to T2 for d = 9.
>> T1 is *NOT* equal to T2 for d = 10.
>> T1 is *NOT* equal to T2 for d = 11.
>> T1 is *NOT* equal to T2 for d = 12.
>> T1 is *NOT* equal to T2 for d = 13.
>> T1 is *NOT* equal to T2 for d = 14.
>> T1 is *NOT* equal to T2 for d = 15.
>> T1 is *NOT* equal to T2 for d = 16.
>> T1 is *NOT* equal to T2 for d = 17.
>> T1 is *NOT* equal to T2 for d = 18.
>> T1 is *NOT* equal to T2 for d = 19.
>> T1 is *NOT* equal to T2 for d = 20.
>> T1 is *NOT* equal to T2 for d = 21.
>> T1 is *NOT* equal to T2 for d = 22.
>> T1 is *NOT* equal to T2 for d = 23.
>> T1 is *NOT* equal to T2 for d = 24.
>> T1 is *NOT* equal to T2 for d = 25.
>> T1 is *NOT* equal to T2 for d = 26.
>> T1 is *NOT* equal to T2 for d = 27.
>> T1 is *NOT* equal to T2 for d = 28.
>> T1 is *NOT* equal to T2 for d = 29.
>> T1 is *NOT* equal to T2 for d = 30.
>> T1 is *NOT* equal to T2 for d = 31.
>> T1 is equal to T2 for d = 32.
>> T1 is equal to T2 for d = 33.
>> T1 is equal to T2 for d = 34.
>> T1 is equal to T2 for d = 4838386420901692723041175965060989195194280026704430236348655611663611748562.
```
The source code in <code>main.cpp</code> is as follows:
```c++
#include <iostream>
using std::cout;
using std::endl;
#include "cryptopp/ecp.h"
using CryptoPP::Integer;
using CryptoPP::ECPPoint;
using CryptoPP::ECP;
int main() {
const Integer p("68563679381982577622739666783671143994995151030968464702867583019834252739659");
const Integer a("38340410290425650555291103033366954895786709470949111520317038818740559472271");
const Integer b("61862461829344747002414367293848044144907923329445405487651446734863421214369");
const ECP E = ECP(p, a, b);
const Integer q("17140919845495644405684916695917785998672015991198074381415721324869292128811");
/* Note: The curve E has order r = 2^2 * q where q is prime. */
const Integer x("49783729659862894673603312242618433622969024866008586212478256625771510792958");
const Integer y("18916745246771588809190938755787142016135405279727789454979776401687407939506");
const ECPPoint P = ECP::Point(x, y);
/* Note: The point P is on E and of order r so it generates all of E. */
/* Note: Let us now compute the point Q = [4] P of prime order q. */
const Integer expected_Qx("33898744863829483362161709717034397769364896634277352921440311777960767108802");
const Integer expected_Qy("23483645583050324501141112153509270605088748325709409281081826839369927198174");
const Integer cofactor(4);
const ECPPoint Q1 = E.ScalarMultiply(P, cofactor);
std::cout << "Q1.x = " << Q1.x << std::endl;
std::cout << "Q1.y = " << Q1.y << std::endl << std::endl;
if ((expected_Qx == Q1.x) && (expected_Qy == Q1.y)) {
std::cout << ">> Q1 is as expected." << std::endl;
} else {
std::cout << ">> Q1 is *NOT* as expected." << std::endl;
}
if (E.VerifyPoint(Q1)) {
std::cout << ">> Q1 is on E." << std::endl;
} else {
std::cout << ">> Q1 is *NOT* on E." << std::endl;
}
std::cout << std::endl;
/* Let us compute Q by a different function call and compare: */
ECPPoint Q2;
E.SimultaneousMultiply(&Q2, P, &cofactor, 1);
std::cout << "Q2.x = " << Q2.x << std::endl;
std::cout << "Q2.y = " << Q2.y << std::endl << std::endl;
if ((expected_Qx == Q2.x) && (expected_Qy == Q2.y)) {
std::cout << ">> Q2 is as expected." << std::endl;
} else {
std::cout << ">> Q2 is *NOT* as expected." << std::endl;
}
if (E.VerifyPoint(Q2)) {
std::cout << ">> Q2 is on E." << std::endl;
} else {
std::cout << ">> Q2 is *NOT* on E." << std::endl;
}
std::cout << std::endl;
/* It seems Crypto++ treats the case where the scalar is of bit length <= 5
* differently from the case where it is of longer length, see:
*
* https://github.com/weidai11/cryptopp/blob/782057f5f18fbdad2bd2b291fb1ec558a8ab8225/ecp.cpp#L387
*
* Could this be the issue? Let us perform the below tests: */
for (unsigned int i = 1; i <= 34; i++) {
Integer d(i);
/* Compute T = [d] P by two different function calls and compare: */
const ECPPoint T1 = E.ScalarMultiply(P, d);
ECPPoint T2;
E.SimultaneousMultiply(&T2, P, &d, 1);
if (T1 == T2) {
std::cout << ">> T1 is equal to T2 for d = " << d << std::endl;
} else {
std::cout << ">> T1 is *NOT* equal to T2 for d = " << d << std::endl;
}
}
std::cout << std::endl;
/* Let us also try with a large scalar uniformly sampled from [0, r). */
{
Integer d("4838386420901692723041175965060989195194280026704430236348655611663611748562");
/* Compute T = [d] P by two different function calls and compare: */
const ECPPoint T1 = E.ScalarMultiply(P, d);
ECPPoint T2;
E.SimultaneousMultiply(&T2, P, &d, 1);
if (T1 == T2) {
std::cout << ">> T1 is equal to T2 for d = " << d << std::endl;
} else {
std::cout << ">> T1 is *NOT* equal to T2 for d = " << d << std::endl;
}
}
}
```
To confirm that there was no issue with the specific Ubuntu installation, I setup a clean virtual Ubuntu 20.04.6 LTS machine and repeated the above steps. I was thus able to reproduce the erroneous behavior.
To check whether this issue extends to other releases and architectures, I furthermore compiled <code>main.cpp</code> and ran the resulting executable under Ubuntu 22.04 LTS for ARM64 in a virtual machine. The correct expected output was then produced:
```console
$ g++ main.cpp -lcryptopp -o test
$ ./test
Q1.x = 33898744863829483362161709717034397769364896634277352921440311777960767108802.
Q1.y = 23483645583050324501141112153509270605088748325709409281081826839369927198174.
>> Q1 is as expected.
>> Q1 is on E.
Q2.x = 33898744863829483362161709717034397769364896634277352921440311777960767108802.
Q2.y = 23483645583050324501141112153509270605088748325709409281081826839369927198174.
>> Q2 is as expected.
>> Q2 is on E.
>> T1 is equal to T2 for d = 1.
>> T1 is equal to T2 for d = 2.
>> T1 is equal to T2 for d = 3.
>> T1 is equal to T2 for d = 4.
>> T1 is equal to T2 for d = 5.
>> T1 is equal to T2 for d = 6.
>> T1 is equal to T2 for d = 7.
>> T1 is equal to T2 for d = 8.
>> T1 is equal to T2 for d = 9.
>> T1 is equal to T2 for d = 10.
>> T1 is equal to T2 for d = 11.
>> T1 is equal to T2 for d = 12.
>> T1 is equal to T2 for d = 13.
>> T1 is equal to T2 for d = 14.
>> T1 is equal to T2 for d = 15.
>> T1 is equal to T2 for d = 16.
>> T1 is equal to T2 for d = 17.
>> T1 is equal to T2 for d = 18.
>> T1 is equal to T2 for d = 19.
>> T1 is equal to T2 for d = 20.
>> T1 is equal to T2 for d = 21.
>> T1 is equal to T2 for d = 22.
>> T1 is equal to T2 for d = 23.
>> T1 is equal to T2 for d = 24.
>> T1 is equal to T2 for d = 25.
>> T1 is equal to T2 for d = 26.
>> T1 is equal to T2 for d = 27.
>> T1 is equal to T2 for d = 28.
>> T1 is equal to T2 for d = 29.
>> T1 is equal to T2 for d = 30.
>> T1 is equal to T2 for d = 31.
>> T1 is equal to T2 for d = 32.
>> T1 is equal to T2 for d = 33.
>> T1 is equal to T2 for d = 34.
>> T1 is equal to T2 for d = 4838386420901692723041175965060989195194280026704430236348655611663611748562.
```
To better try to understand what is going on, I [downloaded Crypto++ releases](https://github.com/weidai11/cryptopp/releases) from [this GitHub repository](https://github.com/weidai11/cryptopp), and proceeded to compile and link against them manually. I did this on the Ubuntu 20.04.6 LTS machine that produced the erroneous output, in the hope of thus being able to reproduce the error. But as it turned out, I could not reproduce the error in this way. Instead, the correct expected output was produced for all of the GitHub releases that I have tried thus far (namely v5.6.3, v5.6.4, v5.6.5, v6.0.0, v6.1.0, v7.0.0, v8.0.0, v8.2.0, v8.3.0, v8.4.0 and v8.9.0) — but not for Crypto++ as provided by the Ubuntu package repository.
I did expect to be able to reproduce the error at least for v5.6.4, if this is the version from which the Ubuntu package was built. When I could not, I computed a diff between the header files installed by the Ubuntu package and the header files for the v5.6.4 release from this GitHub repository, and there appears to be some differences.
So in conclusion, I am not entirely sure which version of Crypto++ is in the Ubuntu repository, and how it was compiled, tested, etc. But it seems that it is not working properly? I find this all a bit surprising. Could someone else please confirm this? Or let me know if I am making some mistake in my code, given that I usually never use Crypto++. Assuming I did not make a mistake and that this really is an issue, further actions may then of course be necessary.
(On a side note, I would expect there to be unit tests that cover the small scalar case, since the code branches depending on the bit length of the scalar. Assuming that this is the case, and that these tests were run, it seems strange to me that this issue would not have been detected when the Ubuntu package was built.) | ECP::ScalarMultiply() may seemingly miscompute for small scalars when using Ubuntu 20.04.6 LTS on 64-bit Intel CPUs | https://api.github.com/repos/weidai11/cryptopp/issues/1269/comments | 6 | 2024-04-06T13:04:46Z | 2024-05-06T18:48:10Z | https://github.com/weidai11/cryptopp/issues/1269 | 2,229,234,040 | 1,269 |
[
"weidai11",
"cryptopp"
] | Updated: The problem raises from g++ (13.2.0) environment detection.
The g++ compiler works well with:
CXX=/mingw64/bin/g++ make all
But does not work correctly with:
CXX="D:\\msys64\\mingw64\\bin\\g++.exe" make
(it adds more flag -DCRYPTOPP_DISABLE_ASM and then some classes like integer, do not work correctly)
### Crypto++ Issue Report
Please help, the Integer class does not work:
Compiler: g++.exe (Rev2, Built by MSYS2 project) 13.2.0;
Plasform: Window 11, Mingw64;
Test code: Compile OK, but execution file returns nothing (cout does not work)
AutoSeededRandomPool prng;
Integer p("01FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFH");
Integer x("1234567654312456789076532134567890012.");
Integer y(prng, 1, p); // random integer
cout << "p= " << p << endl;
cout << "x= " << x << endl;
cout << "y= " << y << endl;
| Integer class errors | https://api.github.com/repos/weidai11/cryptopp/issues/1268/comments | 0 | 2024-04-04T02:07:48Z | 2024-06-10T14:00:18Z | https://github.com/weidai11/cryptopp/issues/1268 | 2,224,290,957 | 1,268 |
[
"weidai11",
"cryptopp"
] | ### Crypto++ Issue Report
The CryptoPP allocation code is vulnerable to infinite executions in case of memory exhaustion conditions.
Submitted a PR to perform a fail safe operation (throw bad_alloc) instead of looping forever. Issue will likely affect all platforms.
On top of this fix, I recommend having more precise exception handling throughout the project instead of using the generic (Exception e) as it may inform users about the precise error causes. I did not change this in the PR.
See: https://github.com/weidai11/cryptopp/pull/1266
Thank you,
Julien
Please do not ask questions in the bug tracker. Please ask questions on the Crypto++ Users List at http://groups.google.com/forum/#!forum/cryptopp-users.
Please do not ask questions about unsupported build systems, like Autotools, CMake, Conan and NuGet. They are other people's projects. We don't know anything about them.
Please do not ask questions at Stack Overflow. We do not patrol Stack Overflow. We will not be able to answer your question.
There is a wiki page with information on filing useful bug reports. If you have some time please visit http://www.cryptopp.com/wiki/Bug_Report on the wiki. The executive summary is:
* State the operating system and version (Ubutnu 17 x86_64, Windows 7 Professional x64, etc)
* State the version of the Crypto++ library (Crypto++ 7.0, Master, etc)
* State how you built the library (Visual Studio, Makefile, distro provided, etc)
* Show a typical command line (the output of the compiler for cryptlib.cpp)
* Show the link command (the output of the linker for libcryptopp.so or cryptest.exe)
* Show the exact error message you are receiving (copy and paste it); or
* Clearly state the undesired behavior (and state the expected behavior)
| Infinite execution behavior in main branch | https://api.github.com/repos/weidai11/cryptopp/issues/1267/comments | 0 | 2024-03-18T19:51:25Z | 2024-03-18T19:51:25Z | https://github.com/weidai11/cryptopp/issues/1267 | 2,193,146,946 | 1,267 |
[
"weidai11",
"cryptopp"
] | Hello there,
Thank you very much for providing support for this open source project.
One project I'm currently working on currently uses Crypto++ and has a need for performing mathematical operations on Hyperelliptic Curves (specifically genus 2).
While libraries such as [libg2hec](https://github.com/syncom/libg2hec/) exist, they depend on [NTL](https://libntl.org/) which, when using Crypto++ for the rest of the application, seems a bit silly to include.
I'm not sure if support for this in Crypto++ was ever discussed in the past (a cursory google search didn't reveal anything), but I figure having an open ticket on GitHub may be the best course of action for both feedback and discussion.
Thank you again | Add support for Elliptic Curves of Genus n (Hyperelliptic Curves) | https://api.github.com/repos/weidai11/cryptopp/issues/1265/comments | 0 | 2024-03-16T07:41:38Z | 2024-03-16T07:41:38Z | https://github.com/weidai11/cryptopp/issues/1265 | 2,189,842,582 | 1,265 |
[
"weidai11",
"cryptopp"
] | env: MacBook Pro Apple M3
ld.lld: error: duplicate symbol: CryptoPP::CallNewHandler()
>>> defined at allocate.cpp:29 (/Users/XXXX/Documents/work/lib-encrypt/EMCrypto/src/main/cpp/cryptopp/allocate.cpp:29)
>>> allocate.cpp.o:(CryptoPP::CallNewHandler()) in archive libcryptopp.a
>>> defined at misc.cpp:121 (/Users/XXXX/Documents/work/lib-encrypt/EMCrypto/src/main/cpp/cryptopp/misc.cpp:121)
>>> misc.cpp.o:(.text._ZN8CryptoPP14CallNewHandlerEv+0x0) in archive libcryptopp.a
ld.lld: error: duplicate symbol: CryptoPP::UnalignedAllocate(unsigned long)
>>> defined at allocate.cpp:90 (/Users/XXXX/Documents/work/lib-encrypt/EMCrypto/src/main/cpp/cryptopp/allocate.cpp:90)
>>> allocate.cpp.o:(CryptoPP::UnalignedAllocate(unsigned long)) in archive libcryptopp.a
>>> defined at misc.cpp:173 (/Users/XXXX/Documents/work/lib-encrypt/EMCrypto/src/main/cpp/cryptopp/misc.cpp:173)
>>> misc.cpp.o:(.text._ZN8CryptoPP17UnalignedAllocateEm+0x0) in archive libcryptopp.a
ld.lld: error: duplicate symbol: CryptoPP::UnalignedDeallocate(void*)
>>> defined at allocate.cpp:98 (/Users/XXXX/Documents/work/lib-encrypt/EMCrypto/src/main/cpp/cryptopp/allocate.cpp:98)
>>> allocate.cpp.o:(CryptoPP::UnalignedDeallocate(void*)) in archive libcryptopp.a
>>> defined at misc.cpp:181 (/Users/XXXX/Documents/work/lib-encrypt/EMCrypto/src/main/cpp/cryptopp/misc.cpp:181)
>>> misc.cpp.o:(.text._ZN8CryptoPP19UnalignedDeallocateEPv+0x0) in archive libcryptopp.a
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
ninja: build stopped: subcommand failed.
Detail: Please check the message from tools.
How to fix it | ld.lld: error: duplicate symbol: CryptoPP::CallNewHandler() | https://api.github.com/repos/weidai11/cryptopp/issues/1263/comments | 0 | 2024-03-09T07:42:51Z | 2024-03-09T07:42:51Z | https://github.com/weidai11/cryptopp/issues/1263 | 2,177,114,808 | 1,263 |
[
"weidai11",
"cryptopp"
] | Hi Team,
We are writing to report a potential security issue about the implementation of Elgamal Encryption in Cryptopp.
Specifically, we cloned Cryptopp-8.9 from [cryptopp.com](http://cryptopp.com/) on February 1, 2024 and analyzed the source code of the Elgamal encryption scheme (more precisely, [elgamal.h](https://github.com/weidai11/cryptopp/blob/master/elgamal.h)). Based on our analysis, its decryption implementation (Line 78 in [elgamal.h](https://github.com/weidai11/cryptopp/blob/master/elgamal.h#L78)}) is vulnerable to fault injection.
As you may know, Rowhammer is a software-induced DRAM fault, which can induce bit flips in main memory that runs a commodity system. In our attack scenario, a malicious user process co-resides in the same system with a victim process that runs the Elgamal decryption of Cryptopp. As both processes share the main memory, the adversary can induce bit flips to the secret key before it is used by the victim to decrypt a ciphertext, resulting in a faulty decryption message. With enough faulty decryption messages released, the adversary can recover/leak the secret key. For more details of the analysis and possible countermeasures, they are provided in the attached pdf [Vulnerability_report.pdf](https://github.com/weidai11/cryptopp/files/14326503/Vulnerability_report.pdf).
Prior to this report, we have reported similar vulnerabilities in RSA encryption and EdDSA signature schemes implemented in WolfSSL. Its security team have acknowledged our findings, fixed RSA encryption via a [commit](https://github.com/wolfSSL/wolfssl/commit/de4a6f9e00f6fbcaa7e20ed7bd89b5d50179e634) and EdDSA signature via another [commit](https://github.com/wolfSSL/wolfssl/commit/c8d0bb0bd8fcd3dd177ec04e9a659a006df51b73). Before our reports to WolfSSL, RSA signature in both WolfSSL and OpenSSL has been proven to be vulnerable to Rowhammer-based attacks. WolfSSL tracked the RSA signature vulnerability via CVE-2019-19962. OpenSSL fixed it by a [commit](https://github.com/openssl/openssl/pull/7225/commits/02534c1ee3e84a1d6c59a887a67bd5ee81bcf6cf).
If you have any question or need more details, please let us know. We are looking forward to your reply. Thank you.
Best Regards,
Junkai Liang (Peking University)
Zhi Zhang (The University of Western Australia)
Xin Zhang (Peking University)
Qingni Shen (Peking University) | Leak the Secret Key of Elgamal Encryption in Cryptopp via Rowhammer | https://api.github.com/repos/weidai11/cryptopp/issues/1262/comments | 1 | 2024-02-19T04:50:15Z | 2024-05-22T18:34:33Z | https://github.com/weidai11/cryptopp/issues/1262 | 2,141,498,668 | 1,262 |
[
"weidai11",
"cryptopp"
] | null | Compilation fails using MSYS2 CLANGARM64 toolchain | https://api.github.com/repos/weidai11/cryptopp/issues/1260/comments | 0 | 2024-01-27T00:00:10Z | 2024-03-06T04:24:34Z | https://github.com/weidai11/cryptopp/issues/1260 | 2,103,076,475 | 1,260 |
[
"weidai11",
"cryptopp"
] | ### Crypto++ Issue Report
Hi, this repo this too large, our project is using this repo as git submodule, but often failed to git clone this repo due to rpc connection timeout.
Any advice / workaround would be appreciate.
| repo too large, git clone often failed due to rpm connection timeout | https://api.github.com/repos/weidai11/cryptopp/issues/1259/comments | 0 | 2024-01-24T09:10:13Z | 2024-01-24T09:10:13Z | https://github.com/weidai11/cryptopp/issues/1259 | 2,097,785,955 | 1,259 |
[
"weidai11",
"cryptopp"
] | I use the following code for signature verification, and it seems that there is a memory leak that occurred in the function RSA_VerifyStr,inside the StringSource,
I don't know what caused it, I hope to receive a response.
cryptopp version is 8.6.0,operating system is win10,IDE is vs2022
`#include <string>
#include <cryptopp/rsa.h>
#include <cryptopp/randpool.h>
#include <cryptopp/osrng.h>
#include <cryptopp/files.h>
#include <cryptopp/base64.h>
#include <cryptopp/aes.h>
#include <cryptopp/hex.h>
#include <cryptopp/modes.h>
#include <cryptopp/sha.h>
using namespace CryptoPP;
std::string SHA256EncodeStr(const std::string& plainText)
{
SHA256 sha256;
std::string hash;
StringSource ss(plainText, true, new HashFilter(sha256, new HexEncoder(new StringSink(hash))));
return hash;
}
bool RSA_VerifyStr(const std::string& pubStr, const std::string& message, const std::string& signatureStr)
{
StringSource pub(pubStr.c_str(), true, new HexDecoder);
RSASS<PKCS1v15, SHA1>::Verifier pubVerifier(pub);
StringSource signatureSrc(signatureStr.c_str(), true, new HexDecoder);
if (signatureSrc.MaxRetrievable() != pubVerifier.SignatureLength())
return false;
SecByteBlock signature(pubVerifier.SignatureLength());
signatureSrc.Get(signature, signature.size());
SignatureVerificationFilter* verifierFilter = new SignatureVerificationFilter(pubVerifier);
verifierFilter->Put(signature, pubVerifier.SignatureLength());
StringSource s((byte*)message.c_str(), message.length(), true, verifierFilter);
return verifierFilter->GetLastResult();
}
int main()
{
std::string pubKeyStr = "30819D300D06092A864886F70D010101050003818B00308187028181009CE8D41CF3B62F8CDBA9B020D9D4A4CFEE9CDF0A49FBA990D2EFD1160649197D206B3D47AC52B6B982E3936EDCCFC850EFF5FEF32B7E7DBB0C017B56CF0FD4FC20ECF8DD58D232569CFAD1AF25DE1CCAABDD85153B572B96A241C49D6E6DBBFC19DB1CEE444488606D6CE0A27E214408FCF727923AEB641E0EF922368582001B020111";
std::string signature = "06B32FEF7F4A5EB12F809F641A7E8F84465401CD212B6B775BA658855C0CD8B417D54D3FDC8DD64FDDD2B04C14A94B5C37EC5C8A2748F97332EF251C02D2958CC88CA3E4A144DD04F609B0BD08043B6FD90E9C369214C84F24A374883CDF836B11156378EF05E9C1E8677090EFD6362A006B4ADD29F1CDDF9D26FFD621D2A7EB";
std::string jsonStr = "{\"validFrom\":1703001600,\"validTo\":1734624000,\"cpuId\":\"BFEBFBFF000A0652\"}";
if (!RSA_VerifyStr(pubKeyStr, SHA256EncodeStr(jsonStr), signature))
return -1;
return 0;
}
` | Memory leak in signature verification | https://api.github.com/repos/weidai11/cryptopp/issues/1258/comments | 3 | 2024-01-13T04:06:43Z | 2024-06-11T06:43:37Z | https://github.com/weidai11/cryptopp/issues/1258 | 2,080,056,465 | 1,258 |
[
"weidai11",
"cryptopp"
] | Hi,
I really need help with this done: I have simple program, which is working fine except for deleting part
I use VS2015 and my Settings or my program are:
General: (Unicode + Use MFC in a Shared DLL)
Link: Multi-threaded DLL (/MD)
link with static lib "cryptlib.lib"
code
```
#define CRYPTOPP_DEFAULT_NO_DLL
#define CRYPTOPP_ENABLE_NAMESPACE_WEAK 1
#include <dll.h>
#include <cryptlib.h>
#include <sha.h>
#include <hex.h>
#include <filters.h>
void CMyDlg::TestCrypto()
{
using namespace CryptoPP;
SHA256 hash;
std::string message = "abcdefghijklmnopqrstuvwxyz";
std::string digest;
{
StringSink MySink(digest);
HexEncoder MyHexEncoder(&MySink);
HashFilter MyHash(hash, &MyHexEncoder);
StringSource s(message, true, &MyHash);
s.PumpAll();
}
}
```
it building and linking fine, but after function is ran and deleting is being done this function it will crash
I have crypto 8.9 / I use WIN_32 Release with Static library (.lib) / Use MFC in a Shared DLL / Unicode / Multi-threaded DLL (/MD)
when I use another settings I get link errors etc. (the program must be same compiler options as the crypt.lib)
my problem looks a lot like this
[https://stackoverflow.com/questions/59163281/runtime-library-heap-error-using-crypto-and-vs2019-with-mfc](https://stackoverflow.com/questions/59163281/runtime-library-heap-error-using-crypto-and-vs2019-with-mfc)
but a solution of this was not found by me
Kind Regards
Dan | destructor delete problem with own dialog program with MFC (Unicode/Use MFC in a Shared DLL) VS2015 | https://api.github.com/repos/weidai11/cryptopp/issues/1256/comments | 0 | 2024-01-02T14:51:54Z | 2024-01-02T14:52:39Z | https://github.com/weidai11/cryptopp/issues/1256 | 2,062,529,664 | 1,256 |
[
"weidai11",
"cryptopp"
] | Thank you so much for many years of hard work and devotion.
This isn’t really an issue but a question. Unfortunately the Google group is down.
I am working with a database of cipher texts derived using PBKDF2 HMAC SHA2 256 key derivation function in Python Django. I am migrating the application to C++ so I chose Crypto++.
Unfortunately I couldn’t get to generate equivalent ciphers using the same parameters as used in Django. This is probably what Django does that I couldn’t get to do with the library:
```
b64encode.b64encode(hash).decode("ascii").strip()
```
The `hash` I am wont to believe is a sequence of bytes which Django produces with the hashing algorithm PBKDF2 HMAC SHA2 256 and it encodes to Base64 bytes before then decoding to ASCII characters.
I am wont to believe that Crypto++ does something similar. It produces a sequence of bytes, then the user can encode the byte sequence to Base64.
Which character set is then used for representation? **UTF8**? **ASCII**? **UTF16**?
Your answer will be very much appreciated. | Django cipher texts not matching Crypto++ cipher texts. | https://api.github.com/repos/weidai11/cryptopp/issues/1254/comments | 0 | 2023-12-18T04:44:04Z | 2023-12-18T04:44:04Z | https://github.com/weidai11/cryptopp/issues/1254 | 2,045,727,660 | 1,254 |
[
"weidai11",
"cryptopp"
] | Operating system and version (Ubuntu 18.04)
version of the Crypto++ library (Crypto++ 8.8.0)
I got some unusual output from the fuzzer. Tried to analyze what this was.
```bash
Successfully executed: ./ChaCha20-Poly1305_id:012769,sync:afl0,src:012806
Output: INFO: Seed: 3188957293
INFO: Loaded 1 modules (309231 inline 8-bit counters): 309231 [0x44cabf9, 0x45163e8),
INFO: Loaded 1 PC tables (309231 PCs): 309231 [0x45163e8,0x49ce2d8),
../fuzzer: Running 1 inputs 1 time(s) each.
Running: ./ChaCha20-Poly1305_id:012769,sync:afl0,src:012806
poly1305.cpp:159:15: runtime error: null pointer passed as argument 1, which is declared to never be null
/usr/include/string.h:43:28: note: nonnull attribute specified here
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior poly1305.cpp:159:15 in
Executed ./ChaCha20-Poly1305_id:012769,sync:afl0,src:012806 in 213 ms
***
*** NOTE: fuzzing was not performed, you have only
*** executed the target code on a fixed set of inputs.
***
```
Code I tried to reproduce. Assigned ```byte* mac = nullptr;```
```cpp
#include "cryptlib.h"
#include "chachapoly.h"
#include "filters.h"
#include "files.h"
#include "hex.h"
int main(int argc, char* argv[])
{
using namespace CryptoPP;
const byte pt[] = {
0x4c,0x61,0x64,0x69,0x65,0x73,0x20,0x61,0x6e,0x64,0x20,0x47,0x65,0x6e,0x74,0x6c,
0x65,0x6d,0x65,0x6e,0x20,0x6f,0x66,0x20,0x74,0x68,0x65,0x20,0x63,0x6c,0x61,0x73,
0x73,0x20,0x6f,0x66,0x20,0x27,0x39,0x39,0x3a,0x20,0x49,0x66,0x20,0x49,0x20,0x63,
0x6f,0x75,0x6c,0x64,0x20,0x6f,0x66,0x66,0x65,0x72,0x20,0x79,0x6f,0x75,0x20,0x6f,
0x6e,0x6c,0x79,0x20,0x6f,0x6e,0x65,0x20,0x74,0x69,0x70,0x20,0x66,0x6f,0x72,0x20,
0x74,0x68,0x65,0x20,0x66,0x75,0x74,0x75,0x72,0x65,0x2c,0x20,0x73,0x75,0x6e,0x73,
0x63,0x72,0x65,0x65,0x6e,0x20,0x77,0x6f,0x75,0x6c,0x64,0x20,0x62,0x65,0x20,0x69,
0x74,0x2e
};
const byte aad[] = {
0x50,0x51,0x52,0x53,0xc0,0xc1,0xc2,0xc3,0xc4,0xc5,0xc6,0xc7
};
const byte key[] = {
0x80,0x81,0x82,0x83,0x84,0x85,0x86,0x87,0x88,0x89,0x8a,0x8b,0x8c,0x8d,0x8e,0x8f,
0x90,0x91,0x92,0x93,0x94,0x95,0x96,0x97,0x98,0x99,0x9a,0x9b,0x9c,0x9d,0x9e,0x9f
};
const byte iv[] = {
0x07,0x00,0x00,0x00, // Common
0x40,0x41,0x42,0x43,0x44,0x45,0x46,0x47 // IV
};
byte ct[sizeof(pt)], rt[sizeof(ct)];
byte* mac = nullptr;
ChaCha20Poly1305::Encryption enc;
enc.SetKeyWithIV(key, sizeof(key), iv, sizeof(iv));
enc.EncryptAndAuthenticate(ct, mac, sizeof(mac), iv, sizeof(iv), aad, sizeof(aad), pt, sizeof(pt));
std::cout << "Plain: ";
StringSource(pt, sizeof(pt), true, new HexEncoder(new FileSink(std::cout)));
std::cout << "\n" << std::endl;
std::cout << "Cipher: ";
StringSource(ct, sizeof(ct), true, new HexEncoder(new FileSink(std::cout)));
std::cout << std::endl;
std::cout << "MAC: ";
StringSource(mac, sizeof(mac), true, new HexEncoder(new FileSink(std::cout)));
std::cout << "\n" << std::endl;
ChaCha20Poly1305::Decryption dec;
dec.SetKeyWithIV(key, sizeof(key), iv, sizeof(iv));
dec.DecryptAndVerify(rt, mac, sizeof(mac), iv, sizeof(iv), aad, sizeof(aad), ct, sizeof(ct));
std::cout << "Recover: ";
StringSource(rt, sizeof(rt), true, new HexEncoder(new FileSink(std::cout)));
std::cout << "\n" << std::endl;
return 0;
}
```
This is how I compiled.
```bash
g++ -fsanitize=address -g main.cpp -o main -L/opt/homebrew/opt/cryptopp/lib -lcryptopp
./main
```
This is the result of Address Sanitizer.
```
AddressSanitizer:DEADLYSIGNAL
=================================================================
==71557==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x000105721fd0 bp 0x00016b22a2f0 sp 0x00016b229aa0 T0)
==71557==The signal is caused by a WRITE memory access.
==71557==Hint: address points to the zero page.
#0 0x105721fd0 in __sanitizer::internal_memmove(void*, void const*, unsigned long)+0xd0 (libclang_rt.asan_osx_dynamic.dylib:arm64e+0x69fd0)
#1 0x104ca5548 in (anonymous namespace)::Poly1305_HashFinal(unsigned int*, unsigned int*, unsigned char*, unsigned long) poly1305.cpp:159
#2 0x104ca5ed4 in non-virtual thunk to CryptoPP::Poly1305TLS_Base::TruncatedFinal(unsigned char*, unsigned long) poly1305.cpp
#3 0x104c21960 in CryptoPP::ChaCha20Poly1305_Base::AuthenticateLastFooterBlock(unsigned char*, unsigned long) chachapoly.cpp:93
#4 0x104c1d2f0 in CryptoPP::AuthenticatedSymmetricCipherBase::TruncatedFinal(unsigned char*, unsigned long) authenc.cpp:175
#5 0x104bd6fa8 in main main.cpp:41
#6 0x18a7bd054 (<unknown module>)
==71557==Register values:
x[0] = 0x0000000000000000 x[1] = 0x000000016b22a308 x[2] = 0x0000000000000008 x[3] = 0x0000000000000008
x[4] = 0x0000000000000001 x[5] = 0x0000000000000001 x[6] = 0x0000000052b8fd53 x[7] = 0x138c753591b28b92
x[8] = 0x0000000000000008 x[9] = 0x000000016b22a310 x[10] = 0x0000000000000000 x[11] = 0xfffffffffffffff8
x[12] = 0x0000000000000000 x[13] = 0x0000000000000000 x[14] = 0x0000000000000000 x[15] = 0x0000000000000000
x[16] = 0x00000001056d25dc x[17] = 0x0000000000000000 x[18] = 0x0000000000000000 x[19] = 0x0000000000000008
x[20] = 0x000000016b22a308 x[21] = 0x0000000000000000 x[22] = 0x0000000000000000 x[23] = 0x000000016b22b3a0
x[24] = 0x0000000106185aa8 x[25] = 0xffffffffffffffc7 x[26] = 0x0000000000000000 x[27] = 0x0000000000000000
x[28] = 0x0000000000000000 fp = 0x000000016b22a2f0 lr = 0x00000001056d26bc sp = 0x000000016b229aa0
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV (libclang_rt.asan_osx_dynamic.dylib:arm64e+0x69fd0) in __sanitizer::internal_memmove(void*, void const*, unsigned long)+0xd0
``` | Poly1305 null pointer passed as argument 1 | https://api.github.com/repos/weidai11/cryptopp/issues/1253/comments | 1 | 2023-12-13T09:26:08Z | 2023-12-13T09:41:14Z | https://github.com/weidai11/cryptopp/issues/1253 | 2,039,295,906 | 1,253 |
[
"weidai11",
"cryptopp"
] | In the current form, Crypto++ will compile the library with optimal settings for the current build machine.
However in many cases (as mine) we need to compile a generic version of the library such that the resulting binary can be redistributed.
If Crypto++ is build on a high end machine and then shipped to a client with old hardware, it is very likely that the application will crash with an instruction unknown.
It would be very useful if a target (-march=target) platform could be defined somewhere that would define all instruction sets supported. In this case all hardware tests should be ignored. | Crypto++ needs to support a fixed target | https://api.github.com/repos/weidai11/cryptopp/issues/1252/comments | 2 | 2023-12-08T20:13:21Z | 2023-12-09T05:49:26Z | https://github.com/weidai11/cryptopp/issues/1252 | 2,033,257,786 | 1,252 |
[
"weidai11",
"cryptopp"
] | Hi,
A week ago I updated crypto to the latest version and recently I discovered that my program sometimes crashes on the release version.
I tried opening it to debug mode. start the program and then stop.
Is there anything unusual about statically linking crypto.lib? I haven't run any functions yet. it just linked up lib.
if I remove the cryptlib library
when i linked cryptlib library
Thanks you!
| Memory leak problem!! | https://api.github.com/repos/weidai11/cryptopp/issues/1251/comments | 2 | 2023-12-06T16:00:57Z | 2023-12-07T11:43:33Z | https://github.com/weidai11/cryptopp/issues/1251 | 2,028,888,083 | 1,251 |
[
"weidai11",
"cryptopp"
] | I`m seeing compiler warnings since the latest VS 2022 update (17.8.0) on Windows 11 with the latest cryptopp 8.9
`17:30:31:685 1>X:\cryptopp\integer.cpp(3061,12): warning C4996: 'stdext::make_checked_array_iterator': warning STL4043: stdext::checked_array_iterator, stdext::unchecked_array_iterator, and related factory functions are non-Standard extensions and will be removed in the future. std::span (since C++20) and gsl::span can be used instead. You can define _SILENCE_STDEXT_ARR_ITERS_DEPRECATION_WARNING or _SILENCE_ALL_MS_EXT_DEPRECATION_WARNINGS to suppress this warning.
17:30:31:685 1>(compiling source file '/integer.cpp')
17:30:32:401 1>X:\cryptopp\zdeflate.cpp(422,155): warning C4996: 'stdext::unchecked_array_iterator<const CryptoPP::byte *>::operator -': warning STL4043: stdext::checked_array_iterator, stdext::unchecked_array_iterator, and related factory functions are non-Standard extensions and will be removed in the future. std::span (since C++20) and gsl::span can be used instead. You can define _SILENCE_STDEXT_ARR_ITERS_DEPRECATION_WARNING or _SILENCE_ALL_MS_EXT_DEPRECATION_WARNINGS to suppress this warning.
`
It appears loosen from the platformSDK and loosen from the C++ standard
Tried PlatformSDK:
- 10.0.19041.0
- 10.0.22000.0
C++ Language standard:
- ISO C++17 Standard (/std:c++17)
- ISO C++20 Standard (/std:c++20)
| Compile warnings in VS 2022 17.8.0 - stdext::make_checked_array_iterator stdext::make_unchecked_array_iterator beeing deprecated | https://api.github.com/repos/weidai11/cryptopp/issues/1250/comments | 1 | 2023-11-21T16:35:32Z | 2024-01-31T14:22:59Z | https://github.com/weidai11/cryptopp/issues/1250 | 2,004,715,353 | 1,250 |
[
"weidai11",
"cryptopp"
] | Hi, recently I found a security issue in the [ModularSquareRoot](https://github.com/weidai11/cryptopp/blob/3e3b8af96d4d957b77588be91df7715efbe2ed69/nbtheory.cpp#L544) function of `Crypto++` library that would cause an infinite loop, since this function is being used in [ECP::DecodePoint](https://github.com/weidai11/cryptopp/blob/93208e83937a351babdfd9cfa07d7908ba15f68b/ecp.cpp#L117), an attacker could potentially craft a malformed DER public key file, and any user or server attempting to read this public key file in processes such as ECDSA may be susceptible to a DOS attack.
### Issue
The issue lies in [the second while loop](https://github.com/weidai11/cryptopp/blob/3e3b8af96d4d957b77588be91df7715efbe2ed69/nbtheory.cpp#L558) in this function, the loop starts with `n = 2` and increments `n` by one each time until we find an `n` such that `Jacobi(n, p) = -1`. However, this overlooks the case when `p` is in the form of `m^2` and `m` is an odd number.
In this case, `jacobi(n, p) = jacobi(n, m^2)` can be converted into the product of a series of squares of Jacobi symbols using the properties of Jacobi symbols, this means that its value can only be `1` or `0` but not `-1`, therefore, no matter how `n` continues to increase, it will never satisfy `Jacobi(n, p) = -1` to break out of the loop, thus leading to an infinite loop.
Furthermore, since this function is being used in `ECP::DecodePoint`, we can construct a malformed DER public key file that includes an elliptic curve parameter `p` as:
```
72358384006116823815439217615866351214375729203207450702838342058601772551609
```
which is the square of:
```
268995137513890432434389773128616504853
```
and repackage it into a DER file, then any attempt to read and parse this DER file in `Crypto++` will trigger an infinite loop immediately.
In addition, since the `ModularSquareRoot` function is in the branch that handles `03` compression encoding, we need to ensure that the points in the constructed DER file are in compressed form (start with `03`).
### Fix
To fix this issue, the simplest method is to check whether `p` is a prime number at the beginning of the `ModularSquareRoot` function. If it is not a prime number, then directly reject any further calculations (after all, even if it is not rejected, the result calculated in this way will be wrong). | A security issue in the `ModularSquareRoot` function leads to a DOS attack | https://api.github.com/repos/weidai11/cryptopp/issues/1249/comments | 8 | 2023-11-20T11:59:01Z | 2024-08-08T04:17:46Z | https://github.com/weidai11/cryptopp/issues/1249 | 2,002,042,178 | 1,249 |
[
"weidai11",
"cryptopp"
] | Hi, recently I found a security issue in the `Crypto++` library that would cause a segmentation fault when parsing DER public key files of the `F(2^m)` class curves, an attacker could potentially craft a malformed DER public key file, and any user or server attempting to read this public key file in processes such as `ECDSA` may be susceptible to a DOS attack.
### Issue
The main reason of this issue is that when parsing the DER public key file of the `F(2^m)` class curve ([EC2N::DecodePoint](https://github.com/weidai11/cryptopp/blob/3e3b8af96d4d957b77588be91df7715efbe2ed69/ec2n.cpp#L78)), there is no check that the degree of each term in the polynomial is strictly decreasing.
For example, for curve `sect193r1`, it uses polynomial `f(x) = x^193 + x^15 + 1`, then under normal circumstances, DER public key file would store their exponents in the following sequential order in ASN.1 format:
```
35:d=5 hl=2 l= 2 prim: INTEGER :C1
39:d=5 hl=2 l= 9 prim: OBJECT :tpBasis
50:d=5 hl=2 l= 1 prim: INTEGER :0F
```
The above snippet is taken from a regular `sect193r1` public key file. However, if we reverse the order of the exponents, for instance, if we swap the positions of `C1` and `0F`, and repackage it into a DER file, then any attempt to read and parse this DER file in `Crypto++` will trigger a segmentation fault immediately.
To figure out the exact location, I debugged it using `gdb`, and here is the result:
```
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007fb8458e34fc in CryptoPP::GF2NT::Reduced(CryptoPP::PolynomialMod2 const&) const ()
from /usr/lib/x86_64-linux-gnu/libcrypto++.so.8
(gdb) bt
#0 0x00007fb8458e34fc in CryptoPP::GF2NT::Reduced(CryptoPP::PolynomialMod2 const&) const ()
from /usr/lib/x86_64-linux-gnu/libcrypto++.so.8
#1 0x00007fb8458e5440 in CryptoPP::GF2NT::Square(CryptoPP::PolynomialMod2 const&) const ()
from /usr/lib/x86_64-linux-gnu/libcrypto++.so.8
#2 0x00007fb8458ad844 in CryptoPP::EC2N::DecodePoint(CryptoPP::EC2NPoint&, CryptoPP::BufferedTransformation&, unsigned long) const () from /usr/lib/x86_64-linux-gnu/libcrypto++.so.8
#3 0x00007fb8458ad696 in CryptoPP::EC2N::DecodePoint(CryptoPP::EC2NPoint&, unsigned char const*, unsigned long) const ()
from /usr/lib/x86_64-linux-gnu/libcrypto++.so.8
#4 0x00007fb8458ae360 in CryptoPP::EC2N::BERDecodePoint(CryptoPP::BufferedTransformation&) const ()
from /usr/lib/x86_64-linux-gnu/libcrypto++.so.8
#5 0x00007fb84587b542 in CryptoPP::DL_GroupParameters_EC<CryptoPP::EC2N>::BERDecode(CryptoPP::BufferedTransformation&) ()
from /usr/lib/x86_64-linux-gnu/libcrypto++.so.8
#6 0x00007fb84587b9fd in CryptoPP::DL_KeyImpl<CryptoPP::X509PublicKey, CryptoPP::DL_GroupParameters_EC<CryptoPP::EC2N>, CryptoPP::OID>::BERDecodeAlgorithmParameters(CryptoPP::BufferedTransformation&) () from /usr/lib/x86_64-linux-gnu/libcrypto++.so.8
#7 0x00007fb845816488 in CryptoPP::X509PublicKey::BERDecode(CryptoPP::BufferedTransformation&) ()
from /usr/lib/x86_64-linux-gnu/libcrypto++.so.8
#8 0x000055a6c6c1fd92 in CryptoPP::ASN1CryptoMaterial<CryptoPP::PublicKey>::Load (this=0x7ffebe95d0e8, bt=...)
at /usr/include/crypto++/asn.h:697
#9 0x000055a6c6c1d453 in main () at poc.cpp:14
```
From the debugging results of gdb, we can see that the function that actually triggers the problem is [GF2NT::Reduced](https://github.com/weidai11/cryptopp/blob/3e3b8af96d4d957b77588be91df7715efbe2ed69/gf2n.cpp#L832), since this function will only be called when the point is in the form of compression encoding, we need to ensure that the points in the constructed DER file are in compressed form (start with `02` or `03`).
### Fix
To fix this issue, the simplest method is to check whether the coefficients of the polynomial satisfy strict decreasing, which should at least close the entry point that triggers this issue.
However, based on the gdb debugging results, it seems that the issue ultimately arises in . Therefore, fixing the actual cause of the segmentation fault from this function is also a feasible option, but it is still advisable to check whether the coefficients of the polynomial meet our requirements.
### Update
The current fix of this issue can be seen [here](https://github.com/weidai11/cryptopp/commit/eb383b8e1622c07da2d5d6599a8b0e17a0deee0f), thanks for @noloader 's help. | EC2N::DecodePoint can crash if exponents are not in descending order | https://api.github.com/repos/weidai11/cryptopp/issues/1248/comments | 2 | 2023-11-20T06:28:23Z | 2023-11-22T02:37:26Z | https://github.com/weidai11/cryptopp/issues/1248 | 2,001,460,069 | 1,248 |
[
"weidai11",
"cryptopp"
] | ### Crypto++ Issue Report
I've verified that the Crypto++ is vulnerable to the [Marvin Attack](https://people.redhat.com/~hkario/marvin/)—a timing variant of the well-known Bleichenbacher attack.
I've executed the test on ArchLinux, using crypto++ 8.9.0 from the Arch repository.
The reproducer is available in the [marvin-toolkit](https://github.com/tomato42/marvin-toolkit/tree/master/example/crypto%2B%2B) repository. It was compiled with a simple `g++ -o time_decrypt -lcryptopp time_decrypt.cpp`.
When executed on AMD Ryzen 5 5600X, I'm able to detect a side-channel signal when performing decryption with PKCS#1 v1.5 padding. The results are statistically significant with just few hundred measurement pairs, but below I'm showing results of a run with 100k repeats to show the size of the side-channel more clearly.
The test summary:
```
Sign test mean p-value: 0.2339, median p-value: 4.255e-12, min p-value: 3.18e-88
Friedman test (chisquare approximation) for all samples
p-value: 0.0
Worst pair: 1(no_header_with_payload_48), 5(valid_0)
Mean of differences: 3.61457e-07s, 95% CI: 2.63026e-07s, 4.577243e-07s (±9.735e-08s)
Median of differences: 4.80000e-07s, 95% CI: 4.30000e-07s, 5.200001e-07s (±4.500e-08s)
Trimmed mean (5%) of differences: 3.84809e-07s, 95% CI: 3.26061e-07s, 4.382825e-07s (±5.611e-08s)
Trimmed mean (25%) of differences: 4.82399e-07s, 95% CI: 4.37442e-07s, 5.255875e-07s (±4.407e-08s)
Trimmed mean (45%) of differences: 4.77529e-07s, 95% CI: 4.31482e-07s, 5.214141e-07s (±4.497e-08s)
Trimean of differences: 4.63125e-07s, 95% CI: 4.07500e-07s, 5.025002e-07s (±4.750e-08s)
Layperson explanation: Definite side-channel detected, implementation is VULNERABLE
```
legend:
```
ID,Name
0,header_only
1,no_header_with_payload_48
2,no_padding_48
3,no_structure
4,signature_padding_8
5,valid_0
6,valid_48
7,valid_192
8,valid_246
9,valid_repeated_byte_payload_246_1
10,valid_repeated_byte_payload_246_255
11,zero_byte_in_padding_48_4
```
Explanation for the ciphertexts is in the [`step2.py`](https://github.com/tomato42/marvin-toolkit/blob/master/step2.py) file.
As can be read from the graph, there's a clear difference between valid (probes 5, 6, and 7) and invalid ciphertexts. Moreover, the probe 2 is significantly different from others, which suggests a side-channel leakage in the numerical library (the last multiplication to apply deblinder, the last Montgormery reduction, or conversion of the arbitrary precision integer to a byte string), which means that that _all_ padding modes that use the same RSADP() primitive will be similarly vulnerable, that means RSA-OAEP too.
(side note: I'm not a C++ programmer, so any help to make the reproducer cleaner, and command-line configurable, like the ones for openssl, pyca-cryptography, etc. will be really appreciated) | Crypto++ vulnerable to the Marvin Attack | https://api.github.com/repos/weidai11/cryptopp/issues/1247/comments | 1 | 2023-11-12T12:57:41Z | 2024-01-29T00:45:42Z | https://github.com/weidai11/cryptopp/issues/1247 | 1,989,391,420 | 1,247 |
[
"weidai11",
"cryptopp"
] | Hello. At `https://www.cryptopp.com/wiki/RDRAND_and_RDSEED`:
Links tied to
- _Documentation_ | `http://www.cryptopp.com/docs/ref/class_rdrand.html`
- _Intel's RDRAND is designed to never underflow_ | `https://lists.randombit.net/pipermail/cryptography/2016-June/007702.html`
- _RDRAND.zip_ | `https://www.cryptopp.com/w/images/manual/RDRAND.zip`
became obsolete.
Links tied to
- _for equivalent support in June 2015_ | `http://support.amd.com/TechDocs/24594.pdf`
- _Programmers Manual_ | `https://support.amd.com/TechDocs/24594.pdf`
became obsolete; they are redirected to `https://www.amd.com/en/search/documentation/hub.html#sortCriteria=%40amd_release_date%20descending&f-amd_archive_status=Active&f-amd_audience=Technical`, which is not related. | page www.cryptopp.com/wiki | Obsolete links | https://api.github.com/repos/weidai11/cryptopp/issues/1246/comments | 0 | 2023-11-03T15:16:49Z | 2023-11-03T15:16:49Z | https://github.com/weidai11/cryptopp/issues/1246 | 1,976,420,953 | 1,246 |
[
"weidai11",
"cryptopp"
] | I am running Crypto++ (master branch) on Xcode (14.3.1) with an iOS (16.6) app. I am attempting to isolate an issue where Crypto++'s gunzip is not inflating a properly formatted JSON file correctly for me. I am providing an already compressed JSON file whose original size is 1.3 MB. After inflation, I end up with 1.01 MB of data. My issue is that I cannot isolate why I am losing data during the inflation. The compression algorithm used is a multi-threaded compression algorithm adhering to the gzip formatting standard. I can successfully inflate this same compressed JSON file using gzip on OSX, Linux, Windows, but not on iOS using gzip inside the Crypto++ framework.
The snippet of code doing the inflation is:
```
std::string GZipUtils::decompressData(const std::vector<uint8_t> &bytes) {
std::string decompressed;
CryptoPP::Gunzip unzipper(new CryptoPP::StringSink(decompressed));
unzipper.Put((CryptoPP::byte *) bytes.data(), bytes.size());
unzipper.MessageEnd();
return decompressed;
}
```
I would like to note that no errors are being thrown and the Put function returns 0 after the API call, which indicates all bytes were processed. We originally were using the Put2 API call, which produces the same result as Put. It appears Put is calling Put2.
I have attached the compressed and uncompressed JSON files.
[uncompressed.json](https://github.com/weidai11/cryptopp/files/13191291/uncompressed.json)
[compressed.json.gz](https://github.com/weidai11/cryptopp/files/13205504/compressed.json.gz)
| Loss of data after inflation using gunzip | https://api.github.com/repos/weidai11/cryptopp/issues/1245/comments | 3 | 2023-10-27T20:05:28Z | 2023-10-31T13:17:54Z | https://github.com/weidai11/cryptopp/issues/1245 | 1,966,127,592 | 1,245 |
[
"weidai11",
"cryptopp"
] | Hello, I'm using Msys2 MinGW Clang++ to build cryptopp.
When I did the make command, I got this error:
```bash
C:/msys64/mingw64/bin/ld: ./libcryptopp.a(cpu.o): in function `CryptoPP::XGetBV(unsigned int)':
D:/cryptopp890/cpu.cpp:395:(.text+0x11): undefined reference to `XGETBV64'
C:/msys64/mingw64/bin/ld: ./libcryptopp.a(cpu.o): in function `CryptoPP::CpuId(unsigned int, unsigned int, unsigned int*)':
D:/cryptopp890/cpu.cpp:453:(.text+0x25): undefined reference to `CPUID64'
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [GNUmakefile:1511: cryptest.exe] Error 1
```
Do you know how to fix it or can you give me the some instruction for me, I have an assignments about this so please help me. Thank you | Linker command | https://api.github.com/repos/weidai11/cryptopp/issues/1244/comments | 0 | 2023-10-21T07:25:24Z | 2023-10-23T10:41:22Z | https://github.com/weidai11/cryptopp/issues/1244 | 1,955,369,834 | 1,244 |
[
"weidai11",
"cryptopp"
] | Like to report a debug build error, hopefully you can solve this, its a bit unhandy to develop an application when you're not able to build it for debugging,
Using cryptopp version 8.9 with Visual Studio 2022 in a MFC application.
When I build this piece of code in debug mode:
> void SomeClass::EncryptString(CString& str)
> {
>
> AutoSeededRandomPool rng;
>
> // Generate private key
> RSA::PrivateKey privateKey;
> privateKey.GenerateRandomWithKeySize(rng, 2048);
> RSA::PublicKey publicKey(privateKey);
>
> std::string plain = CW2A(str), cipher, recovered;
>
> // Encryption
> RSAES_OAEP_SHA_Encryptor e(publicKey);
>
> StringSource ss1(plain, true,
> new PK_EncryptorFilter(rng, e,
> new StringSink(cipher)
> ) // PK_EncryptorFilter
> ); // StringSource
> }
When executing line: **privateKey.GenerateRandomWithKeySize(rng, 2048);** I got the following debug message:
Unhandled exception at 0x00007FF73F1F31FC An invalid parameter was passed to a function that considers invalid parameters fatal.
And Visual Studio 2022 is showing:
> extern "C" __declspec(noreturn) void __cdecl _invoke_watson(
> wchar_t const* const expression,
> wchar_t const* const function_name,
> wchar_t const* const file_name,
> unsigned int const line_number,
> uintptr_t const reserved
> )
> {
> UNREFERENCED_PARAMETER(expression );
> UNREFERENCED_PARAMETER(function_name);
> UNREFERENCED_PARAMETER(file_name );
> UNREFERENCED_PARAMETER(line_number );
> UNREFERENCED_PARAMETER(reserved );
>
> if (IsProcessorFeaturePresent(PF_FASTFAIL_AVAILABLE))
> {
> __fastfail(FAST_FAIL_INVALID_ARG);
> }
>
> // Otherwise, raise a fast-fail exception and termintae the process:
> __acrt_call_reportfault(
> _CRT_DEBUGGER_INVALIDPARAMETER,
> STATUS_INVALID_CRUNTIME_PARAMETER,
> EXCEPTION_NONCONTINUABLE);
>
> TerminateProcess(GetCurrentProcess(), STATUS_INVALID_CRUNTIME_PARAMETER);
> }
And stop at: **__fastfail(FAST_FAIL_INVALID_ARG);**.
While the same piece of code when building in release mode is working just fine.
I use the debug version of cryptlib.lib for building in debug mode and the release version for building in release mode. | An invalid parameter was passed to a function that considers invalid parameters fatal. Only when building in debug mode. | https://api.github.com/repos/weidai11/cryptopp/issues/1243/comments | 3 | 2023-10-14T21:11:09Z | 2023-10-16T22:30:49Z | https://github.com/weidai11/cryptopp/issues/1243 | 1,943,557,814 | 1,243 |
[
"weidai11",
"cryptopp"
] | null | Unable to link using MSYS2 Clang64 toolchain | https://api.github.com/repos/weidai11/cryptopp/issues/1241/comments | 8 | 2023-10-05T09:45:55Z | 2024-03-06T04:24:19Z | https://github.com/weidai11/cryptopp/issues/1241 | 1,927,848,361 | 1,241 |
[
"weidai11",
"cryptopp"
] | `#define CRYPTOPP_DISABLE_ASM 1` does not disable all assembler / builtins / intrinsics (as documented here: https://github.com/weidai11/cryptopp/blob/CRYPTOPP_8_9_0/config_asm.h#L30).
`cpu.cpp` on x86-64 Windows MSVC builds still wants `CPUID64` and `XGETBV64` which are only implemented in `x64dll.asm` (see https://github.com/weidai11/cryptopp/blob/843d74c7c97f9e19a615b8ff3c0ca06599ca501b/cpu.cpp#L451 / https://github.com/weidai11/cryptopp/blob/843d74c7c97f9e19a615b8ff3c0ca06599ca501b/cpu.cpp#L393 / https://github.com/weidai11/cryptopp/blob/843d74c7c97f9e19a615b8ff3c0ca06599ca501b/cpu.cpp#L81). This makes building Crypto++ as pure C++ impossible.
@noloader The offending commit is https://github.com/weidai11/cryptopp/commit/e65fa006bec60192112f0a3f23174ef0528f8cc4 which removes the use of the MSVC-specific intrinsics for MSVC versions new enough to actually provide it. I suggest reverting the part of this commit that removes the use of `__cpuidex` and `_xgetbv`.
For OpenMPT, we are building Crypto++ with our own build system in which we define `CRYPTOPP_DISABLE_ASM 1`. This worked with 8.8.0, however it fails now with 8.9.0. Crypto++ is not performance critical in our case, thus we very much prefer a simple C++-only solution in order to keep the build system simple.
We are using Crypto++ to secure our automatic updates on older Windows versions which do not provide the necessary crypto primitives themselves. In the failing case, we use VS2017 to target Windows XP.
| CRYPTOPP_DISABLE_ASM is broken in 8.9.0 for MSVC x64 builds | https://api.github.com/repos/weidai11/cryptopp/issues/1240/comments | 20 | 2023-10-02T07:30:17Z | 2023-10-02T11:53:03Z | https://github.com/weidai11/cryptopp/issues/1240 | 1,921,390,213 | 1,240 |
[
"weidai11",
"cryptopp"
] | Crypto++ 8.9.0 was released on October 1, 2023. As part of the release process, we bump version numbers for semantic versioning per https://www.cryptopp.com/wiki/Release_Versioning#Increment.
Crypto++ has a `CRYPTOPP_VERSION` macro, but it cannot handle '10' in the minor position. We cannot go from:
```c
#define CRYPTOPP_VERSION 890
```
to version 8.10.
An additional constraint is, `CRYPTOPP_VERSION` has always used 10-based numbers. They are not hexadecimal based.
This report will track the problem.
----
```
$ grep CRYPTOPP_VERSION *.h *.cpp
config_ver.h:/// \sa CRYPTOPP_VERSION, LibraryVersion(), HeaderVersion()
config_ver.h:/// \sa CRYPTOPP_VERSION, LibraryVersion(), HeaderVersion()
config_ver.h:/// \sa CRYPTOPP_VERSION, LibraryVersion(), HeaderVersion()
config_ver.h:/// \details CRYPTOPP_VERSION reflects the version of the library the headers
config_ver.h:#define CRYPTOPP_VERSION 8A0
cryptlib.h: return CRYPTOPP_VERSION;
bench1.cpp: oss << "\n<H1><A href=\"http://www.cryptopp.com\">Crypto++ " << CRYPTOPP_VERSION / 100;
bench1.cpp: oss << '.' << (CRYPTOPP_VERSION % 100) / 10 << '.' << CRYPTOPP_VERSION % 10 << "</A> Benchmarks</H1>";
cryptlib.cpp:# define CRYPTOPP_BUILD_VERSION CRYPTOPP_VERSION
test.cpp: std::cout << CRYPTOPP_VERSION / 100 << '.' << (CRYPTOPP_VERSION % 100) / 10 << '.' << CRYPTOPP_VERSION % 10 << std::endl;
``` | CRYPTOPP_VERSION has reached its limits | https://api.github.com/repos/weidai11/cryptopp/issues/1239/comments | 3 | 2023-10-01T18:08:46Z | 2023-10-07T19:13:39Z | https://github.com/weidai11/cryptopp/issues/1239 | 1,920,895,773 | 1,239 |
[
"weidai11",
"cryptopp"
] | VS2022 with the current head
> cryptopp-master\validat2.cpp(1177,69): warning C4244: 'argument': conversion from 'CryptoPP::word' to 'long', possible loss of data
Should `m` be declared as `Integer`? | Warning in validat2.cpp | https://api.github.com/repos/weidai11/cryptopp/issues/1238/comments | 0 | 2023-10-01T13:05:50Z | 2023-10-01T13:05:50Z | https://github.com/weidai11/cryptopp/issues/1238 | 1,920,757,942 | 1,238 |
[
"weidai11",
"cryptopp"
] | On `cfarm29.cfarm.net`, which is a [POWER9 machine](https://cfarm.tetaneutral.net/machines/list/), Asan is producing the following failure:
```
$ ./cryptest.exe tv simon
Using seed: 1696129750
Testing SymmetricCipher algorithm SIMON-64/ECB.
................................
Testing SymmetricCipher algorithm SIMON-64/CBC.
............................
Testing SymmetricCipher algorithm SIMON-64/CTR.
..........................................
Testing SymmetricCipher algorithm SIMON-128/ECB.
................=================================================================
==2183894==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x7eaff62ed7a0 at pc 0x000100d23344 bp 0x7fffffff72d0 sp 0x7fffffff72f0
READ of size 16 at 0x7eaff62ed7a0 thread T0
#0 0x100d23340 in CryptoPP::VecLoad(unsigned int const*) /home/noloader/cryptopp/ppc_simd.h:441
#1 0x100d23340 in SIMON128_Dec_Block /home/noloader/cryptopp/simon128_simd.cpp:635
#2 0x100d25c58 in unsigned long CryptoPP::AdvancedProcessBlocks128_6x1_ALTIVEC<void (*)(unsigned int __vector(4)&, unsigned long const*, unsigned int), void (*)(unsigned int __vector(4)&, unsigned int __vector(4)&, unsigned int __vector(4)&, unsigned int __vector(4)&, unsigned int __vector(4)&, unsigned int __vector(4)&, unsigned long const*, unsigned int), unsigned long>(void (*)(unsigned int __vector(4)&, unsigned long const*, unsigned int), void (*)(unsigned int __vector(4)&, unsigned int __vector(4)&, unsigned int __vector(4)&, unsigned int __vector(4)&, unsigned int __vector(4)&, unsigned int __vector(4)&, unsigned long const*, unsigned int), unsigned long const*, unsigned long, unsigned char const*, unsigned char const*, unsigned char*, unsigned long, unsigned int) /home/noloader/cryptopp/adv_simd.h:1261
#3 0x100d23f48 in CryptoPP::SIMON128_Dec_AdvancedProcessBlocks_ALTIVEC(unsigned long const*, unsigned long, unsigned char const*, unsigned char const*, unsigned char*, unsigned long, unsigned int) /home/noloader/cryptopp/simon128_simd.cpp:857
#4 0x100d1c980 in CryptoPP::SIMON128::Dec::AdvancedProcessBlocks(unsigned char const*, unsigned char const*, unsigned char*, unsigned long, unsigned int) const /home/noloader/cryptopp/simon.cpp:498
#5 0x100bd8974 in CryptoPP::ECB_OneWay::ProcessData(unsigned char*, unsigned char const*, unsigned long) /home/noloader/cryptopp/modes.cpp:200
#6 0x100a64f34 in CryptoPP::StreamTransformation::ProcessString(unsigned char*, unsigned long) /home/noloader/cryptopp/cryptlib.h:1066
#7 0x100a64f34 in CryptoPP::StreamTransformationFilter::NextPutModifiable(unsigned char*, unsigned long) /home/noloader/cryptopp/filters.cpp:691
#8 0x100a7b174 in CryptoPP::FilterWithBufferedInput::PutMaybeModifiable(unsigned char*, unsigned long, int, bool, bool) /home/noloader/cryptopp/filters.cpp:403
#9 0x1002121c0 in CryptoPP::FilterWithBufferedInput::Put2(unsigned char const*, unsigned long, int, bool) /home/noloader/cryptopp/filters.h:361
#10 0x100802b3c in CryptoPP::BufferedTransformation::ChannelPut2(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, unsigned char const*, unsigned long, int, bool) /home/noloader/cryptopp/cryptlib.cpp:469
#11 0x10037df20 in CryptoPP::BufferedTransformation::ChannelPut(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, unsigned char const*, unsigned long, bool) /home/noloader/cryptopp/cryptlib.h:2210
#12 0x10037df20 in RandomizedTransfer /home/noloader/cryptopp/datatest.cpp:184
#13 0x10038f554 in TestSymmetricCipher /home/noloader/cryptopp/datatest.cpp:750
#14 0x1003a2568 in TestDataFile /home/noloader/cryptopp/datatest.cpp:1350
#15 0x1003a9570 in CryptoPP::Test::RunTestDataFile(char const*, CryptoPP::NameValuePairs const&, bool) /home/noloader/cryptopp/datatest.cpp:1432
#16 0x100207858 in CryptoPP::Test::scoped_main(int, char**) /home/noloader/cryptopp/test.cpp:347
#17 0x100209770 in main /home/noloader/cryptopp/test.cpp:1097
#18 0x7ffff7024ca8 in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58
#19 0x7ffff7024ee8 in generic_start_main ../csu/libc-start.c:360
#20 0x7ffff7024ee8 in __libc_start_main_impl ../sysdeps/unix/sysv/linux/powerpc/libc-start.c:109
0x7eaff62ed7a8 is located 0 bytes to the right of 552-byte region [0x7eaff62ed580,0x7eaff62ed7a8)
allocated by thread T0 here:
#0 0x7ffff78df604 in __interceptor_memalign ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:99
#1 0x100859bac in CryptoPP::AlignedAllocate(unsigned long) /home/noloader/cryptopp/allocate.cpp:46
#2 0x100d21a5c in CryptoPP::AllocatorWithCleanup<unsigned long, true>::allocate(unsigned long, void const*) /home/noloader/cryptopp/secblock.h:215
#3 0x100d21a5c in CryptoPP::AllocatorWithCleanup<unsigned long, true>::pointer CryptoPP::StandardReallocate<unsigned long, CryptoPP::AllocatorWithCleanup<unsigned long, true> >(CryptoPP::AllocatorWithCleanup<unsigned long, true>&, unsigned long*, CryptoPP::AllocatorWithCleanup<unsigned long, true>::size_type, CryptoPP::AllocatorWithCleanup<unsigned long, true>::size_type, bool) /home/noloader/cryptopp/secblock.h:174
#4 0x100d21a5c in CryptoPP::AllocatorWithCleanup<unsigned long, true>::reallocate(unsigned long*, unsigned long, unsigned long, bool) /home/noloader/cryptopp/secblock.h:262
#5 0x100d21a5c in CryptoPP::SecBlock<unsigned long, CryptoPP::AllocatorWithCleanup<unsigned long, true> >::New(unsigned long) /home/noloader/cryptopp/secblock.h:1128
#6 0x100d21a5c in CryptoPP::SIMON128::Base::UncheckedSetKey(unsigned char const*, unsigned int, CryptoPP::NameValuePairs const&) /home/noloader/cryptopp/simon.cpp:372
#7 0x10080395c in CryptoPP::SimpleKeyingInterface::SetKey(unsigned char const*, unsigned long, CryptoPP::NameValuePairs const&) /home/noloader/cryptopp/cryptlib.cpp:61
#8 0x1003c36ec in CryptoPP::ECB_OneWay::SetKey(unsigned char const*, unsigned long, CryptoPP::NameValuePairs const&) /home/noloader/cryptopp/modes.h:277
#9 0x10038bd14 in TestSymmetricCipher /home/noloader/cryptopp/datatest.cpp:652
#10 0x1003a2568 in TestDataFile /home/noloader/cryptopp/datatest.cpp:1350
#11 0x1003a9570 in CryptoPP::Test::RunTestDataFile(char const*, CryptoPP::NameValuePairs const&, bool) /home/noloader/cryptopp/datatest.cpp:1432
#12 0x100207858 in CryptoPP::Test::scoped_main(int, char**) /home/noloader/cryptopp/test.cpp:347
#13 0x100209770 in main /home/noloader/cryptopp/test.cpp:1097
#14 0x7ffff7024ca8 in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58
#15 0x7ffff7024ee8 in generic_start_main ../csu/libc-start.c:360
#16 0x7ffff7024ee8 in __libc_start_main_impl ../sysdeps/unix/sysv/linux/powerpc/libc-start.c:109
SUMMARY: AddressSanitizer: heap-buffer-overflow /home/noloader/cryptopp/ppc_simd.h:441 in CryptoPP::VecLoad(unsigned int const*)
Shadow bytes around the buggy address:
0x11d5fec5daa0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x11d5fec5dab0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x11d5fec5dac0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x11d5fec5dad0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x11d5fec5dae0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x11d5fec5daf0: 00 00 00 00[00]fa fa fa fa fa fa fa fa fa fa fa
0x11d5fec5db00: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x11d5fec5db10: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x11d5fec5db20: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x11d5fec5db30: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x11d5fec5db40: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
==2183894==ABORTING
``` | SIMON128 Asan failures on POWER8 | https://api.github.com/repos/weidai11/cryptopp/issues/1237/comments | 1 | 2023-10-01T03:12:39Z | 2023-10-01T03:19:51Z | https://github.com/weidai11/cryptopp/issues/1237 | 1,920,523,810 | 1,237 |
[
"weidai11",
"cryptopp"
] | Rabbit, RabbitWithIV, HC128 and HC256 were producing incorrect results when `inString == outString` as reported in [GH #1231](https://github.com/weidai11/cryptopp/issues/1231). We added self tests to detect the failures, and cleared the failures.
The new tests also revealed AES/CFB and AES/CTR modes also has problems on ARMv7. This is an old problem that is resurfaced. Also see [GH #683](https://github.com/weidai11/cryptopp/issues/683) and [GH #1088](https://github.com/weidai11/cryptopp/issues/1088).
This bug will track AES/CFB and AES/CTR on ARMv7. | AES/CFB and AES/CTR modes self test failures on ARMv7 | https://api.github.com/repos/weidai11/cryptopp/issues/1236/comments | 1 | 2023-09-29T19:30:03Z | 2023-09-29T19:41:25Z | https://github.com/weidai11/cryptopp/issues/1236 | 1,919,803,048 | 1,236 |
[
"weidai11",
"cryptopp"
] | Rabbit, RabbitWithIV, HC128 and HC256 were producing incorrect results when `inString == outString` as reported in [GH #1231](https://github.com/weidai11/cryptopp/issues/1231). We added self tests to detect the failures, and cleared the failures.
The new tests also revealed ARIA/CTR mode also has problems. The failure can be duplicated with `./cryptest.exe tv aria`.
This bug will track ARIA/CTR. | ARIA/CTR mode self test failures | https://api.github.com/repos/weidai11/cryptopp/issues/1235/comments | 2 | 2023-09-29T06:45:28Z | 2023-09-30T09:53:12Z | https://github.com/weidai11/cryptopp/issues/1235 | 1,918,689,003 | 1,235 |
[
"weidai11",
"cryptopp"
] | Rabbit, RabbitWithIV, HC128 and HC256 were producing incorrect results when `inString == outString` as reported in [GH #1231](https://github.com/weidai11/cryptopp/issues/1231). We added self tests to detect the failures, and cleared the failures.
The new tests also revealed HIGHT/CTR mode also has problems.
This bug will track HIGHT/CTR. | HIGHT/CTR mode self test failures | https://api.github.com/repos/weidai11/cryptopp/issues/1234/comments | 1 | 2023-09-28T17:08:15Z | 2023-09-29T06:48:59Z | https://github.com/weidai11/cryptopp/issues/1234 | 1,917,949,578 | 1,234 |
[
"weidai11",
"cryptopp"
] | Very old commit b3924f2108c0b0825060e91f6fde8202ce35624d left trailing spaces in lines containing `TEXTINCLUDE` | Trailing spaces in cryptopp.rc | https://api.github.com/repos/weidai11/cryptopp/issues/1233/comments | 1 | 2023-09-28T13:31:43Z | 2023-09-29T10:32:55Z | https://github.com/weidai11/cryptopp/issues/1233 | 1,917,563,829 | 1,233 |
[
"weidai11",
"cryptopp"
] | When upgrading from CryptoPP 8.6.0 to 8.8.0 (master branch via vcpkg), we started having our own unit tests fail with code using the `CryptoPP::RabbitWithIV` algorithm. Upon inspection, it appears when `inString == outString` (which is perfectly legal according to `ProcessData`), Rabbit is returning a buffer with all `0x00` bytes, instead of the encrypted/decrypted buffer.
When I dug into the method, it looks like `RabbitWithIVPolicy::OperateKeystream` ends up just XOR'ing the generated keystream with itself...
Here is a minimal example reproducing the issue with the `Rabbit test vectors, Test 4`. This code passes on CryptoPP 8.6.0, and throws an assertion on CryptoPP 8.8.0. This also applies to `CryptoPP::Rabbit`. Compiled using Visual Studio (x64) on Windows 10.
```C++
#include <cryptopp/rabbit.h>
int main()
{
auto key = std::vector<uint8_t>(CryptoPP::RabbitWithIV::KEYLENGTH, 0x00);
auto iv = std::vector<uint8_t>(CryptoPP::RabbitWithIV::IV_LENGTH, 0x00);
auto buffer = std::vector<uint8_t>(0x20, 0x00);
auto expected = std::vector<uint8_t>{ 0xED, 0xB7, 0x05, 0x67, 0x37, 0x5D, 0xCD, 0x7C, 0xD8, 0x95, 0x54, 0xF8, 0x5E, 0x27, 0xA7, 0xC6, 0x8D, 0x4A, 0xDC, 0x70, 0x32, 0x29, 0x8F, 0x7B, 0xD4, 0xEF, 0xF5, 0x04, 0xAC, 0xA6, 0x29, 0x5F };
CryptoPP::RabbitWithIV::Encryption enc;
enc.SetKeyWithIV(key.data(), key.size(), iv.data(), iv.size());
enc.ProcessData(buffer.data(), buffer.data(), buffer.size());
CRYPTOPP_ASSERT(memcmp(buffer.data(), expected.data(), expected.size()) == 0);
return 0;
}
```
Just to note, we use a _lot_ of CryptoPP algorithms in our codebase, and no other algorithms had this issue so far.
Seems this may be related to https://github.com/weidai11/cryptopp/issues/1010, perhaps a missed algorithm? | Rabbit Produces null Keystream When inString == outString | https://api.github.com/repos/weidai11/cryptopp/issues/1231/comments | 9 | 2023-09-25T19:18:52Z | 2023-09-29T14:54:21Z | https://github.com/weidai11/cryptopp/issues/1231 | 1,912,136,274 | 1,231 |
[
"weidai11",
"cryptopp"
] | "g++ main.cpp -static -pthread -lcryptopp -o main". Program result: Segmentation Fault (core dumped)
"g++ main.cpp -pthread -lcryptopp -o main". Program runs normally
Someone help me pls. Im going crazy | Core dumped | https://api.github.com/repos/weidai11/cryptopp/issues/1230/comments | 0 | 2023-09-23T02:59:13Z | 2023-09-25T20:18:30Z | https://github.com/weidai11/cryptopp/issues/1230 | 1,909,684,713 | 1,230 |
[
"weidai11",
"cryptopp"
] | Hello had this working on a separate project using vcpkg on windows vs2019 v142 build tools, but since I've switched to a different project I'm now getting these errors below. I've seen a few other issues saying this might be a compiler bug, but it compiles on a different project with identical settings? Any help appreciated.
`Error C2238 unexpected token(s) preceding ';' seckey.h 56 `
`Error C2059 syntax error: 'constant' seckey.h 56 `
`Error C2143 syntax error: missing ';' before '}' seckey.h 56 `
I've tried changing my cpp versions but the error still remains.
| Can't compile Windows vs2019 c2238 c2059 c2143 errors | https://api.github.com/repos/weidai11/cryptopp/issues/1229/comments | 2 | 2023-09-12T15:15:17Z | 2023-09-25T20:20:29Z | https://github.com/weidai11/cryptopp/issues/1229 | 1,892,736,964 | 1,229 |
[
"weidai11",
"cryptopp"
] | @weidai11 it looks like the SSL certificate for cryptopp[dot]com expired this morning.
<img width="690" alt="cryptopp com" src="https://github.com/weidai11/cryptopp/assets/1933999/bc5b9367-5f10-4ba7-94ad-9e58e97b3468">
| Expired SSL certificate for cryptopp.com | https://api.github.com/repos/weidai11/cryptopp/issues/1228/comments | 0 | 2023-09-06T02:41:56Z | 2023-09-07T17:33:25Z | https://github.com/weidai11/cryptopp/issues/1228 | 1,883,066,961 | 1,228 |
[
"weidai11",
"cryptopp"
] | ### Crypto++ Issue Report
The file structure is very irregular.
The CPP and header files are in the same folder. The test and library files are mixed together. Please separate these. You can have the include and source folder separately,also the core and the test folder separately.
I need to use this project as a static library cross-platform Visual Studio project, but it cannot be used.
Also, suppose a static library is built using the project. The parent project needs its header files. But the header files don't just contain only function declarations. Sometimes it includes the definition of functions and this leads to link error in jni environment of the android studio environment.
Also, the volume of the project has been expanded. If it has a common section and an algorithms section. It would be nice to be able to isolate a particular algorithm more easily from the entire library.
I need only one encrypt algorithm and It must have limited size.
Briefly, The file structure is very irregular, Correction of it is very easy
Thanks a lot, Majid
| The file structure is very irregular | https://api.github.com/repos/weidai11/cryptopp/issues/1227/comments | 0 | 2023-08-13T11:13:03Z | 2023-08-13T17:04:20Z | https://github.com/weidai11/cryptopp/issues/1227 | 1,848,546,319 | 1,227 |
[
"weidai11",
"cryptopp"
] | Normally, we encrypt with the public key and decrypt with the private key. Now you want to know how to use private key encryption. Public key decryption. I know how to implement it under openssl, but I don't know how to write it using this library. There better be examples.
| help | https://api.github.com/repos/weidai11/cryptopp/issues/1226/comments | 0 | 2023-07-31T02:34:17Z | 2023-07-31T03:11:53Z | https://github.com/weidai11/cryptopp/issues/1226 | 1,828,265,413 | 1,226 |
[
"weidai11",
"cryptopp"
] | Hi Crypto++ Developers,
I would like to add [scons](https://scons.org/doc/4.0.0/HTML/scons-user.html) support to cryptopp as well as makefile support. Scons is written in python programming language and has a very understandable and simple structure.
Integration of one of the modern build systems like Scons can solve all build problems under Windows. Additionally, it's written with python syntax, which is pretty straightforward according to a makefile. It doesn't have its own syntax like Cmake or Makefile. For example, someone who is familiar with the compiler toolset for iOS can quickly implement Scons for iOS.
Now let me talk about a problem of developers working / having to work on Windows.
One of the current compilation issues is that even with MinGW64 installed on the Windows machine, it is not possible to compile the project without opening Git Bash or working on a tool like MSYS2.
With scons support, users can compile by installing python and scons on their machines if they wish. Tools like Git Bash are not needed.
Before I go into more details, I'd like to know if this is reasonable. If accepted, I can take over the maintenance of the Scons scripts (at least I will for MSVC and MinGW64 on Windows). | implementing request to add new build system: scons | https://api.github.com/repos/weidai11/cryptopp/issues/1225/comments | 1 | 2023-07-12T09:17:28Z | 2023-09-25T20:25:22Z | https://github.com/weidai11/cryptopp/issues/1225 | 1,800,542,897 | 1,225 |
[
"weidai11",
"cryptopp"
] | ### Crypto++ Issue Report
Just update vcpkg files to take into account last releases
| Update vcpkg repo to last version | https://api.github.com/repos/weidai11/cryptopp/issues/1224/comments | 1 | 2023-07-11T16:07:12Z | 2023-07-11T16:09:35Z | https://github.com/weidai11/cryptopp/issues/1224 | 1,799,276,768 | 1,224 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.