{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":428662235,"defaultBranch":"master","name":"secure-kernel-loader","ownerLogin":"TrenchBoot","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2021-11-16T13:16:21.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/36201946?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1722807927.0","currentOid":""},"activityList":{"items":[{"before":"37af5050630377370befbd75e1353981252edb70","after":"7d2b133229f1d4ac4050f8971b593cfbfcd319ea","ref":"refs/heads/update-slrt","pushedAt":"2024-08-04T21:51:00.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"SergiiDmytruk","name":null,"path":"/SergiiDmytruk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/81815690?s=80&v=4"},"commit":{"message":"include/slrt.h: update sizes and order of fields\n\nThis results in 64-bit alignment of 64-bit fields.\n\nSigned-off-by: Sergii Dmytruk ","shortMessageHtmlLink":"include/slrt.h: update sizes and order of fields"}},{"before":"18f535843b22e784dbbc8e1ec11d8dc099b3d0fe","after":"37af5050630377370befbd75e1353981252edb70","ref":"refs/heads/update-slrt","pushedAt":"2024-08-04T21:48:32.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"SergiiDmytruk","name":null,"path":"/SergiiDmytruk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/81815690?s=80&v=4"},"commit":{"message":"include/slrt.h: update sizes and order or fields\n\nThis results in 64-bit alignment of 64-bit fields.\n\nSigned-off-by: Sergii Dmytruk ","shortMessageHtmlLink":"include/slrt.h: update sizes and order or fields"}},{"before":null,"after":"18f535843b22e784dbbc8e1ec11d8dc099b3d0fe","ref":"refs/heads/update-slrt","pushedAt":"2024-08-04T21:45:27.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"SergiiDmytruk","name":null,"path":"/SergiiDmytruk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/81815690?s=80&v=4"},"commit":{"message":"dev: loop over CPU nodes on disabling memory protection\n\nDEV is specific to a northbridge, so there are multiple of them on\nsystems with several CPU sockets. 0x18 is the device number of the\nfirst one with the rest using successive numbers (0x19, 0x1A, etc.).\n\nSigned-off-by: Sergii Dmytruk ","shortMessageHtmlLink":"dev: loop over CPU nodes on disabling memory protection"}},{"before":"a3a13422ec0935258d6f581623bdceb64b30c832","after":null,"ref":"refs/tags/ci-test-tag","pushedAt":"2024-05-16T11:08:26.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"krystian-hebel","name":"Krystian Hebel","path":"/krystian-hebel","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/40995177?s=80&v=4"}},{"before":"cff8ab0e6e57c8d845d972c075463ea569be2aef","after":null,"ref":"refs/tags/testing_ci","pushedAt":"2024-05-16T11:08:22.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"krystian-hebel","name":"Krystian Hebel","path":"/krystian-hebel","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/40995177?s=80&v=4"}},{"before":"96657b5713b5ed9a5ff6228626bd67399f1cb251","after":null,"ref":"refs/heads/test_ci","pushedAt":"2024-05-16T11:07:41.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"krystian-hebel","name":"Krystian Hebel","path":"/krystian-hebel","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/40995177?s=80&v=4"}},{"before":null,"after":"96657b5713b5ed9a5ff6228626bd67399f1cb251","ref":"refs/heads/test_ci","pushedAt":"2024-05-13T13:12:01.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"krystian-hebel","name":"Krystian Hebel","path":"/krystian-hebel","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/40995177?s=80&v=4"},"commit":{"message":"NOT FOR MERGE: test CI after bumping release-action\n\nSigned-off-by: Krystian Hebel ","shortMessageHtmlLink":"NOT FOR MERGE: test CI after bumping release-action"}},{"before":"18f535843b22e784dbbc8e1ec11d8dc099b3d0fe","after":null,"ref":"refs/heads/handle-multiple-nodes","pushedAt":"2024-04-17T18:36:32.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"krystian-hebel","name":"Krystian Hebel","path":"/krystian-hebel","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/40995177?s=80&v=4"}},{"before":"c00c554c793508a5719661105a6d6929249b0945","after":"18f535843b22e784dbbc8e1ec11d8dc099b3d0fe","ref":"refs/heads/shrink_measured_size","pushedAt":"2024-04-17T18:36:26.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"krystian-hebel","name":"Krystian Hebel","path":"/krystian-hebel","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/40995177?s=80&v=4"},"commit":{"message":"dev: loop over CPU nodes on disabling memory protection\n\nDEV is specific to a northbridge, so there are multiple of them on\nsystems with several CPU sockets. 0x18 is the device number of the\nfirst one with the rest using successive numbers (0x19, 0x1A, etc.).\n\nSigned-off-by: Sergii Dmytruk ","shortMessageHtmlLink":"dev: loop over CPU nodes on disabling memory protection"}},{"before":"951f504307833b994a00879e7142e33e43c8ee6c","after":"18f535843b22e784dbbc8e1ec11d8dc099b3d0fe","ref":"refs/heads/handle-multiple-nodes","pushedAt":"2024-04-17T18:27:45.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"SergiiDmytruk","name":null,"path":"/SergiiDmytruk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/81815690?s=80&v=4"},"commit":{"message":"dev: loop over CPU nodes on disabling memory protection\n\nDEV is specific to a northbridge, so there are multiple of them on\nsystems with several CPU sockets. 0x18 is the device number of the\nfirst one with the rest using successive numbers (0x19, 0x1A, etc.).\n\nSigned-off-by: Sergii Dmytruk ","shortMessageHtmlLink":"dev: loop over CPU nodes on disabling memory protection"}},{"before":"c00c554c793508a5719661105a6d6929249b0945","after":null,"ref":"refs/heads/iommu_updates","pushedAt":"2024-04-17T17:47:55.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"macpijan","name":"Maciej Pijanowski","path":"/macpijan","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/19353650?s=80&v=4"}},{"before":"8c4fea6af765fa87e1f01e60bedd283b6c74c40e","after":"c00c554c793508a5719661105a6d6929249b0945","ref":"refs/heads/shrink_measured_size","pushedAt":"2024-04-17T17:47:47.000Z","pushType":"push","commitsCount":4,"pusher":{"login":"macpijan","name":"Maciej Pijanowski","path":"/macpijan","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/19353650?s=80&v=4"},"commit":{"message":"sha1sum.c, sha256.c: make code work with -fstrict-aliasing\n\n-fstrict-aliasing is enabled by default when using optimization levels\nhigher than 1, including -Os. With that option, compiler may assume\nthat object of one type never resides at the same address as object of\na different type. Both sha1_final() and sha256_final() used to write\nmessage length by casting a pointer to buffer into a pointer to u64,\nwhile surrounding code operated on the buffer directly.\n\nThe problem manifests in GCC 11 and later versions.\n\nThe commit fixes this issue and another UB caused by unaligned access\nat the beginning of transformation step by using memcpy() in both cases.\n\nSigned-off-by: Krystian Hebel \nSigned-off-by: Sergii Dmytruk ","shortMessageHtmlLink":"sha1sum.c, sha256.c: make code work with -fstrict-aliasing"}},{"before":"c00c554c793508a5719661105a6d6929249b0945","after":null,"ref":"refs/heads/make_tests","pushedAt":"2024-04-17T17:46:44.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"macpijan","name":"Maciej Pijanowski","path":"/macpijan","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/19353650?s=80&v=4"}},{"before":"f16a0d0651f8dc5a22d098ee98f6f9daf4d98618","after":"c00c554c793508a5719661105a6d6929249b0945","ref":"refs/heads/iommu_updates","pushedAt":"2024-04-17T17:46:38.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"macpijan","name":"Maciej Pijanowski","path":"/macpijan","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/19353650?s=80&v=4"},"commit":{"message":"sha1sum.c, sha256.c: make code work with -fstrict-aliasing\n\n-fstrict-aliasing is enabled by default when using optimization levels\nhigher than 1, including -Os. With that option, compiler may assume\nthat object of one type never resides at the same address as object of\na different type. Both sha1_final() and sha256_final() used to write\nmessage length by casting a pointer to buffer into a pointer to u64,\nwhile surrounding code operated on the buffer directly.\n\nThe problem manifests in GCC 11 and later versions.\n\nThe commit fixes this issue and another UB caused by unaligned access\nat the beginning of transformation step by using memcpy() in both cases.\n\nSigned-off-by: Krystian Hebel \nSigned-off-by: Sergii Dmytruk ","shortMessageHtmlLink":"sha1sum.c, sha256.c: make code work with -fstrict-aliasing"}},{"before":"8ef5b89b3de1b640a39f96e22d1bcf0e4b4ecb97","after":"c00c554c793508a5719661105a6d6929249b0945","ref":"refs/heads/make_tests","pushedAt":"2024-04-17T17:16:02.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"krystian-hebel","name":"Krystian Hebel","path":"/krystian-hebel","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/40995177?s=80&v=4"},"commit":{"message":"sha1sum.c, sha256.c: make code work with -fstrict-aliasing\n\n-fstrict-aliasing is enabled by default when using optimization levels\nhigher than 1, including -Os. With that option, compiler may assume\nthat object of one type never resides at the same address as object of\na different type. Both sha1_final() and sha256_final() used to write\nmessage length by casting a pointer to buffer into a pointer to u64,\nwhile surrounding code operated on the buffer directly.\n\nThe problem manifests in GCC 11 and later versions.\n\nThe commit fixes this issue and another UB caused by unaligned access\nat the beginning of transformation step by using memcpy() in both cases.\n\nSigned-off-by: Krystian Hebel \nSigned-off-by: Sergii Dmytruk ","shortMessageHtmlLink":"sha1sum.c, sha256.c: make code work with -fstrict-aliasing"}},{"before":"9db046cd677666fa0e18b0f1314476ff96334e49","after":"8ef5b89b3de1b640a39f96e22d1bcf0e4b4ecb97","ref":"refs/heads/make_tests","pushedAt":"2024-04-17T13:31:20.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"SergiiDmytruk","name":null,"path":"/SergiiDmytruk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/81815690?s=80&v=4"},"commit":{"message":"WIP: get rid of UB\n\nSigned-off-by: Sergii Dmytruk ","shortMessageHtmlLink":"WIP: get rid of UB"}},{"before":"589a643bf74486b09398db8fb86c9c6f75f37f6c","after":"951f504307833b994a00879e7142e33e43c8ee6c","ref":"refs/heads/handle-multiple-nodes","pushedAt":"2024-04-16T21:24:36.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"SergiiDmytruk","name":null,"path":"/SergiiDmytruk","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/81815690?s=80&v=4"},"commit":{"message":"dev: loop over CPU nodes on disabling memory protection\n\nDEV is specific to a northbridge, so there are multiple of them on\nsystems with several CPU sockets. 0x18 is the device number of the\nfirst one with the rest using successive numbers (0x19, 0x1A, etc.).\n\nSigned-off-by: Sergii Dmytruk ","shortMessageHtmlLink":"dev: loop over CPU nodes on disabling memory protection"}},{"before":"d22cfcfce60eee0817b05db0215b7968b87296bf","after":"9db046cd677666fa0e18b0f1314476ff96334e49","ref":"refs/heads/make_tests","pushedAt":"2024-04-16T12:49:22.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"krystian-hebel","name":"Krystian Hebel","path":"/krystian-hebel","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/40995177?s=80&v=4"},"commit":{"message":"sha1sum.c, sha256.c: make code work with -fstrict-aliasing\n\n-fstrict-aliasing is enabled by default when using optimization levels\nhigher than 1, including -Os. With that option, compiler may assume\nthat object of one type never resides at the same address as object of\na different type. Both sha1_final() and sha256_final() used to write\nmessage length by casting a pointer to buffer into a pointer to u64,\nwhile surrounding code operated on the buffer directly.\n\nThe problem manifests in GCC 11 (and possibly later versions).\n\nTo solve this problem, the commit adds message length field to SHA\ncontext structures and accesses it through the structure, without any\ncasting to different types. Message length is declared volatile,\notherwise compiler doesn't write it before address of buffer is\nobtained and passed to sha*_transform().\n\nSigned-off-by: Krystian Hebel ","shortMessageHtmlLink":"sha1sum.c, sha256.c: make code work with -fstrict-aliasing"}},{"before":"d2cb1b776cd1c44abedbd0f68401d62c46b6e05a","after":"f16a0d0651f8dc5a22d098ee98f6f9daf4d98618","ref":"refs/heads/iommu_updates","pushedAt":"2024-04-16T12:45:34.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"krystian-hebel","name":"Krystian Hebel","path":"/krystian-hebel","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/40995177?s=80&v=4"},"commit":{"message":"tpmlib/tis.c: work around poor TPM implementations\n\nRelease versions of SKL hanged in tis_send(), while versions with serial\noutput worked, most likely thanks to increased delay between DRTM\nsequence and next TPM command. Apparently, some TPMs don't properly\nhandle setting STS.commandReady when all of the following conditions are\nmet:\n\n- TPM has recently finished DRTM sequence (internal work may still be\n happening at that point, there is no way to be sure),\n- TPM just transitioned to Idle state (e.g. by changing locality),\n- STS.commandReady is written periodically before TPM reports it is in\n Ready state.\n\nWhen all of the above applies, STS.commandReady is always read as 0,\nas if the TPM restarted transition from Idle to Ready each time it is\nasked to do so. To work around this, set this bit once and keep checking\nin a loop until TIMEOUT_B (2 seconds). Well behaving TPM must be able to\nenter Ready state before that time, if it doesn't, error is returned.\n\nSigned-off-by: Krystian Hebel ","shortMessageHtmlLink":"tpmlib/tis.c: work around poor TPM implementations"}},{"before":"43049429092897dd3fe6663eb9c5329f12f012b1","after":"d2cb1b776cd1c44abedbd0f68401d62c46b6e05a","ref":"refs/heads/iommu_updates","pushedAt":"2024-04-16T12:34:11.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"krystian-hebel","name":"Krystian Hebel","path":"/krystian-hebel","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/40995177?s=80&v=4"},"commit":{"message":"tpmlib/tis.c: work around poor TPM implementations\n\nRelease versions of SKL hanged in tis_send(), while versions with serial\noutput worked, most likely thanks to increased delay between DRTM\nsequence and next TPM command. Apparently, some TPMs don't properly\nhandle setting STS.commandReady when all of the following conditions are\nmet:\n\n- TPM has recently finished DRTM sequence (internal work may still be\n happening at that point, there is no way to be sure),\n- TPM just transitioned to Idle state (e.g. by changing locality),\n- STS.commandReady is written periodically before TPM reports it is in\n Ready state.\n\nWhen all of the above applies, STS.commandReady is always read as 0,\nas if the TPM restarted transition from Idle to Ready each time it is\nasked to do so. To work around this, set this bit once and keep checking\nin a loop until TIMEOUT_B (2 seconds). Well behaving TPM must be able to\nenter Ready state before that time, if it doesn't, error is returned.\n\nSigned-off-by: Krystian Hebel ","shortMessageHtmlLink":"tpmlib/tis.c: work around poor TPM implementations"}},{"before":"2740b9da0d5f11c1622d30a037d60d75f537b5f7","after":null,"ref":"refs/heads/slrt","pushedAt":"2024-04-16T10:28:36.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"macpijan","name":"Maciej Pijanowski","path":"/macpijan","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/19353650?s=80&v=4"}},{"before":"2fbf539bd18553e9cdbeb68d59eb3b507056b787","after":"d22cfcfce60eee0817b05db0215b7968b87296bf","ref":"refs/heads/make_tests","pushedAt":"2024-04-15T12:27:57.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"krystian-hebel","name":"Krystian Hebel","path":"/krystian-hebel","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/40995177?s=80&v=4"},"commit":{"message":"sha1sum.c, sha256.c: make code work with -fstrict-aliasing\n\n-fstrict-aliasing is enabled by default when using optimization levels\nhigher than 1, including -Os. With that option, compiler may assume\nthat object of one type never resides at the same address as object of\na different type. Both sha1_final() and sha256_final() used to write\nmessage length by casting a pointer to buffer into a pointer to u64,\nwhile surrounding code operated on the buffer directly.\n\nThe problem manifests in GCC 11 (and possibly later versions).\n\nTo solve this problem, the commit adds message length field to SHA\ncontext structures and accesses it through the structure, without any\ncasting to different types. Message length is declared volatile,\notherwise compiler doesn't write it before address of buffer is\nobtained and passed to sha*_transform().\n\nSigned-off-by: Krystian Hebel ","shortMessageHtmlLink":"sha1sum.c, sha256.c: make code work with -fstrict-aliasing"}},{"before":"34ba175ea8fac7739a90785f471550883fb0f3ff","after":"2fbf539bd18553e9cdbeb68d59eb3b507056b787","ref":"refs/heads/make_tests","pushedAt":"2024-04-15T12:13:19.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"krystian-hebel","name":"Krystian Hebel","path":"/krystian-hebel","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/40995177?s=80&v=4"},"commit":{"message":"sha1sum.c, sha256.c: make code work with -fstrict-aliasing\n\n-fstrict-aliasing is enabled by default when using optimization levels\nhigher than 1, including -Os. With that option, compiler may assume\nthat object of one type never resides at the same address as object of\na different type. Both sha1_final() and sha256_final() used to write\nmessage length by casting a pointer to buffer into a pointer to u64,\nwhile surrounding code operated on the buffer directly.\n\nThe problem manifests in GCC 11 (and possibly later versions).\n\nTo solve this problem, the commit adds message length field to SHA\ncontext structures and accesses it through the structure, without any\ncasting to different types.\n\nSigned-off-by: Krystian Hebel ","shortMessageHtmlLink":"sha1sum.c, sha256.c: make code work with -fstrict-aliasing"}},{"before":"b790c717600ea9a026c7ad8345f46fcf3ac326c9","after":"34ba175ea8fac7739a90785f471550883fb0f3ff","ref":"refs/heads/make_tests","pushedAt":"2024-04-15T11:56:13.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"krystian-hebel","name":"Krystian Hebel","path":"/krystian-hebel","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/40995177?s=80&v=4"},"commit":{"message":"sha1sum.c, sha256.c: make code work with -fstrict-aliasing\n\n-fstrict-aliasing is enabled by default when using optimization levels\nhigher than 1, including -Os. With that option, compiler may assume\nthat object of one type never resides at the same address as object of\na different type. Both sha1_final() and sha256_final() used to write\nmessage length by casting a pointer to buffer into a pointer to u64,\nwhile surrounding code operated on the buffer directly.\n\nThe problem manifests in GCC 11 (and possibly later versions).\n\nTo solve this problem, the commit adds message length field to SHA\ncontext structures and accesses it through the structure, without any\ncasting to different types.\n\nSigned-off-by: Krystian Hebel ","shortMessageHtmlLink":"sha1sum.c, sha256.c: make code work with -fstrict-aliasing"}},{"before":"90540fec8b5b5c26575fefd281f14d2faeeccbb6","after":"b790c717600ea9a026c7ad8345f46fcf3ac326c9","ref":"refs/heads/make_tests","pushedAt":"2024-04-15T11:06:15.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"krystian-hebel","name":"Krystian Hebel","path":"/krystian-hebel","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/40995177?s=80&v=4"},"commit":{"message":"sha1sum.c, sha256.c: make code work with -fstrict-aliasing\n\n-fstrict-aliasing is enabled by default when using optimization levels\nhigher than 1, including -Os. With that option, compiler may assume\nthat object of one type never resides at the same address as object of\na different type. Both sha1_final() and sha256_final() used to write\nmessage length by casting a pointer to buffer into a pointer to u64,\nwhile surrounding code operated on the buffer directly.\n\nThe problem manifests in GCC 11 (and possibly later versions).\n\nTo solve this problem, the commit adds message length field to SHA\ncontext structures and accesses it through the structure, without any\ncasting to different types.\n\nSigned-off-by: Krystian Hebel ","shortMessageHtmlLink":"sha1sum.c, sha256.c: make code work with -fstrict-aliasing"}},{"before":"5726b379b5dbb6a0ae21d2fb503d279e0978bc8b","after":"90540fec8b5b5c26575fefd281f14d2faeeccbb6","ref":"refs/heads/make_tests","pushedAt":"2024-04-15T10:27:52.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"krystian-hebel","name":"Krystian Hebel","path":"/krystian-hebel","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/40995177?s=80&v=4"},"commit":{"message":".github/workflows/build.yml: run 'make tests'\n\nThis enables SHA tests to check if different compilers produce the same\nresults.\n\nDefinitions in string.h were moved outside of __STDC_HOSTED__ to avoid\ncompiler warnings (promoted to errors because of -Werror) due to\nincompatible implicit declaration of built-in functions.\n\nSigned-off-by: Krystian Hebel ","shortMessageHtmlLink":".github/workflows/build.yml: run 'make tests'"}},{"before":"bc84bc2154ee90bafc7b16c6849d96b08eed1362","after":"5726b379b5dbb6a0ae21d2fb503d279e0978bc8b","ref":"refs/heads/make_tests","pushedAt":"2024-04-15T10:06:45.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"krystian-hebel","name":"Krystian Hebel","path":"/krystian-hebel","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/40995177?s=80&v=4"},"commit":{"message":".github/workflows/build.yml: run 'make tests'\n\nThis enables SHA tests to check if different compilers produce the same\nresults.\n\nSigned-off-by: Krystian Hebel ","shortMessageHtmlLink":".github/workflows/build.yml: run 'make tests'"}},{"before":"5163cdc3e8c1b472b54898c03f232611bdd86dbb","after":"bc84bc2154ee90bafc7b16c6849d96b08eed1362","ref":"refs/heads/make_tests","pushedAt":"2024-04-15T10:05:12.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"krystian-hebel","name":"Krystian Hebel","path":"/krystian-hebel","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/40995177?s=80&v=4"},"commit":{"message":".github/workflows/build.yml: run 'make tests'\n\nThis enables SHA tests to check if different compilers produce the same\nresults.\n\nSigned-off-by: Krystian Hebel ","shortMessageHtmlLink":".github/workflows/build.yml: run 'make tests'"}},{"before":"4125d0295bd3137adbf3103dccdd690fdfdfed6b","after":"5163cdc3e8c1b472b54898c03f232611bdd86dbb","ref":"refs/heads/make_tests","pushedAt":"2024-04-15T09:55:04.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"krystian-hebel","name":"Krystian Hebel","path":"/krystian-hebel","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/40995177?s=80&v=4"},"commit":{"message":".github/workflows/build.yml: run 'make tests'\n\nThis enables SHA tests to check if different compilers produce the same\nresults.\n\nSigned-off-by: Krystian Hebel ","shortMessageHtmlLink":".github/workflows/build.yml: run 'make tests'"}},{"before":"bef3b091cb0f454feb6c27af4f65d383fabeacf8","after":"4125d0295bd3137adbf3103dccdd690fdfdfed6b","ref":"refs/heads/make_tests","pushedAt":"2024-04-15T09:52:41.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"krystian-hebel","name":"Krystian Hebel","path":"/krystian-hebel","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/40995177?s=80&v=4"},"commit":{"message":".github/workflows/build.yml: run 'make tests'\n\nThis enables SHA tests to check if different compilers produce the same\nresults.\n\nSigned-off-by: Krystian Hebel ","shortMessageHtmlLink":".github/workflows/build.yml: run 'make tests'"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEkXpNugA","startCursor":null,"endCursor":null}},"title":"Activity ยท TrenchBoot/secure-kernel-loader"}