SOLVED Anyone else's Module Admin confused this morning?

[tbrummell]

Received the update saying my modules had a security vulnerability, so I updated. Error was still in Dashboard, so I went to look....


Something seems a bit confusing...

 

[krzykat]

This is a subject that is being discussed over on FreePBX forums.

 

[tbrummell]

Not the exact same, but OK, will follow for now.

 

[hawk#1]

No issues at all on my system

 

[KNERD]

You may want try to do the update from the command line.

 

[kenn10]

Yes. I did the following instead of using the web interface in FreePBX:

Log into your system and at the Linux command prompt do this:

fwconsole ma upgradeall
fwconsole reload

It may not be necessary, but just for housekeeping, I also did:

fwconsole restart

 

[kenn10]

If you still have issues with the dashboard saying that your modules are unsigned, you can do this:

Log into your system and at the Linux command line:

/root/sig-fix
/root/sig-fix
fwconsole restart

 

[hawk#1]

I just follow the instuctions in Ward's nerdvittles articles

Keeping FreePBX 15 Modules Current​

We strongly recommend that you periodically update all of your FreePBX modules to eliminate bugs and to reduce security vulnerabilities. From the Linux CLI, log into your server as root and issue the following commands:

fwconsole ma upgradeall
rm -f -r /tmp/*
fwconsole reload
/root/sig-fix
/root/sig-fix

it works and I have not had any issues with tampered files warnings or unsigned modules. Copy, paste, enter, and done.

 

[mainenotarynet]

Did Module Admin and UCP stuck at 15.0.6.14 - so read all this thread and did command line next fwconsole ma upgradeall -- this came back all up to date. Well it's not -- still stuck at 15.0.6.14 -- so did specific fwconsole ma upgrade ucp -- says it's up to date -- still nope. Oh well -- I'll be vulnerable until my system gets a clue.

 

[kenn10]

@mainenotarynet, in your Settings > Advanced Settings, check the branding field and make sure it is not set to a specific version of FreePBX. Mine systems were not updating until I changed the setting. To get all updates, it generally requires that you set it like this:

 

[krzykat]

@mainenotarynet, in your Settings > Advanced Settings, check the branding field and make sure it is not set to a specific version of FreePBX. Mine systems were not updating until I changed the setting. To get all updates, it generally requires that you set it like this:
View attachment 3611

Yep - excellent advice

 

[hawk#1]

I never had to touch this setting and it seems to work fine for me.

Branding​

Lock Version

15.19.11.001

KEYWORD:MIRROR_BRAND_VERSION
Version to set this brand to


Wonder why it works correctly on default system installs, and others have to go into settings and make changes to the settings. Maybe some changed the setting from default and forgot they changed it?

 

[kenn10]

I never had to touch this setting and it seems to work fine for me.

Branding​

Lock Version

15.19.11.001

KEYWORD:MIRROR_BRAND_VERSION
Version to set this brand to


Wonder why it works correctly on default system installs, and others have to go into settings and make changes to the settings. Maybe some changed the setting from default and forgot they changed it?

At one point when there was a scare about some FreePBX modules possibly being compromised, Ward had advised us to lock it to a specific version so that the suspect modules would not download. I suspect that if you ever put something in there, unless you change it, it stays locked on that one version. Perhaps on a clean install where no one messes with the lock, FreePBX will default to most current.

It took me forever to figure out what was wrong when I wasn't getting updates to my modules.

 

[hawk#1]

At one point when there was a scare about some FreePBX modules possibly being compromised, Ward had advised us to lock it to a specific version so that the suspect modules would not download. I suspect that if you ever put something in there, unless you change it, it stays locked on that one version. Perhaps on a clean install where no one messes with the lock, FreePBX will default to most current.

It took me forever to figure out what was wrong when I wasn't getting updates to my modules.

Thanks for clarification. I guess that is why the default on mine was set for ver 15.19 (probably won't get there since 16 already in beta). I guess I should set mine to latest also. Hopefully that will prevent a problem when I upgrade to ver 16

 

[Halea]

@mainenotarynet, in your Settings > Advanced Settings, check the branding field and make sure it is not set to a specific version of FreePBX. Mine systems were not updating until I changed the setting. To get all updates, it generally requires that you set it like this:
View attachment 3611

@kenn10 : How on earth did you figure this one out? I'm speechless!
My Debian install had a version number in it and I removed it long ago, but without entering "latest" in that field it doesn't seem to make any difference.

 

[kenn10]

@kenn10 : How on earth did you figure this one out? I'm speechless!
My Debian install had a version number in it and I removed it long ago, but without entering "latest" in that field it doesn't seem to make any difference.

I could not find the forum post where Ward had recommended we lock the version number but I did find an arcane reference in the FreePBX forums. I tried "latest" and it worked!

 

[mainenotarynet]

@kenn10 -- Thanks, that was my issue. I never touch Advance settings so how it was set to 15.19.11.001 I don't know.

Maybe I saw the post from Ward and just forgot, but the UCP is now correct at 15.0.10 as it should be.

 

[ostridge]

/root/sig-fix
/root/sig-fix

Is the /root/sig-fix (bis) needed?

 

[kenn10]

Is the /root/sig-fix (bis) needed?

Only if the dashboard is complaining about non-signed modules.

 

[wardmundy]

@kenn10 -- Thanks, that was my issue. I never touch Advance settings so how it was set to 15.19.11.001 I don't know.

Maybe I saw the post from Ward and just forgot, but the UCP is now correct at 15.0.10 as it should be.

The Incredible PBX branding module from ClearlyIP lets us manage versions of every FreePBX module. UCP was erroneously set to a specific version rather than the latest release. We have fixed it. Ordinarily, you are much safer leaving the Branding option in Advanced Settings set to 15.19.11.001 which lets us protect your platform from a dangerous module if one should appear down the road. The downside is what happened here where I forgot to unblock a locked version of UCP because the next version caused folks problems that were later fixed in a subsequent release. My apologies.