+- Madison Motorsports (https://forum.mmsports.org)
+-- Forum: Technical (https://forum.mmsports.org/forumdisplay.php?fid=4)
+--- Forum: Member's Projects (https://forum.mmsports.org/forumdisplay.php?fid=12)
+--- Thread: Project: Gravel Express MkII mod 0. (/showthread.php?tid=9725)
Re: Project: <Err#: 200013920, Decryption Failure> - V1GiLaNtE - 11-04-2011
Kaan Wrote:it better have gold rimz+ 1 bajillion
Re: Project: <Err#: 200013920, Decryption Failure> - CaptainHenreh - 11-04-2011
I will tell you it is NOT an STi, and it does NOT share a color with any of the other 3rd gen WRX's in MM.
I will also go through the reasoning. It pretty much went like this:
While I liked my Bugeye, liked it a lot, actually, in the end it wasn't really fast enough, or nice enough. I was spoiled by my Speed3, but disliked it for its traction problems (and absurd tires.)
So after I sold the bugeye, I thought long and hard about what to get. I came up with the following requirements:
4 or 5 doors (I do intend after all to reproduce at SOME point, 2 doors is no bueno)
Manual Transmission (I don't think I need to justify this)
Somewhere around 200 horsepower, although more is always nice. (Because)
Some level of luxury (Hey, I'm getting older. Nothing wrong with a little softness.)
And finally, Not Front Wheel Drive.
So with that in mind, I plugged all that into Deep Thought and meditated. IS300? Too slow. And if I'm going to drop anything that ends with "GTE" in it, all I'm going to have is an IS300 I paid too much for. (Although it'd be fast, for sure.) Plus, it's a lot of work. Almost did it, though. Looked at BMW's of various types, and determined that You People Are Crazy, to put up with such horseshit on a daily basis as justification for driving der ultimate driving machine. RX8, again, tempting! But the horsepower vs godawful fuel economy numbers were just too much for me to swallow. Thought about an S4, you know, with the sexy V8? Then I realized that no matter how many cylinders it had, it was always going to be an Audi and lolfuckthat. A G35 sedan got some attention, but in the end it was too difficult to find a manual trans AND decent mileage AND not be a million bucks.
So what I kept coming back to was a new WRX. Combine that with us (that is, MM) getting VIP pricing from Bob Wade, and it kept looking better and better. I didn't really want a new car, but I also had a firm "project" in the Jeep, so I didn't need something I was gonna dive balls deep into right off the bat.
So I thought about an STI. I really did. I wanted six forward gears. I wanted little world rally elves inside my differentials, making sure every single pony was going to the appropriate corner for maximum hoonage. I wanted big fat brembo brakes. I wanted my asscheeks gently cupped by alcantara, my love handles compressed by race-inspired bolsters. Hell, I wanted USD shocks and aluminum suspension bits. But damn son, those things cost fat stacks I ain't got, (or rather, don't want to give up) and that's doubly true for the 5 door. Combine that with none of that STI pixie dust actually mattering for shit and you've got a recipe for me not being able to justify an extra 6 grand.
So there you go. I was too late to order a 2011, so I had to wait and order a 2012. I suspect that this (the third gen) will actually end up being the "greatest" WRX generation since the GC, when it's judged over time.
Re: Project: <Err#: 200013920, Decryption Failure> - Evan - 11-04-2011
Jake Wrote:Colors... blue and red are both kinda bright. I'll wager on a Satin White Pearl WRX Premium.does the WRX come in girly periwinkle blue?
Re: Project: <Err#: 200013920, Decryption Failure> - Mike - 11-04-2011
CaptainHenreh Wrote:it wasn't really fast enough, or nice enough.
ferwhat?
Re: Project: <Err#: 200013920, Decryption Failure> - CaptainHenreh - 11-04-2011
Mike Wrote:CaptainHenreh Wrote:it wasn't really fast enough, or nice enough.
ferwhat?
ferme? :dunno: It was slower than my speed3, and had a bunch of miles on it. I didn't feel like I could reliably make it faster so, g'bye.
Re: Project: <Err#: 200013920, Decryption Failure> - CaptainHenreh - 11-05-2011
Since you donkeys are a bunch of knuckle dragging trogs, I'm gonna learn you something:
The Vigenere Cipher
Author: R. Morelli
From: <!-- m --><a class="postlink" href="http://www.cs.trincoll.edu/~crypto/historical/vigenere.html">http://www.cs.trincoll.edu/~crypto/historical/vigenere.html</a><!-- m -->
One of the main problems with simple substitution ciphers is that they are so vulnerable to frequency analysis. Given a sufficiently large ciphertext, it can easily be broken by mapping the frequency of its letters to the know frequencies of, say, English text. Therefore, to make ciphers more secure, cryptographers have long been interested in developing enciphering techniques that are immune to frequency analysis. One of the most common approaches is to suppress the normal frequency data by using more than one alphabet to encrypt the message. A polyalphabetic substitution cipher involves the use of two or more cipher alphabets. Instead of there being a one-to-one relationship between each letter and its substitute, there is a one-to-many relationship between each letter and its substitutes.
The Vigenere Tableau
The Vigenere Cipher, proposed by Blaise de Vigenere from the court of Henry III of France in the sixteenth century, is a polyalphabetic substitution based on the following tableau:
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
A A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
B B C D E F G H I J K L M N O P Q R S T U V W X Y Z A
C C D E F G H I J K L M N O P Q R S T U V W X Y Z A B
D D E F G H I J K L M N O P Q R S T U V W X Y Z A B C
E E F G H I J K L M N O P Q R S T U V W X Y Z A B C D
F F G H I J K L M N O P Q R S T U V W X Y Z A B C D E
G G H I J K L M N O P Q R S T U V W X Y Z A B C D E F
H H I J K L M N O P Q R S T U V W X Y Z A B C D E F G
I I J K L M N O P Q R S T U V W X Y Z A B C D E F G H
J J K L M N O P Q R S T U V W X Y Z A B C D E F G H I
K K L M N O P Q R S T U V W X Y Z A B C D E F G H I J
L L M N O P Q R S T U V W X Y Z A B C D E F G H I J K
M M N O P Q R S T U V W X Y Z A B C D E F G H I J K L
N N O P Q R S T U V W X Y Z A B C D E F G H I J K L M
O O P Q R S T U V W X Y Z A B C D E F G H I J K L M N
P P Q R S T U V W X Y Z A B C D E F G H I J K L M N O
Q Q R S T U V W X Y Z A B C D E F G H I J K L M N O P
R R S T U V W X Y Z A B C D E F G H I J K L M N O P Q
S S T U V W X Y Z A B C D E F G H I J K L M N O P Q R
T T U V W X Y Z A B C D E F G H I J K L M N O P Q R S
U U V W X Y Z A B C D E F G H I J K L M N O P Q R S T
V V W X Y Z A B C D E F G H I J K L M N O P Q R S T U
W W X Y Z A B C D E F G H I J K L M N O P Q R S T U V
X X Y Z A B C D E F G H I J K L M N O P Q R S T U V W
Y Y Z A B C D E F G H I J K L M N O P Q R S T U V W X
Z Z A B C D E F G H I J K L M N O P Q R S T U V W X Y
Note that each row of the table corresponds to a Caesar Cipher. The first row is a shift of 0; the second is a shift of 1; and the last is a shift of 25.
The Vigenere cipher uses this table together with a keyword to encipher a message. For example, suppose we wish to encipher the plaintext message:
TO BE OR NOT TO BE THAT IS THE QUESTION
using the keyword RELATIONS. We begin by writing the keyword, repeated as many times as necessary, above the plaintext message. To derive the ciphertext using the tableau, for each letter in the plaintext, one finds the intersection of the row given by the corresponding keyword letter and the column given by the plaintext letter itself to pick out the ciphertext letter.
Keyword: RELAT IONSR ELATI ONSRE LATIO NSREL
Plaintext: TOBEO RNOTT OBETH ATIST HEQUE STION
Ciphertext: KSMEH ZBBLK SMEMP OGAJX SEJCS FLZSY
Decipherment of an encrypted message is equally straightforward. One writes the keyword repeatedly above the message:
Keyword: RELAT IONSR ELATI ONSRE LATIO NSREL
Ciphertext: KSMEH ZBBLK SMEMP OGAJX SEJCS FLZSY
Plaintext: TOBEO RNOTT OBETH ATIST HEQUE STION
This time one uses the keyword letter to pick a column of the table and then traces down the column to the row containing the ciphertext letter. The index of that row is the plaintext letter.
The strength of the Vigenere cipher against frequency analysis can be seen by examining the above ciphertext. Note that there are 7 'T's in the plaintext message and that they have been encrypted by 'H,' 'L,' 'K,' 'M,' 'G,' 'X,' and 'L' respectively. This successfully masks the frequency characteristics of the English 'T.' One way of looking at this is to notice that each letter of our keyword RELATIONS picks out 1 of the 26 possible substitution alphabets given in the Vigenere tableau. Thus, any message encrypted by a Vigenere cipher is a collection of as many simple substitution ciphers as there are letters in the keyword.
Although the Vigenere cipher has all the features of a useful field cipher -- i.e., easily transportable key and tableau, requires no special apparatus, easy to apply, etc. -- it did not catch on its day. A variation of it, known as the Gronsfeld cipher , did catch on in Germany and was widely used in Central Europe. The Gronsfeld variant used the digits of a keynumber instead of a the letters of keyword, but remained unchanged in all other respects. So in fact the Gronsfeld is a weaker technique than Vigenere since it only uses 10 substitute alphabets (one per digit 0..9) instead of the 26 used by Vigenere.
Cryptanalyzing the Vigenere Cipher: The Kasiski/Kerckhoff Method
Vigenere-like substitution ciphers were regarded by many as practically unbreakable for 300 years. In 1863, a Prussian major named Kasiski proposed a method for breaking a Vigenere cipher that consisted of finding the length of the keyword and then dividing the message into that many simple substitution cryptograms. Frequency analysis could then be used to solve the resulting simple substitutions.
Kasiski's technique for finding the length of the keyword was based on measuring the distance between repeated bigrams in the ciphertext. Note that in the above cryptogram the plaintext bigram 'TO' occurs twice in the message at position 0 and 9 and in both cases it lines up perfectly with the first two letters of the keyword. Because of this it produces the same ciphertext bigram, 'KS.' The same can be said of plaintext 'BE' which occurs twice starting at positions 2 and 11, and also is encrypted with the same ciphertext bigram, 'ME.' In fact, any message encrypted with a Vigenere cipher will produce many such repeated bigrams. Although not every repeated bigram will be the result of the encryption of the same plaintext bigram, many will, and this provides the basis for breaking the cipher. By measuring and factoring the distances between recurring bigrams -- in this case the distance is 9 -- Kasiski was able to guess the length of the keyword. For this example,
Location: 01234 56789 01234 56789 01234 56789
Keyword: RELAT IONSR ELATI ONSRE LATIO NSREL
Plaintext: TOBEO RNOTT OBETH ATIST HEQUE STION
Ciphertext: KSMEH ZBBLK SMEMP OGAJX SEJCS FLZSY
the Kasiski method would create something like the following list:
Repeated Bigram Location Distance Factors
KS 9 9 3, 9
SM 10 9 3, 9
ME 11 9 3, 9
...
Factoring the distances between repeated bigrams is a way of identifying possible keyword lengths. Those factors that occur most frequently will be the best candidates for the length of the keyword. Note that in this example since 3 is also a factor of 9 (and any of its multiples) both 3 and 9 would be reasonable candidates for keyword length. Although in this example we don't have a clear favorite, we've narrowed down the possibilities to a very small list. Note also that if a longer ciphertext were encrypted with the same keyword ('RELATIONS'), we would expect to find repeated bigrams at multiples of 9 -- i.e., 18, 27, 81, etc. These would also have 3 as a factor. Kasiski's important contribution is to note this phenomenon of repeated bigrams and propose a method -- factoring of distances -- to analyze it.
Once the length of the keyword is known, the ciphertext can be broken up into that many simple substitution cryptograms. That is, for a keyword of length 9, every 9-th letter in the ciphertext was encrypted with the same keyword letter. Given the structure of the Vigenere tableau, this is equivalent to using 9 distinct simple substitution ciphers, each of which was derived from 1 of the 26 possible Caesar shifts given in the tableau. The pure Kasiski method proceeds by analyzing these simple substitution cryptograms using frequency analysis and the other standard techniques.
A variant of this method, proposed by the French cryptographer Kerckhoff, is based on discovering the keyword itself and then using it to decipher the cryptogram. In Kerckhoff's method, after the message has been separated into several columns, corresponding to the simple substitution cryptograms, one tallies the frequencies in each column and then uses frequency and logical analysis to construct the key. For example, suppose the most frequent letter in the first column is 'K'. We would hypothesize that 'K' corresponds to the English 'E'. If we consult the Vigenere tableau at this point, we can see that if English 'E' were enciphered into 'K' then row G of the table must have been the alphabet used for the first letter of the keyword. This implies that the first letter of the keyword is 'G'.
The problem with this "manual" approach is that for short messages there are often several good candidates for English 'E' in each column. This requires the testing of multiple hypotheses, which can get quite tedious and involved. Therefore we need a more sensitive test to discover the alphabet used by each letter of the keyword.
Recalling that each row of the Vigenere tableau is one of the 26 Caesar shifts, we can use the chi-square test to determine which of the 26 possible shifts was used for each letter of the keyword. This modern day version of the Kerckhoff method turns out to be very effective. And this is the algorithm that is used in CryptoToolJ's Vigenere Analyzer.
Re: Project: <Err#: 200013920, Decryption Failure> - CaptainHenreh - 12-29-2011
Though the winter of that year was mild, a cold wind blew through the prophet's heart, turning it stony and hard. A voice cried out in the wilderness, "Why do you turn your face from your servant? Did ye not say the number of weeks shall be likely thrice two, though not more than two fifths score? Why then hath that number and more thus elapsed?"
And from the white-capped mountain echoed, "Shit doth happen. Should thou hadst ordered the shade blue known World Rally, thou might be riding thy fine steed, the distant sound of thunder following your hoofbeats."
"But lord," He cried in desperation, "Already in the southlands art mine chosen chroma, yea but for a single option! And they didst have but FOUR weeks elapse from their supplication to their satisfaction!"
And the mountain replied: :dunno:
And thus, the prophet did pout like a whiney bitch.
Re: Project: <Err#: 200013920, Decryption Failure> - Dave - 12-29-2011
I lol'd.
Patience my son, though time passeth beyond expectation, the fruit shall be that much sweeter when it comes.
Re: Project: <Err#: 200013920, Decryption Failure> - BLINGMW - 12-29-2011
Where do you come up with this insanity? :dunno: :lol:
Re: Project: <Err#: 200013920, Decryption Failure> - Apoc - 12-29-2011
Dave Wrote:though time passeth beyond expectation, the fruit shall be that much sweeter when it comes.
Funny, I say that EXACT same thing to my wife.
Re: Project: <Err#: 200013920, Decryption Failure> - CaptainHenreh - 01-19-2012
77 Days.
That's how long I'd been searching for this dame. 77 miserable, frustrating, seemingly endless days. I wasn't even sure she existed. But my client, oh boy, he didn't care. The sign on the door said "Rex Steele, Private Investigator" but I was sure my mysterious client read it "Merlin, Magnificent Wizard" for the work he expected me to do. I'm a patient man, dogged even, but my patience has a limit and boy, I was drawing to it. "It should be pretty easy," he'd said. "She's from Japan, good figure, smart as a whip. She's in the transportation industry, if you catch my meaning." I did, sounded pretty tame. Most of those oriental broads were pretty simple to understand. "And, she's got dark blue hair." Well why do you even need me? I'd thought at the time. "Sounds like the kind of woman who'd stand out in a crowd," I said, through the smoke-laden atmosphere of the bar my unnamed client had insisted meeting me in. "Y-yeah," he stuttered. "When you see her, you'll know right away you've found her."
He reached inside his jacket, with drew a small pouch. It jangled when he tossed it on the table. "That's your retainer," he whispered. "It's yours whether you find her or not, but if you do, there's more where that came from." I opened the pouch just a fraction to see what was inside, and the bright yellow reflections from within nearly blinded me in the dusky bar. "Gold." I said. My mystery man nodded. Looking closer, I could make out an eagle...and below the eagle, I let out a hiss when I finally identified the symbol in the wreath. I nearly shut down the deal right there, and in retrospect I should have. My last big client had been months, and the makework I'd been doing for a local native american tribe had been more trouble than it was worth. I needed the money. "Are you out of your mind?" The sweat on his brow coalesced into a drop, and ran down the side of his face. It wasn't that hot in here. "It's...a family heirloom. It's all I have. Please, you can melt it down into bars and fence it that way. I know it wouldn't be worth as much, but it's still gold!"
I reached into my own pocket, glaring at my fat, sweaty client. My Colt Government, free from it's leather cage, slammed on the table. "Listen here you puke," I hissed. "You got a lot of nerve trying to sling that shit to me." He glanced left, right, trying to gauge how much help he'd have if he started squealing. But he'd chosen this venue for its discretion, and that's exactly what he was getting. "P-please. I'm in love. I have to find her! Mr. Steele you're my only hope!" I leaned back in my chair, the cold blue steel of the colt punctuating my body language. "Please," he begged. I wanted him to think I was considering walking, but I'd made my decision the minute I walked in the bar. And the gold didn't hurt. It might be forbidden, but it was still gold. And the gods knew I needed gold.
"Alright. We're done here," I said, putting the colt back in its home under my jacket. "But I'll expect triple this on delivery. You good for that?" He nodded sharply, sweat slinging off his forehead. I grabbed the gold pouch off the dusty table as I stood, enjoying the warm weight of the coins inside. "I'll call you," I said over my shoulder.
That was 77 days ago. This bitch is a ghost.
Re: Project: <Err#: 200013920, Decryption Failure> - Evan - 01-19-2012
Dude, you're related to Ginger?
Re: Project: <Err#: 200013920, Decryption Failure> - JPolen01 - 01-19-2012
So did your car not make it into the sea container or something?
Re: Project: <Err#: 200013920, Decryption Failure> - xvxax - 01-19-2012
Can a brother get a tl;dr?
Re: Project: <Err#: 200013920, Decryption Failure> - CaptainHenreh - 01-19-2012
Evan Wrote:Dude, you're related to Ginger?
I wish, if only for the bitchin' last name.
I mean, seriously. Steele. You might as well go ahead and start fighting crime because man.
Re: Project: <Err#: 200013920, Decryption Failure> - Apoc - 01-19-2012
Steele DDS
Re: Project: <Err#: 200013920, Decryption Failure> - Evan - 01-19-2012
xvxax Wrote:Can a brother get a tl;dr?
Story Time With Uncle Rexy is worth the read, n00b!
Re: Project: <Err#: 200013920, Decryption Failure> - Evan - 01-19-2012
CaptainHenreh Wrote:Evan Wrote:Dude, you're related to Ginger?
I wish, if only for the bitchin' last name.
I mean, seriously. Steele. You might as well go ahead and start fighting crime because man.
But then you're a skinny little white kid with red hair. God has a sense of humor.
Re: Project: <Err#: 200013920, Decryption Failure> - Ginger - 01-19-2012
Rex is my friend. I hate the rest of you fuckers.
Re: Project: <Err#: 200013920, Decryption Failure> - CaptainHenreh - 01-24-2012
Incoming transmission. Stand by.