Meiga 0.4.0 “end of the year” release

I didn’t want to finish the year without devoting some time to Meiga, so I took advantage of Christmas holidays and prepared a new release with some long awaited features that make it a more serious tool:

  • Dynamic port change
  • SSL support
  • Persistent settings storage
  • Password protection

Latest information, including the source code, install instructions and previous versions can be found in the project website:

Happy new year!

4 thoughts on “Meiga 0.4.0 “end of the year” release”

  1. Wow! What a great app!
    Are there any security implications/problems in using it?

    How can I activate the SSH server(s)?



    1. There aren’t known security implications but, as with any other network related application, there can always be bugs. No application is 100% safe forever. What I can tell you is that the server password (if set) is stored using MD5, never in clear text. Credentials to connect to remote SSH servers are never stored (you must supply them each time you start the application).

      To activate HTTPS, just go to the “options” tab and check “Encrypt transmission”, then “Apply” (see the screenshot at the Meiga website).

      If what you want is to forward the serving port so that it’s like if it’s being served from a remote machine, then fill in the “SSH options” (host, port, user, password) and then select “SSH” as “Port redirection scheme”. A helper application will connect to the specified SSH server and forward the ports accordingly. Remote users can then connect to the remotely forwarded port. When you don’t need to serve files anymore, select again “Port redirection scheme: None” and the forwarding will stop. Exiting Meiga also stops forwardings automatically.

  2. how difficult would it be to implement something like webdav into meiga?

    1. It seems that libsoup already has some constants defined to deal with WebDAV’s particular protocol extensions, but the actual protocol would need to be implemented from scratch coding custom handlers and following the RFC step by step. It would be a nice addition to libsoup itself, but it’s not a trivial task and would probably be out of the Meiga project scope, at least by the moment.

      For “advanced” features such as WebDAV, Apache would probably be a better solution. If you’re specially interested about Meiga’s port forwarding features, probably it’s easier to use the redirection tools included in Meiga (fwlocalip, fwfon, fwssh, fwupnp) to setup external access to a “serious” server like Apache easily.

Comments are closed.