Security through, er, idiocy?
-
No comment needed...
If (InputBox("Access is highly restricted. Please enter the password: ") = "nooneneedstoseethisscreensokeepoutyoumonkey.") Then
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
-
No comment needed...
If (InputBox("Access is highly restricted. Please enter the password: ") = "nooneneedstoseethisscreensokeepoutyoumonkey.") Then
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
-
No comment needed...
If (InputBox("Access is highly restricted. Please enter the password: ") = "nooneneedstoseethisscreensokeepoutyoumonkey.") Then
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
According to http://xkcd.com/936/ -- password strength[^] that is the strongest password in the universe. :laugh: Albeit, cleartext does tend to make things a bit easier to hack. :)
-
No comment needed...
If (InputBox("Access is highly restricted. Please enter the password: ") = "nooneneedstoseethisscreensokeepoutyoumonkey.") Then
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
-
No comment needed...
If (InputBox("Access is highly restricted. Please enter the password: ") = "nooneneedstoseethisscreensokeepoutyoumonkey.") Then
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
-
No comment needed...
If (InputBox("Access is highly restricted. Please enter the password: ") = "nooneneedstoseethisscreensokeepoutyoumonkey.") Then
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
At my former employer we had a small config app with such a password baked into the code. It ran with all our clients on many computers. The regular user couldn't change the configs and we, and admins at the customers, always knew the password. A bit more secure than a regular config file or a non-password protected config app. It did the job! :thumbsup: I wouldn't use it on a website or anything though :laugh:
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
} -
At my former employer we had a small config app with such a password baked into the code. It ran with all our clients on many computers. The regular user couldn't change the configs and we, and admins at the customers, always knew the password. A bit more secure than a regular config file or a non-password protected config app. It did the job! :thumbsup: I wouldn't use it on a website or anything though :laugh:
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}Even in those circumstances, the password should at the very least be encrypted. Further, should it become necessary to change the password, your app will have to be rebuilt. There are many, many better alternatives.
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
-
Even in those circumstances, the password should at the very least be encrypted. Further, should it become necessary to change the password, your app will have to be rebuilt. There are many, many better alternatives.
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
Rob Grainger wrote:
the password should at the very least be encrypted.
Why? It wasn't a big secret. Just some local configuration...
Rob Grainger wrote:
should it become necessary to change the password
That was the beauty of it, the password was always the same!
Rob Grainger wrote:
There are many, many better alternatives
I know, I'd actually never use such a solution. I'm just saying it did the job of keeping users out and letting admins in ;)
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
} -
According to http://xkcd.com/936/ -- password strength[^] that is the strongest password in the universe. :laugh: Albeit, cleartext does tend to make things a bit easier to hack. :)
