• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Image Definition Path Slashes Removed

    Scheduled Pinned Locked Moved
    FOG Problems
    2
    4
    800
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      jkonney
      last edited by

      Hi-

      I have subfolders on our server that contain images and can no longer specify them in our image definitions because the slashes are removed from the path when typed in now that we have upgraded to 1.3.0-RC-1 SVN Revision: 5936

      Is this a bug or has this functionality been removed?

      Thanks

      1 Reply Last reply Reply Quote 0
      • Tom ElliottT
        Tom Elliott
        last edited by

        I don’t understand.

        The path should always be in the root of the images folder. To my knowledge, the slashes were removed since 0.32 even released.

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

        1 Reply Last reply Reply Quote 0
        • J
          jkonney
          last edited by

          We were on v1.2 and upgraded and now are experiencing this issue so I’m not sure how it was working.

          For example,

          Image Path /images/2015/DESKTOP

          If we try to enter any slashes after /images/ in the “Image Path” field, the slashes are automatically removed.

          So 2015/DESKTOP becomes 2015DESKTOP which is an invalid path.

          If I understand correctly, the slashes I’m trying to add shouldn’t be possible after v0.32 ? Thanks

          Tom ElliottT 1 Reply Last reply Reply Quote 0
          • Tom ElliottT
            Tom Elliott @jkonney
            last edited by

            @jkonney Correct, they shouldn’t be possible, though I suppose it’s not the end of the world. The issue it poses, though, is it could give you access to lower level directories. For example, if you had put in the path as “…/…/…/…/usr/bin/init” you could lose your ability to load your OS any further. Of course it’s only with FOG permissions I suppose, but capturing could be a bad time.

            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

            Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

            Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

            1 Reply Last reply Reply Quote 1
            • 1 / 1
            • First post
              Last post

            165

            Online

            12.0k

            Users

            17.3k

            Topics

            155.2k

            Posts
            Copyright © 2012-2024 FOG Project