Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If you're looking to do device authentication, you may want to consider mutually authenticated SSL. Here, you'd deploy a client identity certificate to each endpoint you'd want to authenticate. Then, you set the server up to require client authentication, so that a client would need to present a valid identity certificate in order to form the SSL tunnel. </p> <p>This, of course, is not a perfect solution. In reality, this presents much of the same weaknesses as other solutions (to various degrees) Once your client identity certificates go to your clients, they are out of your control; should a client give their certificate to anyone else, you lost the device authentication that you have based on it. SSL identity certificates are generally stored in a keystore on the client which is encrypted with a password or other credential needed to unlock them. While a client certificate could still be compromised, it's somewhat stronger that just a cookie or something like that (assuming you don't have a client that is trying to give away its credential). In addition, you'd want to come up with some validation routine that a client would need to go though in order to get a credential in the first place (how do I know that this is a client device that I <em>want</em> to remember/register?). </p> <p>Remember, these types of approaches only do <em>device</em> authentication, not users. There are more in-depth schemes already developed for device authentication than what I've mentioned; for example, 802.1x is a network protocol where an endpoint needs to present a client-side certificate to the network switch to get on a LAN. This is out-of-scope for a web application scenario, like what you've described, but the idea is the same (put a cryptographic credential on the client and validate it to establish the connection).</p> <p>This, like all other security matters really, is a risk decision. What are you trying to accomplish with such a countermeasure? What are the threats you're trying to prevent and what are the consequences if someone does log in on an unregistered device? Only your situation can answer those questions and let you see the real risk, if you need/should mitigate it, and, if so, how strong of a solution do you need to get the risk level down to an acceptable level?</p>
    singulars
    1. This table or related slice is empty.
    1. POReliable ways to register a user's computer with a server
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. This table or related slice is empty.
    1. COThe problem with the client authentication isn't that the client cerficates can be passed out (this can be addressed by issuing the certificate to specific IPs/DNs) but how will the client certificate be deployed/install to clients in the first place.If we are talking about thousands or even hundrend of devices this is impossible
      singulars
      1. PO
      1. USCratylus
    2. COYour suggestion for the SSL identity certificate looks like the solid option, thanks for the feedback. Basically, we are trying to provide solution options for two-factor login authentication. The obvious go-to would be something like CAC cards (smart cards), which some of the authors and editors on-site will own, but not necessarily all. We are exploring alternatives that, though not as secure, would allow for alternative user validation for access which would have a more limited scope of editorial and workflow permissions once the user is successfully logged in. I think we are set, thanks!
      singulars
      1. PO
      1. USdavmorr
    3. COIn this case, I think the SSL client auth mechanism makes a lot of sense. It's not as strong as a physical token, but for lower-risk-scenarios (which seem to match what you describe), it's appropriate.
      singulars
      1. PO
      1. This table or related slice is empty.
 

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