ASDOCX and ASLIC

[Terry Harm]

How safe is the ASDOCX code, and the ASLIC Code. Are there any privacy concerns? Is the ASLIC Code only used for license tracking or can someone get into my computer if they have the information?

[Nick Cox]

These are programs by Attaullah Shah on his website. I have not used either.

People need to make their own decisions about safety of any Stata program based on looking at the code.

Attaullah's programs often make use of compiled Mata code, which is hard for mortals to read.

That said, if anyone had bad experiences with these commands, then I'd expect to have seen angry posts here and I have not noticed them.

If in doubt don't use a command, and that includes any of mine you don't trust.

[Attaullah Shah]

Dear Terry Harm
For asdocx, I prioritize not only the functionality and quality of the software but also the security and privacy of its users. I understand that trust is fundamental, especially when it comes to licensing systems, and I've gone to great lengths to ensure that our process is transparent, safe, and devoid of any malicious intent. Our licensing mechanism, ASLIC, comprises only three essential files: aslic.ado, asdocx_update.ado, and lasm.mlib. These files are straightforward, serve specific roles in licensing and updating asdocx, and they're open for the user to inspect except the lasm.mlib. If you require, I shall send its source code to see (but keep in mind this will reveal the basic process of how we create licenses and hence throw open our whole model. But I am ready do it to remove any doubts that you might have). There's no hidden agenda—everything operates in the plain sight of the user.

As a testament to our commitment to fair practices, I have made my profile public, including my university affiliation. My academic and professional reputation stands behind asdocx, ensuring that the software is held to the highest ethical standards. Moreover, ASLIC's operational transparency is evident—once the license is verified, users can remove the aslic components, retaining only the asdocx_update.ado for future updates of asdocx.

Addressing concerns regarding security, I agree with the esteemed Nick Cox: if there were any vulnerabilities or issues, the community would certainly raise them. The absence of such discourse underscores our system's reliability. Furthermore, the brief blue screen observed daily is a necessary step for license validation via a system's MAC address—a function Stata lacks natively, thus necessitating a shell command. This process is a one-time daily occurrence to minimize disruption and maximize user experience. We ensure that it's a quick, unobtrusive check, respecting your time and interaction with our product.

asdocx is designed with your security and convenience in mind, upheld by a transparent licensing system and backed by a reputation built on integrity and fairness. Your trust is our priority.