gitbook | 📝 Modern documentation format and toolchain using Git

I found this answer on tex.stackexchange.com which brought me on the right track to solve my problem.

Here is what I am doing.

1. Create boxes.lua with following function:

Your second approach can work, but in a roundabout way, as mikefarah/yq does not support updating multi-line block literals yet

One way to solve this, with the existing constructs would be to do below, without having to create a temporary YAML file

It can be accomplished by doing a recursive decent to identify keys matching your string and update their value part using |=

• You are using the wrong encoders for data, key and IV. All three are Base64 encoded (and not hex or Utf8). So apply the Base64 encoder.
• The ciphertext must be passed to CryptoJS.AES.decrypt() as a CipherParams object or alternatively Base64 encoded, which is implicitly converted to a CipherParams object.

When both are fixed, the plain text is: "[\"001\",\"001\"]".

There are some encoding bugs in the code:

• keygen.randomPassword() does not return a hex encoded string, nevertheless the hex encoder is used for parsing. A hex encoded key and IV can be generated e.g. as follows:

You do not need to use a transaction. You should use a transaction if and only if you want to undo the added Company, 'users' relation when something goes wrong adding the Company, 'deals' relation. Transactions are just a way of making the queries within it atomic (ie all occur or none occur).

As far as query runner releasing - I'm not sure. I haven't used query runner at all. I'm not sure why you are, actually, so maybe this is a bad answer? I use getRepository for everything. ie either getRepository(Company).createQueryBuilder('company')

Or

getRepository(Company).find('primary key value')

should both work, assuming you create the connection on server startup.

Both codes use the OpenSSL proprietary key derivation function EVP_BytesToKey() with an iteration count of 1 and MD5 as digest.
NodeJS does not use a salt, while CryptoJS applies a random salt. For this reason, the NodeJS result is unchanged for each encryption, while the CryptoJS result always changes (assuming the same plaintext and passphrase).

Thus, to get the result of the NodeJS code with the CryptoJS code, you must not use a salt. However, by default, a salt is always applied. This can only be circumvented by explicitly determining key and IV with the key derivation function EvpKDF and then using both in the encryption:

If you intention is to newly create masterZones on the test.txt or completely overwrite the values present in it, you could do

Based on this issue

https://github.com/semantic-release/semantic-release/issues/1593

you also need the npm module.

• npm install @semantic-release/npm -D
• add "private": true, to your package.json if you don't want to publish to npm
• add the npm plugin to the release configuration file (the order matters)

.