Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. Enabling or Disabling SSH "support access" function does not create anything in the Event Log

Enabling or Disabling SSH "support access" function does not create anything in the Event Log

Scheduled Pinned Locked Moved Support
eventlog
2 Posts 2 Posters 502 Views 3 Watching
  • 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.
    • d19dotcaD Offline
      d19dotcaD Offline
      d19dotca
      wrote on last edited by girish
      #1

      I think I have stumbled across a bug or possibly more of a missing security workflow that should definitely exist.

      I had tried enabling and then later disabling the SSH "support access" function from the Support page in my Cloudron server. When I later went to the Event Log page, I noticed that function enable/disable was never displayed in the table on the Event Log page.

      I'm unsure if this is a bug or something that just was overlooked in the design, but I'm sure you'd agree that something as critical as enabling or disabling remote SSH access to a server containing a lot of data should most definitely be properly logged and shown on the Event Log page too.

      --
      Dustin Dauncey
      www.d19.ca

      1 Reply Last reply
      1
      • nebulonN Offline
        nebulonN Offline
        nebulon
        Staff
        wrote on last edited by
        #2

        Yes that eventlog entry was simply not created, this was fixed actually a few days ago with https://git.cloudron.io/cloudron/box/commit/93199c7f5bb491629c865b283a46ecdaef59741f

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • Bookmarks
          • Search