Beiträge von themmm

    I had the same Problem and i used this solution:


    You need to configure your local DNS server (router, OMV Box) so it will answer DNS requests with your local IP.


    For example:


    Your public domains is "omv.domain.com"
    The IP of your OMV Box is 192.168.0.33


    Configure your DNS Server with the IP 192.168.0.33 for the Domain omv.domain.com.


    You can do this by using your OMV machine as your local DNS server (with dnsmasq plugin).


    You need to change the following file:


    /etc/resolvconf/resolv.conf.d/base


    add the following entry (replace with your adress and IP):


    omv.domain.com 192.168.0.33


    and restart the dnsmasq service.


    Works great for me!

    You are running a backport kernel. That's what bpo in the name means. See the following for an explanation of backports:


    https://backports.debian.org/

    Is the backports kernel the default kernel in OMV 3? I can not remember that i ever changed anything kernel related.


    *edit


    Nevermind just found the Info:


    http://www.openmediavault.org/?p=2131


    "Use kernel/firmware backports by default"


    So which Kernel has to be installed to fix CVE-2017-5754? Is it Kernel Version 4.9.65-3+deb9u2~dpo+1~?


    Thank you!

    Hi!


    I've been searching the forum for informations regarding the Spectre/Meltdown vulnerability but could not find anything. So i did a little googling and found the following:


    https://security-tracker.debian.org/tracker/CVE-2017-5754


    A short


    cat /proc/version


    told me that my Box is running the following Kernel Version


    Linux version 4.9.0-0.bpo.4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 SMP Debian 4.9.65-3+deb9u1~bpo8+1 (2017-12-23)


    So i guess this is a Debian 9 Kernel on Debian 8?!


    The fix is included in Kernel Version 4.9.65-3+deb9u2 as you can see in the Link above. Are there any plans to release this Kernel/Patch in the near future?


    Thank you very much
    themmm

    If you would like to use your own certificate you should be able to edit your nginx config file. For example:


    /etc/nginx/sites-enabled/openmeduivault-webgui


    Point ssl_certificate and ssl_certificate_key to your certificate. For example:


    ssl_certificate /etc/letsencrypt/live/your-domain.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/your-domain.com/privkey.pem;


    save the file and do a


    service nignx restart


    Works for me.