{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":371383357,"defaultBranch":"master","name":"cryptvault","ownerLogin":"bolcom","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2021-05-27T13:29:07.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/2914076?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1722408049.0","currentOid":""},"activityList":{"items":[{"before":null,"after":"1a8f1af4b3f414e5dc03759361a76c323ea7a1c4","ref":"refs/heads/sra/externalize-config","pushedAt":"2024-07-31T06:40:49.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"svandenakker","name":"Stefan van den Akker","path":"/svandenakker","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/103565568?s=80&v=4"},"commit":{"message":"feat: externalize config\n\nThis commit adds the ability for a user to specify the algorithm/mode of\noperation/padding directly in their `application.yml`. This is pretty\nflexible and allows the user easy access to many JCA \"transformations\"\nwithout them needing to write any code. A new, incompatible format for\nthe encrypted binary blob is introduced to achieve this. The versioned\nformat allows us to make continuous improvements to it without rendering\nall previous outputs undecryptable. Provisions were made for version-1\noutputs: these can still be decrypted. When migrating from version 1 to\nversion 2, legacy key versions should be marked as such in the config.\nThese key versions are then only allowed to decrypt: no new encryptions\ncan be performed with them.","shortMessageHtmlLink":"feat: externalize config"}},{"before":null,"after":"8ba35edfe28550cbae73262d5ceca64009a4ac2a","ref":"refs/heads/sra/remove-mandatory-iv","pushedAt":"2024-07-16T10:06:15.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"svandenakker","name":"Stefan van den Akker","path":"/svandenakker","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/103565568?s=80&v=4"},"commit":{"message":"feat: allow using ciphers with no IV or the same IV for every encryption\n\nThis commit enables modes of operation that do not require an IV, such\nas ECB. It also allows reusing of IVs. This is not recommended if it can\nbe avoided, because if the (first few blocks of) plaintext are the same,\nthe (first few blocks of) the ciphertext will be the same, thus\ndisclosing information. However, this can be useful to implement a form\nof \"searchable encryption\", where one can search whether a string is\npresent without having to decrypt all ciphertexts first.\n\nThis commit also renames references to \"salt\" with \"IV\". A salt is some\nrandom string added to a passphrase. Some algorithm (such as PBKDF2) is\nthen used to derive a key from this passphrase. This key is then used by\nthe block cipher. The salt makes sure the same passphrase does not\nalways result in the same key. An IV, on the other hand, is used by a\nblock cipher mode of operation (such as CBC) to ensure that the same\nplaintext does not always encrypt to the same ciphertext. In this case,\nit is clear \"IV\" was meant.","shortMessageHtmlLink":"feat: allow using ciphers with no IV or the same IV for every encryption"}},{"before":null,"after":"97f5b5b2274ac3c3096bf85988a5242acf5c5451","ref":"refs/heads/spring-boot-3","pushedAt":"2024-04-09T14:33:19.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"svandenakker","name":"Stefan van den Akker","path":"/svandenakker","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/103565568?s=80&v=4"},"commit":{"message":"chore: make POM ready for deployment to Maven Central\n\nThis commit basically follows the guidelines outlined [here][1]:\n\n* Update the SCM section.\n* Add a new developer (svandenakker@bol.com, PGP key ID BE65F50D) as\n developer to this project.\n* Create a `release` profile that will attach the source code, generate\n javadoc and sign the artifacts with the private key of the releaser.\n This is in a separate profile because these tasks take time and are\n only necessary when releasing to Maven Central.\n\nWhen releasing in the future, these are the steps to follow:\n\n* Develop\n* Commit any outstanding changes\n* Run tests, make sure build passes\n* Update versions to release version\n* Commit release version\n* Run deployment\n* Update versions to next snapshot version\n* Commit new snapshot version\n* Develop, develop, develop and rinse and repeat\n\n[1]: ","shortMessageHtmlLink":"chore: make POM ready for deployment to Maven Central"}},{"before":"e613b72b835e5ca042264e3561f08f7ea74cb863","after":"97f5b5b2274ac3c3096bf85988a5242acf5c5451","ref":"refs/heads/master","pushedAt":"2024-04-08T09:15:38.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"svandenakker","name":"Stefan van den Akker","path":"/svandenakker","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/103565568?s=80&v=4"},"commit":{"message":"chore: make POM ready for deployment to Maven Central\n\nThis commit basically follows the guidelines outlined [here][1]:\n\n* Update the SCM section.\n* Add a new developer (svandenakker@bol.com, PGP key ID BE65F50D) as\n developer to this project.\n* Create a `release` profile that will attach the source code, generate\n javadoc and sign the artifacts with the private key of the releaser.\n This is in a separate profile because these tasks take time and are\n only necessary when releasing to Maven Central.\n\nWhen releasing in the future, these are the steps to follow:\n\n* Develop\n* Commit any outstanding changes\n* Run tests, make sure build passes\n* Update versions to release version\n* Commit release version\n* Run deployment\n* Update versions to next snapshot version\n* Commit new snapshot version\n* Develop, develop, develop and rinse and repeat\n\n[1]: ","shortMessageHtmlLink":"chore: make POM ready for deployment to Maven Central"}},{"before":"502aabfaef7eab8b27ee51ac0cdbbea451f49039","after":null,"ref":"refs/heads/dependabot/maven/org.springframework.boot-spring-boot-autoconfigure-2.5.15","pushedAt":"2024-03-14T10:10:02.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"dependabot[bot]","name":null,"path":"/apps/dependabot","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/29110?s=80&v=4"}},{"before":"ee5a9c594e5245506b31582c670bc34d73030a57","after":"e613b72b835e5ca042264e3561f08f7ea74cb863","ref":"refs/heads/master","pushedAt":"2024-03-14T10:02:19.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"svandenakker","name":"Stefan van den Akker","path":"/svandenakker","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/103565568?s=80&v=4"},"commit":{"message":"chore: upgrade \"Jave project with Maven\" GitHub action\n\nThe old version was deprecated.","shortMessageHtmlLink":"chore: upgrade \"Jave project with Maven\" GitHub action"}},{"before":null,"after":"502aabfaef7eab8b27ee51ac0cdbbea451f49039","ref":"refs/heads/dependabot/maven/org.springframework.boot-spring-boot-autoconfigure-2.5.15","pushedAt":"2023-05-26T22:16:43.163Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"dependabot[bot]","name":null,"path":"/apps/dependabot","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/29110?s=80&v=4"},"commit":{"message":"Bump spring-boot-autoconfigure from 2.4.0 to 2.5.15\n\nBumps [spring-boot-autoconfigure](https://github.com/spring-projects/spring-boot) from 2.4.0 to 2.5.15.\n- [Release notes](https://github.com/spring-projects/spring-boot/releases)\n- [Commits](https://github.com/spring-projects/spring-boot/compare/v2.4.0...v2.5.15)\n\n---\nupdated-dependencies:\n- dependency-name: org.springframework.boot:spring-boot-autoconfigure\n dependency-type: direct:production\n...\n\nSigned-off-by: dependabot[bot] ","shortMessageHtmlLink":"Bump spring-boot-autoconfigure from 2.4.0 to 2.5.15"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEjbgm9wA","startCursor":null,"endCursor":null}},"title":"Activity ยท bolcom/cryptvault"}