Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The main problem here is that you're doing a whole lot of work and you're not getting any better security than a self-signed SSL certificate, and you set yourself up as being the responsible party to close any possible holes and maintain the security of your system (hint: this is a Big Deal).</p> <p>So, if you're talking about a generally available web application that you want your users to be able to just use, and use with confidence of security, then paying for a signed SSL certificate is really your only option. That said, a couple notes:</p> <ol> <li>The hashes you've mentioned are OK, but if you want real security use something like pbkdf2 (google this and your eyes will be opened to the depth and difficulty of real security)</li> <li>Without verifying the identity of the server (the purpose of signing in a signed SSL certificate) you open yourself up to man-in-the-middle attacks. If someone else can impersonate you, and has the full ability to "intercept, modify, and forge arbitrary messages between client and server", then it's simple for them to phish whatever info they want from your users. So, that's a problem you'll need to address if you intend for this to be a complete solution.</li> </ol> <p>Edit: After reading and thinking more about what you're looking for, I think I may have a solution for you.</p> <p>There's really two things that you could want to secure: your content, and your users credentials. You've determined that your content isn't worth spending $35 a year to secure, which is fair enough and perfectly reasonable. You still want to provide as much security as possible for your user's credentials, because that information is valuable to them and to those who would exploit it.</p> <p>Even though you don't want to spend the money to secure your content, you still want it only accessible to credentialed users. So, instead of making users create a username/password, which would be worth protecting, just have them log in with their email address.</p> <p>Your content and the email address are accessible to third parties of sufficient skill and motivation, but from what you've said, your content probably isn't worth that amount of effort, and their email address isn't that sensitive. But you still get to have a login gateway between the world and your content, and you can utilize a double opt-in to limit spam, etc. You can easily expand such a system to include a username/password and use SSL if your content grows to require it.</p>
    singulars
    1. This table or related slice is empty.
    1. POA proposal for Data Transmission and Password Encryption
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJason
    1. USJason
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks, there are many security issues incurred if i plan to implement sort of SSL by myself. Those are what I am worried about. The reason why I do not chose SSL is that there are not much sensitive date needed from the client site. Currently, i wish my website just provide some free of charge information to registered users. What the server need are just user id and password rather than further private information like credit card etc. for online transaction. Can't I say that the SSL provide much more than our demands?
      singulars
      1. PO
      1. USDamao17
    2. COi would take the second point seriously. if someone knew how the routine of how you site works, especially with the self-implemented security, anyone can just "clone" your site - literally reverse-engineer it, and impersonate it. a slight typo like a `.co` instead of a `.com` will never get noticed if the sites look and act the same.
      singulars
      1. PO
      1. USJoseph
    3. COGetting a signed SSL certificate for security is just the cost of doing business, much like the money you pay for hosting. The data is either worth securing properly, or not. Half security is no security.
      singulars
      1. PO
      1. USJason
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload