I hope they choke on it.
Apr. 7th, 2008 09:53 amI grumped about this last week, but now I am up against a deadline and I need to fill in some blanks.
3.3 Preliminary Orientations
The general orientations for a solution to manage the critical security aspects and leverage the context's beneficial elements.
Originally I was going to insert a fish as my answer, but I have decided to go with the following:
Who writes this stuff? What does this even mean?
We must engineer a proactive security solution which leverages the beneficial security elements contextually oriented within the vision framework.
Unprofessional? Perhaps a little, but I am tired of slogging my way through obfuscated documents dripping with corporate double-speak. I could sum up section three of this "Opportunities Document" with three questions that need answers:
1) How is application security handled today?
2) How will application security be handled tomorrow?
3) How will these changes affect the company and the end user?
A few years ago I attended a company-sponsored course on clarity in communication. They emphasized the need to be clear and concise in our correspondence, yet they seem to have no qualms about sending out bizarre documents laden with corporate lingo. Colour me unimpressed.
By the way, I haven't sent this document yet, so if you can help me to make my answer even more obscure, I welcome your input. >:)
3.3 Preliminary Orientations
The general orientations for a solution to manage the critical security aspects and leverage the context's beneficial elements.
Originally I was going to insert a fish as my answer, but I have decided to go with the following:
Who writes this stuff? What does this even mean?
We must engineer a proactive security solution which leverages the beneficial security elements contextually oriented within the vision framework.
Unprofessional? Perhaps a little, but I am tired of slogging my way through obfuscated documents dripping with corporate double-speak. I could sum up section three of this "Opportunities Document" with three questions that need answers:
1) How is application security handled today?
2) How will application security be handled tomorrow?
3) How will these changes affect the company and the end user?
A few years ago I attended a company-sponsored course on clarity in communication. They emphasized the need to be clear and concise in our correspondence, yet they seem to have no qualms about sending out bizarre documents laden with corporate lingo. Colour me unimpressed.
By the way, I haven't sent this document yet, so if you can help me to make my answer even more obscure, I welcome your input. >:)
no subject
Date: 2008-04-07 03:07 pm (UTC)Security is handled by the end user typing in a 128 character password, known only to me, exactly on the first try. Any mistyping forces a re-boot of his station and the main server. The end user is also forbidden to try again for 24 hours.
2) How will application security be handled tomorrow?
I change the password daily, and sometimes twice a day.
3) How will these changes affect the company and the end user?
No one, other than myself, will ever see the application, so security is maximized.
Of course your password, only accessible from your station, would be "Fish". :=3
no subject
Date: 2008-04-07 06:45 pm (UTC)If the user is locked out for 24 hours and assuming he does get it right on the very last try, he would spend 7936 days or 21.727583846680355920602327173169 years (21 years 8 months 22 days). Pretty secure in my book.
If you did not lock him out for 24 hours and he tried once a minute, it would take him 132.26666666666666666666666666667 hours or 5.5111111111111111111111111111111 days (5 days 12 hours 16 minutes). Still pretty secure. :=3
no subject
Date: 2008-04-07 07:50 pm (UTC)One character, there are 94 possible combinations.
Two characters, there are 94*94 possible combinations. 8836
Three character, 94*94*94. 830K
128 characters, 94^128. 3.6338 x 10^252
Number of seconds since the big bang, approx 441.8 x 10^15
Odds of someone remembering a 128 letter password - 0.0000
no subject
Date: 2008-04-07 11:35 pm (UTC)...and the new system at work will accept a 128 character password.
I suddenly feel a challenge coming on...
no subject
Date: 2008-04-08 03:47 am (UTC)no subject
Date: 2008-04-07 03:46 pm (UTC)Fish would probably get you in less trouble though.
no subject
Date: 2008-04-07 06:43 pm (UTC)no subject
Date: 2008-04-07 06:55 pm (UTC)no subject
Date: 2008-04-07 09:56 pm (UTC)An alternative approach is to repeatedly write "Please clarify the question" as the answer to each section. This works well if you don't want to do the project anytime soon. For bonus points submit the document to the project review board for clarification.