Error generating previews in latest version

[davidrutland]

Latest version:

Docker logs output:

Started development server: http://localhost:5000
Error generating preview: 198 | if(!forge.util.isArray(key)) {
199 | tmp = key;
200 | key = [];
201 |
202 | // key lengths of 16, 24, 32 bytes allowed
203 | var len = tmp.length();
^
TypeError: tmp.length is not a function. (In 'tmp.length()', 'tmp.length' is 8)
at (/app/node_modules/node-forge/lib/aes.js:203:19)
at new (/app/node_modules/node-forge/lib/cipher.js:118:18)
at (/app/node_modules/node-forge/lib/cipher.js:42:10)
at encrypt (/app/utilities/security.utility.ts:7:31)
at (/app/index.ts:294:26)

[TBosak]

You'll need to make your encryption key at least 16 characters, that should resolve this issue.

Edit: I don't believe I set up previews for email feeds yet. 😬 I'll work on that today.

[bigdale123]

Hi, i've recently tried self hosting mkfd and ran into a similar issue. It looks like this is might be an upstream issue in node-forge (I hope that's the right way to describe it), As mentioned in This Issue. I am trying to chase it down, I think it's a relatively simple fix (if the problem is what I think it is 🙂 ).

The only reason I even thought it might be an upstream issue is because I tried this with a key of lengths 16 and 17, which should work, but didn't and resulted in the same error.

[bigdale123]

I have an update! After waiting for a response on the upstream issue and not getting one, I decided to just make the PR anyway. The worst they can do is reject it. Here is that in case anybody wants to keep tabs on it. digitalbazaar/forge#1111

[TBosak]

@bigdale123 - thanks for chasing this down, hopefully it fixes the issue. Odd that this isn't happening to more people. I removed forge-related code from the preview endpoint altogether, so email previews still aren't possible, but this issue shouldn't show up while trying to preview other types of feeds for now. Are you guys getting this issue after setting up an email feed at all? I've had no trouble personally with this.

EDIT: If this doesn't resolve, I'll find an alternative package for password encryption.

[bigdale123]

I've been having the issue in Web Scraping mode. And for what its worth, I did realize I was one character over the sixteen character "requirement". Removing the extra character resolved the issue on my side.

EDIT: And BTW, web scraping mode rocks. You can turn almost any news based site into a feed, especially with a drill chain setup if necessary.

[TBosak]

Ah, so I probably just need to specify in docs that it's not "at least 16", but exactly 16, 24, or 32. I'll be sure to update those later.

[bigdale123]

That would definitely make the requirement more clear. If you wanted, you could probably add a little in between that chops off any excess data to satisfy the 16,24,32 requirements. That way it can be "at least 16".