Re: Pirated WebCat? NOT...
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 49772
interpreted = N
texte = Hi Everyone,I would like to know if this SmithMicro serial number check also applies to WebCatalog 4.5.x because that's the license I currently use and I'm very concerned about the liability this suggests I should cover for.If my insurance company learns that the software engine I use to manipulate the data in SuperJobs.net can connect back to SmithMicro at any moment to transfer any data (including the serial number) which I'm not fully aware of, this could mean big trouble for me.You see, when SuperJobs.net users come on my site to post data, some public and some for internal use, they assume they have a relationship with my company. Not with my company AND another one called SmithMicro (which they never heard about).I mean, take the problem and turn it around. Would you post your resume on HotJobs.com if you knew the people who built and sold them the data engine behind the site could communicate through some back door? Would you continue posting detailed personal data with them knowing they don't have control over what's going on in their data center?This incident shows how SmithMicro has to review the way it intends to protect the software it sells. My liability will be jumping through the roof if I can't insure that 100% of what's going on in my server is handled, controlled and intended in-house. Having SmithMicro keep the ability to access my private server farm at will is a clear invasion of my privacy and of my property. I don't see how any of you can live with this kind of liability...In case someone has an idea what I could say to the insurance company which also protects me from legal actions, please speak out. My first reflex if I'm sued by a customer who learns my system leaks information would be to sue SmithMicro for accessing my server without my prior consent through a clear signed form with an expiry date each month since that kind of privilege they allow themselves is very significant and if I ever sell my company (or part of it) to new investors, this is exactly what their experts will be freaking out about.The issue is simple: when we buy your software, it's ours and you have no business whatsoever coming back sniffing around our premises, online or otherwise. If you do and specially if we're not fully aware and ok with it, it may be a criminal act (but I'm not a lawyer so go figure, I may be wrong).Please SmithMicro, address this very hot issue.Kind regards, On Friday, April 25, 2003, at 09:06 AM, Kenneth Grome wrote:>> First of all, if you don't have anything to hide, meaning to pirate >> your >> number, there is no need to worry. > > I have credit card numbers to hide because I run an online store. > Anyone else have something similar to hide from people who are not > supposed to have access to it? How do we know credit card numbers are > not being sent back to SMSI, or even to one of its potential software > hackers? > > > >> It is hard for me to believe that SMSI point of doing this is to snap >> your >> data under your nose or anything illegal. We are NOT talking about a >> little >> company with some freaks. > > What evidence do you have that they are not some freaks? Have you > met or do you know any of the programmers personally? Even if you > know then, how can you possibly assure us that they are *ALL* happy at > SMSI, and that none of them have axes to grind with SMSI's management? > > > >> btw: Did you guys ever think about that with every app you work the >> developer knows how to crack any of your data, since they are the >> ones who >> developed it in the first place! > > This doesn't matter when the developers do not also create features > that give them unauthorized access to the data on my server that > belongs to innocent online shoppers. God only knows WHAT data is > really being sent back to the company ... > > > By the way, I'm not suggesting that SMSI is doing (or will do) the > things I've mentioned here and previously. I am simply taking the > devil's advocate position by arguing that it is not only possible, but > for SMSI it would also very EASY. > > Clearly if the wrong person (or people) were left alone to modify the > webdna engine code, far more serious consequences could result than > just the theft of our own personal or private data -- because we store > credit card data of OTHER PEOPLE on our WebDNA-enabled servers. > -- > > Sincerely, > Kenneth Grome > ------------------------------------------------------------- > My programmers will write WebDNA code for you at $27 an hour! > ------------------------------------------------------------- > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list
. > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > > Web Archive of this list is at: http://webdna.smithmicro.com/ > >-- Claude Gelinas, Chief Technological Officer MBNX.net - Online ServicesDirect: (418) 657-6184 Toll free: 1 866 783-2321Mailto:cgelinas@mbnx.net Visit us - http://mbnx.net/ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Hi Everyone,I would like to know if this SmithMicro serial number check also applies to WebCatalog 4.5.x because that's the license I currently use and I'm very concerned about the liability this suggests I should cover for.If my insurance company learns that the software engine I use to manipulate the data in SuperJobs.net can connect back to SmithMicro at any moment to transfer any data (including the serial number) which I'm not fully aware of, this could mean big trouble for me.You see, when SuperJobs.net users come on my site to post data, some public and some for internal use, they assume they have a relationship with my company. Not with my company AND another one called SmithMicro (which they never heard about).I mean, take the problem and turn it around. Would you post your resume on HotJobs.com if you knew the people who built and sold them the data engine behind the site could communicate through some back door? Would you continue posting detailed personal data with them knowing they don't have control over what's going on in their data center?This incident shows how SmithMicro has to review the way it intends to protect the software it sells. My liability will be jumping through the roof if I can't insure that 100% of what's going on in my server is handled, controlled and intended in-house. Having SmithMicro keep the ability to access my private server farm at will is a clear invasion of my privacy and of my property. I don't see how any of you can live with this kind of liability...In case someone has an idea what I could say to the insurance company which also protects me from legal actions, please speak out. My first reflex if I'm sued by a customer who learns my system leaks information would be to sue SmithMicro for accessing my server without my prior consent through a clear signed form with an expiry date each month since that kind of privilege they allow themselves is very significant and if I ever sell my company (or part of it) to new investors, this is exactly what their experts will be freaking out about.The issue is simple: when we buy your software, it's ours and you have no business whatsoever coming back sniffing around our premises, online or otherwise. If you do and specially if we're not fully aware and ok with it, it may be a criminal act (but I'm not a lawyer so go figure, I may be wrong).Please SmithMicro, address this very hot issue.Kind regards, On Friday, April 25, 2003, at 09:06 AM, Kenneth Grome wrote:>> First of all, if you don't have anything to hide, meaning to pirate >> your >> number, there is no need to worry. > > I have credit card numbers to hide because I run an online store. > Anyone else have something similar to hide from people who are not > supposed to have access to it? How do we know credit card numbers are > not being sent back to SMSI, or even to one of its potential software > hackers? > > > >> It is hard for me to believe that SMSI point of doing this is to snap >> your >> data under your nose or anything illegal. We are NOT talking about a >> little >> company with some freaks. > > What evidence do you have that they are not some freaks? Have you > met or do you know any of the programmers personally? Even if you > know then, how can you possibly assure us that they are *ALL* happy at > SMSI, and that none of them have axes to grind with SMSI's management? > > > >> btw: Did you guys ever think about that with every app you work the >> developer knows how to crack any of your data, since they are the >> ones who >> developed it in the first place! > > This doesn't matter when the developers do not also create features > that give them unauthorized access to the data on my server that > belongs to innocent online shoppers. God only knows WHAT data is > really being sent back to the company ... > > > By the way, I'm not suggesting that SMSI is doing (or will do) the > things I've mentioned here and previously. I am simply taking the > devil's advocate position by arguing that it is not only possible, but > for SMSI it would also very EASY. > > Clearly if the wrong person (or people) were left alone to modify the > webdna engine code, far more serious consequences could result than > just the theft of our own personal or private data -- because we store > credit card data of OTHER PEOPLE on our WebDNA-enabled servers. > -- > > Sincerely, > Kenneth Grome > ------------------------------------------------------------- > My programmers will write WebDNA code for you at $27 an hour! > ------------------------------------------------------------- > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > > Web Archive of this list is at: http://webdna.smithmicro.com/ > >-- Claude Gelinas, Chief Technological Officer MBNX.net - Online ServicesDirect: (418) 657-6184 Toll free: 1 866 783-2321Mailto:cgelinas@mbnx.net Visit us - http://mbnx.net/ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Claude Gelinas
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Summing fields (1997)
2.0 Beta (1997)
formvariable funkyness (2000)
RE: protect tag on NT (1997)
[WebDNA] "Safe Write for Database" setting.... (2016)
Sort Issue? (2000)
Using Cookie for client specific info? (1997)
[shippingtotal] & Formulas.db prob (2003)
Error Log.db --however (1997)
Upload Progress Bar (2003)
Upgrading from 2.1 to 3.0.7 (2000)
Enterprise Server (1998)
Inventory lookup & display... (2003)
Remote administration (1998)
Db design question (relational vs. flat?) (1998)
bug in [SendMail] (1997)
[WebDNA] Wishlist: ignore whitespace in database changes (2016)
Bug or syntax error on my part? (1997)
Unexpected error (1997)
Archive (Zip, Sit, Tgz) (2004)