W dniu 2017-04-21 o 16:20, Wendell Lovewell pisze:
I work for a vendor, so I understand the necessity of making sure that licensed 
products are used properly.  But I also understand the inconvenience for both 
the customer and the vendor of managing software keys.

I’m wondering what the list’s response would be toward implementing a system 
that automatically managed the keys by allowing the software to “phone home” to 
update them.  My thoughts are that each time the software was started, and 
perhaps periodically, it would report its own key (to identify the customer), 
CPU id, MSU and/or whatever licensing metric was used.  If a verification 
response could not be obtained, either because of license expiration or 
communication errors, a grace period of “n” days would be allowed.

There would obviously be encryption, high availability, and possibly even 
customer firewall considerations.  But it seems like a fair trade to me.  
Opinions?

[my €0.02]
We all understand licenses should be paid, not stolen, IMHO that's obvious.
A little bit less obvious is the need of license enforcement, especially there are companies (IBM) which do not use enforcement. However I think, the most of us agree the need is justfied by the real life cases.

Regarding the "call home" method - I DONT LIKE IT!
Really, that's not good idea to enforce Internet connection just to perform such an action. I would agree for HMC to communicate, however I have no idea whether it's possible. Can BCPii be enhanced used for such purposse? That would be preferrable to use IBM call home site as the hub. ISV's shoudl communicate to IBM, instead of customer. Too complex IMHO.

More practical approach: the product periodically or just by demand create some token. Admin sends the token using copy-paste and e-mail or webservice. The he gets some response (again, numerical token) which should be put into the product in order to elongate licence period. I should be required once a quarter or less frequently, it should be able to be performed just today, because tomorron I start my holiday, etc.

Last, but not least: I wish I had same way of licensing enforcement for all products.

Regards
--
Radoslaw Skorupka
Lodz, Poland




======================================================================


       --
Treść tej wiadomości może zawierać informacje prawnie chronione Banku 
przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie 
jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem 
niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania 
adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie 
lub inne działanie o podobnym charakterze jest prawnie zabronione i może być 
karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie 
zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość 
włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku.

This e-mail may contain legally privileged information of the Bank and is 
intended solely for business use of the addressee. This e-mail may only be 
received by the addressee and may not be disclosed to any third parties. If you 
are not the intended addressee of this e-mail or the employee authorized to 
forward it to the addressee, be advised that any dissemination, copying, 
distribution or any other similar activity is legally prohibited and may be 
punishable. If you received this e-mail by mistake please advise the sender 
immediately by using the reply facility in your e-mail software and delete 
permanently this e-mail including any copies of it either printed or saved to 
hard drive.

mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, 
www.mBank.pl, e-mail: [email protected]ąd Rejonowy dla m. st. Warszawy XII 
Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców 
KRS 0000025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2016 r. kapitał 
zakładowy mBanku S.A. (w całości wpłacony) wynosi 168.955.696 złotych.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to