zuda

Airtight security 2.0 is out!! We now have a premium option. We also fixed the issues you are having. Thank you for being part of the airtight community.

This is an issue with a specific configuration environment. Since there are only 2 reports of a problem, it’s extremely localized.

When working on a product that isn’t working on just one environment, rather working in every single possible configuration under different hosts configurations, the “maybe more testing is required” theory flies out the window. We can test for a decade, someone will still have a weird config that makes it malfunction. As we can all tell, this malfunction is localized to a certain configuration or there would be wider cry for help. Two people having issues, while not optimal shows it has something to do with their configuration.

Hey Tom,
They should still be in the database, however I have no familiarity with this issue as it was tested on a live site before releasing this version. 2.0 is an absolute complete rewrite from another programmer that did some coding for the project. It has been tested rigourosly. I have no clue why some installs are acting this bad with 1.8.1. I wish I had some log files that could explain it.

This is extremely odd, as we tested this on a live site before releasing using Linux and the latest version of WordPress. Could you email [email protected] the 1.6.2 code? THe code we have been working very hard on and has been tested rigourosly 2.0 is finally done and ready to be released. 2.0 is a complete rewrite of the entire software, by a programmer other than myself. It took a lot of time and work to get it just right.

• This reply was modified 6 years, 3 months ago by zuda.

The current version is 1.8.1, where redirection issues were fixed. Is everything fixed since the caching issue has been solved?

Okay, an emergency patch was sent out after testing. You can now save again. Our deepest apologies about that error. Lots of work and time is being put into version 2.

Thomas,
Thank you so much for your feedback. We have been working on a complete codebase rewrite, which is far more complex than it sounds. This process has taken over $500 USD and 2 months. We are on the final version, just fixing a glitch we don’t want people to run into. Since this is a free program, I certainly hope you can see how serious we are taking making everything work smoothly to spend over $500 on such a free program.

We want to ensure the highest quality experience possible. We also have a private invite only bug bounty to ensure the safety of our free software. The new version should be out very soon. I hope this helps that you know how hard we are working on this.

This is being resolved as this feature only addresses 403, not 404. If there was an error in spelling, please open a new ticket.

Hey, I am sorry to hear about the problem. Is this happening only for logged in users or also for logged out users?

We believe we have solved this issue. Let us know if it isn’t solved in the latest version.

It is explained to the best of our knowledge on our site, however every expert WP coder and programmer can not explain nor understand how this could’ve happened, however based on the data we have this is the current conclusion. Thanks centicon.
https://planetzuda.com/incident-response-to-software-issues-how-to-plan-for-incident-response/2018/07/19/

There have been no problems with the latest release.

We were absolutely shocked as root under no circumstances should have been affected. We will be adding more coders into this free open source project to ensure stability, functionality, and new features go smoothly. We only know of a dozen sites that were affected out of over 3000 that use our software, but that is still too many for our liking.

How root was affected is a mystery no one has been able to solve yet. Again, we apologize for this error, but have no idea how it affected you. We will be examining your sites to see if there was a configuration difference we hadn’t planned for, or something that could’ve caused this. We still wish we could see this happen live, as we’ve yet to see it malfunction. We learn a lot that way.

• This reply was modified 6 years, 8 months ago by zuda.
• This reply was modified 6 years, 8 months ago by zuda.

We are so sorry that our new feature that was tested on live sites on different hosts, malfunctioned for you. We would love to find out what was the cause of the malfunction, but in the meantime, have sent out a patch removing the index.html.

On all the sites we tested this blocked directory traversal, we look forward to learning how this went wrong and would be happy to give all of you ten minutes free of our time doing security for you.

Again, we are so sorry about this issue and look forward to identifying where it went wrong.