Disabling LPKG Index Validation

Just a quick blog today...

When you start up LR 7 CE/LR DXP, you'll often see it stop while trying to validate LPKGs. This is a security measure which is used to verify that the LPKG files have not been tampered with.

In development, though, this delay is just painful.

Fortunately it can be disabled. Add the following line to portal-ext.properties:

module.framework.properties.lpkg.index.validator.enabled=false

That's all there is to it.

Note that I probably would not do this in my production environments. It is, after all, in there to protect your environment. Disabling it in production removes that small bit of protection and doesn't seem wise.

Blogues
Hi,
where is this property declared and which version? I couldn't find it in portal.properties and it's not working in 7.0.2
You won't find it listed in portal.properties at all.

It wasn't supported in initial versions of 7.0; I know it went in about 6 months ago in DXP, so it may only now be available in 7.0 GA4.

And if you're not at GA4 yet, I'd recommend upgrading when you can. Lots of bug fixes, etc over the earlier GAs...
Are lpkg's extra vulnerable to tampering in different ways than the jars or anything else in the app server?
They are not more vulnerable, but I think it is really a shared facility with lpkg downloads from the marketplace where having the system verify the lpkg with the known value to ensure the download hasn't been modified prior to or during download.

Note that this is a guess on my part, I'm not really privy to why it was put in, the role it was meant to have and how widely it is to be used. These are more like educated guesses on my part.
Might be an idea to have this property added to the portal-developer.properties so that people who are in development mode get access to this setting automagically.