Timeline for How do command authorization codes work in Star Trek?
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2020 at 9:31 | history | edited | CommunityBot |
Commonmark migration
|
|
| Sep 13, 2015 at 6:16 | comment | added | user11521 | @MichaelViktorStarberg Wow, that's worse than Tuvok's two character password! | |
| Jun 6, 2013 at 3:44 | comment | added | Robotnik | @MichaelViktorStarberg - I think that movie was supposed to be crazily over the top... I think. (I hope so at least) | |
| Mar 7, 2013 at 22:42 | comment | added | Michael Viktor Starberg | Worse ever is in the movie Demolition Man. Sly: Access Secret Files. Computer: Access Denied! Sly: Override Computer: Access Granted | |
| Mar 7, 2013 at 22:40 | comment | added | Michael Viktor Starberg | Thaddeus: Would be more plausible if the code was like two GUID's expressed in nibbles in hex. Boss could start rambling and then cut to commercial and then we come back to the show ones he is almost done. But the eight-five-two-dash-seven is a worse code than 'give me access or else' | |
| Mar 7, 2013 at 22:34 | comment | added | Michael Viktor Starberg | I would also like to add that in Andromeda they use these super secret codes as Deux ex Machina whenever needed. Poor Dylan must have had to memorize thousands of them, as he always seem to have just the right one handy whenever catastrophy awaits. | |
| Mar 7, 2013 at 22:34 | comment | added | Thaddeus Howze | Yes, I agree. I worked with military intelligence in the military and every time I saw them using a code they rattle off from memory, I would just cringe. I remember having to look up authentication codes from a book, being given a table to reference and then comparing the two results. No way to memorize all of that and give a meaningful reply in the time we were allotted to authenticate. It's just bad writing from people unfamiliar with how security protocols really work. | |
| Mar 7, 2013 at 22:30 | comment | added | Michael Viktor Starberg | I would like to add that luckely for all of us, in the military and in financial institutions, any code that could cause serious damage used wrongly; are sealed secure and never seen until needed, let alone comitted to memory. | |
| Mar 7, 2013 at 20:22 | comment | added | Thaddeus Howze | Thank you. My memory isn't quite what it used to be. | |
| Mar 7, 2013 at 20:16 | comment | added | Bobby | If I remember the scene from ST II correct, Kirk did not hack anything, he knew the command codes of the Reliant. Short transcript: Kirk: "Mr Saavik, punch up the data charts of the Reliant's command console." Spock: "The prefix code?" Kirk: "It'S all we've got." ... Spock: "Reliant's prefix number is 16309." ... Spock: "Every starship has it's own code..." Kirk: "...to prevent the enemy from doing what we're attempting. Using our console to order Reliant to lower her shields." In layman's terms, he did log in via SSH, knowing the public key. | |
| Mar 7, 2013 at 20:02 | vote | accept | Peter | ||
| Mar 7, 2013 at 19:49 | history | edited | Thaddeus Howze | CC BY-SA 3.0 |
added 516 characters in body
|
| Mar 7, 2013 at 19:40 | history | answered | Thaddeus Howze | CC BY-SA 3.0 |