Security Run Output

[sharky]

Hello,

I received a couple of emails from my freenas system "security run output" . I see a lot of programms which should be updated.

I'm running the latest freenas images. So I how should I deal with the email?

Do I have to wait until freenas team release a new update ?

best regards, sharky

 

[Mirfster]

In the GUI; go to [System] - [Update]. Should see and be able to apply updates. :)

 

[sharky]

That was the first thing I checked, but there aren't any updates.

 

[DrKK]

Could we see the original email?

 

[sharky]

E-Mail attached

 

[DrKK]

Fascinating. I have never once gotten a list of out-of-date packages in a FreeNAS security-run email. You have not made any modifications to the appliance's runtime files?

Weird.

 

[Mirfster]

Hmm, I have never seen that myself...

Did you also receive an "Update Available" e-mail?

Normal "Update Available" e-mails look like this and usually not like what you show for a Security Run Output:

Code:

Subject: [Server Name Redacted]: Update Available

A new update is available for the FreeNAS-9.3-STABLE train.

Changelog:
#3217   Feature Nice to have    Support more than 16 user groups on NFS
#4884   Feature Nice to have    Listen Interface in SSH Options
#6077   Bug     Nice to have    Local replication breaking new jail creation
#6985   Feature Critical        Manual LUN assignment for iSCSI
#11099  Bug     Important       NFS gets stuck if you reboot FreeNAS while NFS Server is Running
#11242  Bug     Important       Unable to mount NFS partitions after reboot
#11701  Bug     Important       FreeNAS as Domain Controller, can't create GPO
#11833  Bug     Nice to have    LDAP Home path and shell not populating with anonymous bind
#12450  Bug     Nice to have    Pressing the "Guide" icon leads to a 404 Not Found page.
#12584  Bug     Important       Removes /etc/resolv.conf from the release, since it is not needed.
#12596  Bug     Expected        Fixes an issue with an undefined variable in some circumstances.
#12669  Bug     Important       Errata Notice: FreeBSD-EN-15:19.kqueue
                        Errata Notice: FreeBSD-EN-15:20.vm
                        Security: FreeBSD-SA-15:26.openssl
#12717  Bug     Important       Can't load iSCSI config after importing database
#12763  Bug     Important       Checks a master site for manifest file, also falls back to master site for other downloads if necessary.
#12784  Bug     Expected        replicator can send failure emails even when it succeeds
#12785  Bug     Nice to have    DS flag is not set in LBP mode page of SCSI target
#12829  Feature Nice to have    API call for updating Free/TrueNAS
#12831  Bug     Expected        Factory restore from the CLI console menu doesn't work
#12927  Bug     Critical        Cannot enable LDAP anymore
#12929  Bug     Critical        sshd crashing upon root login
#12956  Bug     Important       Active Directory Controller, Group Policy and Samba4 System Share Attributes
#13102  Bug     Important       Failed VMware snapshot email providing unusable output
#13154  Bug     Important       Don't send email if system cronjobs fail
#13164  Bug     Critical        ssh security vulnerability
#13178  Bug     Critical        Creates remote dataset during replication, and removes old replication metadata.
#13187  Bug     Important       Update the CA bundle in FreeNAS to 3.21
#12813  Bug     Critical        Cannot Create additional Vlans
#13267  Bug     Expected        system verification looks like is broken in latest FreeNAS SU.
#13273  Bug     Important       Make replication logging less verbose
#13416  Bug     Critical        replication still not working in TrueNAS internal SU.

 

[Kevin Horton]

Is this possibly the output of the weekly periodic script, if the user has done some pkg manipulations on the base system? I note that the weekly periodic script seems to check for outdated packages.