FYI, I'm not reposting these messages (below) for purposes of
vindication, but instead because I was gravely worried about the
potential of issues with the licensing mechanism and I felt that it was
no less prudent to point these out before these issues occurred than I
am now that they have. Both Declude and their customer base is well
served by people talking about things that concern them, and having
these things not only listened to, but also understood.Re: [Declude.JunkMail] Declude Phone's Home Re: [Declude.Virus] Upgrade issues There have been repeated assurances in the past and even currently that all the bases were covered, but they aren't. I think that we deserve to know now what changes are going to be made that guarantee that these bases are covered in the future. For instance, Declude needs to be able to function 100% independently of any dependence on a third-party to enable it. This means that even if there is a 30 day grace period, following that period the software must function without needing to phone home successfully because no authentication system is guaranteed to survive years that may pass, a takeover, or a failure of the company operating it. This also needs to be more readily accessible than a backdoor to unlock the software since that information may not survive these circumstances. This can be done in a way that doesn't cause a breakdown in licensing enforcement. It's not time to complain, it's time to fix the issues and give us the confidence that things have been thoroughly resolved. I can't imagine that any administrator around here would disagree in light of the past weekend's failure. Thanks, Matt |