440 reputation
516
bio website kopli.pri.ee/kalle_varavas
location Tallinn, Estonia
age
visits member for 3 years, 5 months
seen Nov 9 at 12:41

I work for a small investment and loan company. I take care of the main software (built by yours truly), that deals with the accounting. I also do lots of freelancing work related to web-based software.

I have successfully built my own custom CMS, that I started in 2009 and released the first time in 2010. Hoping to publish it for commercial usage.

Been developing websites for 11 years now. Mostly with PHP and JavaScript.

I got two Benz's and I love to drink coffee.


Jul
4
comment How to verify that all files are intact prior to install?
Thank you for the answer. I knew the hashing was the method, but couln't find the correct function.
Jul
4
comment How to verify that all files are intact prior to install?
The first part of your answer has a good point. Since I mostly use my CMS at the moment for my own clients, then I didn't think of the existing directory content. I also have a security system for cracking. Of course in PHP you cant have 100% secure software, but it mostly detects counterfake copies. The sha_file() was the lead I needed, thanks!
Sep
21
comment Should I include a selfdestruct-method to my applications?
Well, Im not judging you.. As people used to think the world is flat. Currently, your opinion vs. my lawyers. Enough said.
Sep
21
comment Should I include a selfdestruct-method to my applications?
If the kill-switch is part of your windows system. And I would: run kill-switch on 1.111.1.4 and boom, your PC is down. Then yes, legal. As it is part of the system and also the purpose of the script is exactly that. However, that is a poor example, as you cannot compare Operating systems with content-management systems, in this case. But to really put you in the place, the kill-switch is as legal as stealing the software from me. I would love to hear his pitch to jury. What client wants and how the system is designed -- not the same thing!
Sep
21
comment Should I include a selfdestruct-method to my applications?
So you are saying that kill-switch aka. unlink() loop is illegal? You couldn't be more incorrect. Kill-switch is as legal as changing your avatar on SE.
Sep
21
comment Should I include a selfdestruct-method to my applications?
If there is no contract, then there is no terms of what is part of the software. If the kill-switch is part of the software, then yes.. from programmers point of view: is it ethical? However, it is legal. Because the kill-switches purpose as part of the script, is to be activated remotely with the sole purpose of deleting EVERYTHING. Its legal, so why is it bad idea?
Sep
21
comment Should I include a selfdestruct-method to my applications?
I disagree. It is actually a very good idea. If you would read the details carefully, then you would understand that i'm talking about non-contract jobs.. where in my examples case, the client is questionable. His reputation as a known thug vs. my attempt to protect myself. I don't think this will affect my reputation negatively. Your scenario sounds like contracted work.. in that case I have a contract, no need for the kill-switch. However, if there is no contract then they cannot get the copy of the code either..
Sep
21
comment Should I include a selfdestruct-method to my applications?
True, however this depends on the client, software, server. In my case, the client barely could change the ftp access. But checking the logs is impossible. Also, that server doesn't support any such logging..neither does my humble CMS..
Sep
21
comment Should I include a selfdestruct-method to my applications?
Im starting to actually love the trial-software idea. However, the second part is iffy. Basically, if the trial-licensing or even kill-switch would be a part of the software, then its perfectly legal. Depending on contracted or non-contracted work, it should be stated in the contract.
Sep
21
comment Should I include a selfdestruct-method to my applications?
I love your answer, it addresses my point alot better then other answers. I checked with my lawyer and he said, that afterwards going inside the admin panel and uploading a unlinking script via filemanager, is consider hacking -- illegal. However, if there is a actual function built-in the software.. then its part of the software and has its own purpose. This obviously should be covered in the contract, though this question is about non-contract works. Thank you for your answer :)
Sep
21
comment Should I include a selfdestruct-method to my applications?
@Dave. I do get your point, but if you think about it. If there is no contract, so the terms and what not are not set. Then, the program is hole as it is. So, if the kill-switch was inside the code when the software got moved/stolen/delivered.. then using that kill-switch (basically unlik() function), is part of the softwares purpose.. I have talked with my lawyer, and he did point out, that hacking the software would be illegal (using filemanager to upload unlinking-script for example.) But if the kill-switch is included inside the code, as part of software, then its perfectly legal.
Sep
20
comment Should I include a selfdestruct-method to my applications?
@thedaian, you are correct. Its because of the local understanding of freelance work. The term over here is mostly used for non-contracted work.
Sep
20
comment Should I include a selfdestruct-method to my applications?
@thedaian valid point, however I didn't ask "do I always have to have a contract?"
Sep
20
comment Should I include a selfdestruct-method to my applications?
Indeed, first answer that doesn't argue about "why you iz not contract" or "using unlink() is ILLEGAL". I actually really like your idea, I can cook something up in CRON.
Sep
20
comment Should I include a selfdestruct-method to my applications?
Stick it to an awful client in the future? That sounds something what I didn't ask about or even mention. And if I don't get paid, yet he will lose the software, then how is your 1st point valid? Also there were two points in my question, is it ethical/legal to have the kill-switch inside my own server and/or in the clients server. You didn't mention which one you meant. Fairly certain, that I can have kill-switches in my own server.. So when somebody copies it, I can remotely delete it. And I think good clients are irrelevant, as the kill-switch is not included in the software. Its 1 line.
Sep
20
comment Should I include a selfdestruct-method to my applications?
-1 Sorry, but your answer is off-topic. Good advice, little bit offensive but still. I don't recommend to make judgments as you don't know the full story nor do you know, how I usually make business.
Sep
20
comment Should I include a selfdestruct-method to my applications?
@Aaronaught, negative. As this is without contract version, though very similar.
Sep
19
comment Should I include a selfdestruct-method to my applications?
@Mason, I'm having dejavu while reading it. Its pretty much like that, however the client is a criminal and my code rocks.
Sep
19
comment Should I include a selfdestruct-method to my applications?
Agreed, I got my lesson. Well, in theory it is correct, but it was one of those rare combinations of different variables. Friend of a friend, who wanted it cheap (1000€), my personal CMS with custom made design. I think its more clear, how the programmers community feels about this. Thank you for your answer, it still was focused more on the contracted-cases, but left the imagination for the non-contracted jobs.
Sep
19
comment Should I include a selfdestruct-method to my applications?
@Steven Basically, all answers have gone over this. But I'm talking about freelance work, no contract. If I would have a contract, then this is obviously an unethical and stupid idea. So, this is the case where you are developing a software for some questionable-character, without contract and he just basically copies the files from your server and that's it. Personally, I feel that I want to have the option to kill it. Would you?