Posts made by astrugatch

@george1421

haha. No. Too early & haven’t finished coffee. I just replaced the password in configuration with the one from .fogsettings. That fixed my kernel download issue. I was able to deploy an image yesterday with the mismatched passwords but I haven’t tried to capture one.

@george1421

That did it.

Is there anywhere else that password is used that I should check?

When trying to update kernel on 1.5.7.104 I get the following error:

Type: 2, File: /var/www/fog/lib/fog/fogftp.class.php, Line: 464, Message: ftp_login(): Login incorrect., Host: 10.10.70.4, Username: fogproject

@Sebastian-Roth

Link sent in PM

@Fernando-Gietz

It was a fresh install but I migrated my DB from my old install before enabling ldap which originated at 1.5.0 RCX upgrading up to current.

@Fernando-Gietz

Version: 1.5.5_1

@Sebastian-Roth

I just checked and unfortunately I don’t have a snapshot post install. I had rolled back to have a working version for when I did the migration to the clean install on 18.04. If i can capture the machine and put it in a sandbox at some point I can start it back up and run the installer again. That might be a while though.

@Sebastian-Roth

I still have that VM in my backups so I can take a look. Hopefully I didn’t revert it before I migrated. Do you have a particular log you would want to see? I can pull any file out of the backups.

@Sebastian-Roth

I’ve only ever used 636 and running into this is the first time i’ve ever seen 686. It more sparked my interest considering its different on the pane to create the LDAP connection than it is to edit the ldap making me think it was a typo on one or the other.

@george1421

To have:

SSLProtocol             all -SSLv3 -TLSv1 -TLSv1.1
SSLCipherSuite          ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384

added to the virtual host automatically when the ./installfog.sh -S is run just like

    SSLEngine on
    SSLCertificateFile      /path/to/signed_cert_and_intermediate_certs
    SSLCertificateKeyFile   /path/to/private_key

is automatically added. I guess this is less a bug than a feature request geared toward security

I opened this up in github, but was posting it here to have a wider discussion for those that don’t visit github.

The apache config currently accepts tls 1.0 and 1.1 which should be disabled to meet current standards. tls 1.2 should be the only accepted protocol.

FOG Version: Dev Branch 1.5.7.104

I don’t know who developed the LDAP plugin so I will just post this here. When you go to set up a new LDAP connection the dropdown for the port number has 389 and 686. This should be 636. It is correct on the page where you edit existing connections. This means you need to create it with 389 and then update that to 636 after creation

@Sebastian-Roth

deb-branch works when i migrated to a clean 18.04 install. I have a feeling my upgrade from 16.04 to 18.04 left something behind that I’m not finding.

@Wayne-Workman

I know this thread is old but I am following the guide now and have a question.

I am in the process of building a new host. On my old host I have SSL setup (./installfog.sh -S). Do I set up the new machine with SSL and replace the certs with the one from the old machine? following the se instructions: https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#Maintain_Control_Of_Hosts_When_Building_New_Server

Thanks

Nevermind I got it all sorted. Just wanted to make a note that the wiki needs to be update to reflect that the user that needs to be added and given permissions is now fogproject rather than fog

@Sebastian-Roth

I am looking at the migration instructions in the wiki and see a mention of SSL at the top by don’t see it mentioned in the instructions (except for migrating from 1.3)

@Sebastian-Roth

Tried dev-branch but still no dice. I think the issue is related to my current system. I’m going to spin up a new instance and migrate to that with a clean install of 18.04 and 1.5.7 and see how it behaves after that.

@Sebastian-Roth
No worries. I’m not in a rush to have a newer version and our windows footprint is fairly small so even if our fog install crashes and burns its not the end of the world.

Here you go.

fogadmin@fogimaging:~$ apt-cache policy | grep http | awk '{print $2 $3}' | sort -u
http://security.ubuntu.com/ubuntubionic-security/main
http://security.ubuntu.com/ubuntubionic-security/multiverse
http://security.ubuntu.com/ubuntubionic-security/restricted
http://security.ubuntu.com/ubuntubionic-security/universe
http://us.archive.ubuntu.com/ubuntubionic-backports/main
http://us.archive.ubuntu.com/ubuntubionic-backports/universe
http://us.archive.ubuntu.com/ubuntubionic/main
http://us.archive.ubuntu.com/ubuntubionic/multiverse
http://us.archive.ubuntu.com/ubuntubionic/restricted
http://us.archive.ubuntu.com/ubuntubionic/universe
http://us.archive.ubuntu.com/ubuntubionic-updates/main
http://us.archive.ubuntu.com/ubuntubionic-updates/multiverse
http://us.archive.ubuntu.com/ubuntubionic-updates/restricted
http://us.archive.ubuntu.com/ubuntubionic-updates/universe

@Sebastian-Roth

fogadmin@fogimaging:~$ sudo dpkg -l | grep -e mariadb -e mysql -e curl
[sudo] password for fogadmin:
ii  libcurl3:amd64                        7.58.0-2ubuntu2                                          amd64        easy-to-use client-side URL transfer library (OpenSSL flavour)
ii  libcurl3-gnutls:amd64                 7.58.0-2ubuntu3.8                                        amd64        easy-to-use client-side URL transfer library (GnuTLS flavour)
ii  mysql-client                          5.7.29-0ubuntu0.18.04.1                                  all          MySQL database client (metapackage depending on the latest version)
ii  mysql-client-5.7                      5.7.29-0ubuntu0.18.04.1                                  amd64        MySQL database client binaries
ii  mysql-client-core-5.7                 5.7.29-0ubuntu0.18.04.1                                  amd64        MySQL database core client binaries
ii  mysql-common                          5.8+1.0.4                                                all          MySQL database common files, e.g. /etc/mysql/my.cnf
ii  mysql-server                          5.7.29-0ubuntu0.18.04.1                                  all          MySQL database server (metapackage depending on the latest version)
ii  mysql-server-5.7                      5.7.29-0ubuntu0.18.04.1                                  amd64        MySQL database server binaries and system database setup
ii  mysql-server-core-5.7                 5.7.29-0ubuntu0.18.04.1                                  amd64        MySQL database server binaries
ii  php7.1-curl                           7.1.30-1+ubuntu16.04.1+deb.sury.org+1                    amd64        CURL module for PHP
ii  php7.1-mysql                          7.1.30-1+ubuntu16.04.1+deb.sury.org+1                    amd64        MySQL module for PHP
ii  python-pycurl                         7.43.0.1-0.2                                             amd64        Python bindings to libcurl
ii  python3-pycurl                        7.43.0.1-0.2                                             amd64        Python bindings to libcurl (Python 3)
fogadmin@fogimaging:~$ sudo dpkg -l apache2 | grep '^ii'
ii  apache2        2.4.39-1+ubuntu16.04.1+deb.sury.org+1 amd64        Apache HTTP Server
fogadmin@fogimaging:~$ sudo dpkg --configure -a
fogadmin@fogimaging:~$ sudo apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
fogadmin@fogimaging:~$

@Sebastian-Roth

I’ll check this tomorrow. There may be idiosyncrasies with my system. I’ve been upgrading in place from 1.5.0RC2 and 16.04 to the present.

@Sebastian-Roth

No worries. Let me know if you need someone to test. I can clone / snapshot my setup pretty quickly.