Tag Info

New answers tagged

2

If you are in the United States, each state government maintains a registry of businesses in that state. Do a Google search like this: "register business georgia" (or whatever state the business is in.) For many states, you can look at the business records on line; in some, you'll have to go to a government office. That will tell you who owns the business ...


0

Any normal business needs to register with the Chamber of Commerce or whatever it is called in the country from which he runs his business. So check there. Even then - he can be a government agent!


2

Probabilistic or statistical authentication are probably the best fit, the alternative to deterministic authentication. (Though technically, there's a degree of probability involved when password hashes are used, rather than plaintext passwords, let's just ignore that for now.) Biometric implies a probabilistic system, but the converse is not true, e.g. ...


0

Most client-side solutions such as cookies and client certificates are not strictly machine-bound and can be exported to another device or circumvented if a user really wants to. One simple solution would be to loop a Kensington lock cable though the eye of a one-time-password dongle connected to the computer.


3

One relatively easy approach to this would be to create a persistent cookie on the client's side after the first log in. The cookie should hold only the user's username and a generated key. During the next log in the server would verify the key against the same key stored in the database and if it doesn't match or the user doesn't have the cookie at all you ...


0

As PiTheNumber said you can't just create or safe a file on the users drive. But you could let the user download your generated file so the user can open it with your desktop application after he finished downloading it. This is no problem with php, just send the right headers and almost every Browser will start the download. ...


0

Because of security restrictions you can not create a file on the client side. Using JavaScript you can however store data in Cookies or localStorage. See http://stackoverflow.com/questions/3950131/how-can-i-create-a-file-on-client-side-by-javascript You might be able to read this data from your Desktop App. See ...


1

Depending on metrics such as the false acceptance rate and the false rejection rate of your authentication system, you can set a similarity percentage for which your biometric authentication is acceptable. Also, I don't think you can speak of passwords regarding voice authentication because it relies on an inherence factor as you can see on Wikipedia.


0

There is usually a trade-off between security and usability. As a web developer, you have to decide what level of security is required for your application and strike a balance between the two. As correctly pointed out by you, there is an inconsistent treatment on the protection of email addresses on many websites. The reason is fairly simple: A login ...


1

If this is supposed to be a secure system to that extent and since the email address is disclosed elsewhere, the developers could make the username a randomly generated number instead of the user's email address. This closes the information leakage gap. For instance, for a generated numerical username: Failed login: "Username incorrect" Failed password: ...


0

An alternate approach and a legitimate one is to simply use a random Class 4 UUID1. This way you detach your keys from any changes in material circumstances and any shifts in your privacy attitude in your personal or professional life. If you intend to use key servers so that people may contact you securely from the onset (instead of sending a signed ...


2

Regarding your "password" approach, this is exactly how API keys work. If you want to use Facebook's API, or Stack Exchange's API (etc., etc.), you'll need to get an API key to identify yourself as a particular user of the API and send that API key with every request. Thus, every request that hits the API can be traced back to an originating user. This also ...


2

You can use HTTPS together with client certificate authentication. Then you can ensure that only clients with a valid certificate are able to use your site. The client certificate will then replace the password you mentioned and the user will not notice the magic done in the background.



Top 50 recent answers are included