While running Yum Update
I receive error "Package wbm-virtual-server-3.52.gpl-2.noarch.rpm is not signed"
I recently installed virtualmin after the webmin update. On the “System Information” home page a new update popped up. which it says is unsigned and won’t install.
You can edit the /etc/yum.repos.d/virtualmin.repo file. Change gpgcheck=1 to =0 under the virtualmin-univer section.
this will let the rpm install. Be sure to change it back when finished
isn’t that a security risk??
I have this same problem.
question:
isn’t that a security risk??
I just changed what jwdick proposed and changed it right back… everything seems to be fine. But files are meant to verified for a reason 
Ok,
It works after change.
I need to ask this question becous i dont know it is realy your update 
After i change it back and look good
regards
Houston, we have a problem after update.
It show an information " Recheck is needed".
Checking Configuration
The status of your system is being checked to ensure that all enabled features are available, that the mail server is properly configured, and that quotas are active …
Virtualmin is configured to setup DNS zones, but this system is not setup to use itself as a DNS server. Either add 127.0.0.1 to the list of DNS servers, or turn off the BIND feature on the module config page.
… your system is not ready for use by Virtualmin.
Ofcours bind is working properly 
Quote:
Virtualmin is configured to setup DNS zones, but this system is not setup to use itself as a DNS server. Either add 127.0.0.1 to the list of DNS servers, or turn off the BIND feature on the module config page.
… your system is not ready for use by Virtualmin.
Unquote
To correct the "bind" issue, log into Webmin, go to "networking" "Network Configuration" "Hostname and DNS Client". Add "127.0.0.1" to the DNS servers listed then click <SAVE>. Now recheck your module configuration with VirtualMin and all is well.
Thank you
BIND DNS server is installed, and the system is configured to use it.
regards
I agree. Packages should be signed. But there are several reasons why a package would not be signed, just a mistake on the creator’s part being one of them. That is why I always download and install packages (even those signed) to a “test” box to verify first. You should NEVER apply any update to a production server, not even an update to the OS without testing it first on a test server with a similar configuration. Having done this, I found the update to be fine even with the signing problem and decided to install it.
Jamie forgot to sign this release (the GPL packages are built in a different process than the Professional packages, and I guess aren’t automatically signed…I build the Pro packages, Jamie builds the GPL). I’ll ask him to re-roll and sign. Maybe I’ll also take over package builds for the GPL yum repos, since signatures are more important there than standalone RPMs.
Should be fixed in a day or so, regardless.