Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
I've been looking at several sites that offer a form of "linkware" license where you get the website for free but need to keep all links to the developers site in place. Purchasing a license key and adding it to the site (either in a database or some form of config file) removes these links.
I was wondering if anyone has had any experience of running a system like this, specifically how do you generate and check the license keys? I'm thinking of applying a similar model to something I'm working on so any examples in "Classic" ASP would be most appreciated.
Generally licences work using a public-key system. Your licence string is simply some info (perhaps with info on which domain name this licence is valid for, for example), signed by your private key. The web app contains the public key, which is used to check the validity of the signature.
I'm sure there are other ways, but this seems to be one of the more robust ones that I know of. :-)
I haven't coded anything in ASP, so I have no examples for you, sorry.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
My application will be using the API of the public-domain SQLite library to dynamically create databases and input data automatically into those databases.
When I google and look at their licencing it says nothing about IP rights.
Do I need to email them and find out if I need to purchase a licence to publicly use their API within my commercial project/asset?
Do I need to collaborate with the company/person who created such API and have them collaborate and have a % in-take due to it being their work?
"Public domain" means that you can do whatever you want with it.
The SQLite web site has a License link right at the top:
All of the code and documentation in SQLite has been dedicated to the public domain by the authors. […] Anyone is free to copy, modify, publish, use, compile, sell, or distribute the original SQLite code, either in source code form or as a compiled binary, for any purpose, commercial or non-commercial, and by any means.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
Apologies if this is in the wrong category. I'm currently developing and application in ASP, due to my inexperience with ASP I'm worried about vulnerabilities that a user can exploit.
My application is being coded from scratch, no templates used or defaults from Visual Studio, completely blank projects. The user is greeted with a login page where depending on there user access in active directory depends on which pages the user can access.
The exploit I'm worried about is if the user will be able to commit a directory traversal and access a page in which they're not allowed to access and change critical information.
I'm afraid my inexperience has caught up with me. Could someone explain to me how I could limit the access to the user or, If I'm over thinking the process, correct me? Constructive criticism is accepted.
Microsoft does try to help protect your application through their defaults, so if you're running in IIS, make sure the user the application pool is running under only has write access to the folders it needs to write into.
This is a very open-ended question and depends on many factors such as version of .net, server OS/IIS version, other handlers installed, etc. But a good start is to review the OWASP Top 10:
https://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project#OWASP_Top_10_for_2013
Here's a list of some automated tools you can use for testing your implementation:
https://geekflare.com/online-scan-website-security-vulnerabilities/
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 8 years ago.
Improve this question
We are developing an enrollment system through asp.net (c#), we are required to generate PDF reports and be deployed on a Web Host. We are going to use iTextSharp since it can be used for free but under Affero General Public License (AGPL). How can we deploy oursystem that is under Affero General Public License (AGPL) or more likely the free versions of iTextSharp ?
You need to distribute the complete source code of the project using iTextSharp using the same medium you use to distribute your software. For instance: in old days, software was distributed on a CD. In that case, the complete source code had to be distributed on the same CD(-set).
In your case, you are distributing the code on a Web Host (the main difference between the AGPL and the GPL is that putting code on a web site is also considered as distribution). This means that you should host the complete source code on the same site where you deploy your application.
Everybody visiting your site needs to have access to your complete source code. As many companies wish to avoid this, they purchase a commercial license.
There is also a persistent misconception where some project manager think "we did not modify iText, hence we do not have the obligation to share our code." That is wrong: linking to an AGPL library is generally considered being a modification of the library.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 9 years ago.
Improve this question
I want a simple html and javascript based web page for editing a single document for documentation of an app that I am making. it should be editable by multiple people if possible asking for a password before it registers. I have ftp access to a web site but that is it. no database. I did not find anything that will point to a single file and just simply edit it without any software requirements. it would be nice if it were mobile friendly too.
I work for a hosting provider so that is a good question imo. What you are looking for is a flat file storage CMS to avoid a database. Requiring user management and simplicity you will not want to code this from scratch. We deal with alot of CMS (Content Management Systems) and most are bloated and require MySQL.
Check Out: http://get-simple.info/
I fired an installation up and it is very easy to install, has alot of features, and is very WordPress like which means it looks good out of the box and is very easy to use.
I hope this helps you out and if you do use it let me know your thoughts.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I'm thinking of making a web service that can file bugs on issue trackers through (mainly) xml-rpc. But I'd like to get a sense whether issue trackers nowadays tend to be available behind the firewall or on the internet...
The target for this web service would be companies that build websites.
So is your issue tracker (jira, bugzilla, trac etc) behind the firewall? (as opposed to being accessible on the internet)
Thanks!
At our shop, our bug tracker is accessible, because certain clients are allowed to file bugs. It really makes things easier, because the developer working on the ticket can directly solicit feedback from the client, rather than trying to get the project manager to get in touch and ask the right questions.
We had thought about doing something similar to what it sounds like you're thinking of, but never got around to implementing it.
Yes, ours is. We have it there partly for security and partly because there was no need to have it public to the world.
An issue tracker behind the firewall?! So it means you won't allow users outside to submit issues, and this is actually the only difference.
They could mail issues / bugs to someone inside, then ask the recipient to create that issue / bug.
BTW, the issue tracker of our company is behind the firewall, we really need to control every detail, as the users may not know what the problem is. We use firewall to ensure higher security and easier management.