161:
know the last byte of every 8byte sequence we send (effectively 12.5% of all our data). Finding out 256 plaintext-ciphertext pairs is not hard at all in the internet world, given that standard protocols are used, and standard protocols have standard headers and commands (e.g. "get", "put", "mail from:", etc.) which the attacker can safely guess. On the other hand, if our cipher has this property (and is generally secure in other ways, too), the attacker would need to collect 2 (~10) plaintext-ciphertext pairs to crack the cipher in this way.
25:
193:
160:
of changing. The easiest way to show why this is good is the following: consider that if we changed our 8-byte plaintext's last byte, it would only have any effect on the 8th byte of the ciphertext. This would mean that if the attacker guessed 256 different plaintext-ciphertext pairs, he would always
46:
97:
69:
76:
230:
83:
65:
116:
54:
50:
254:
90:
223:
204:
35:
39:
148:
This is a desirable property to have in an encryption cipher, so that if one bit of the input (
249:
216:
170:
8:
134:
200:
243:
130:
157:
153:
149:
24:
192:
241:
224:
141:if the value of each output bit depends on
53:. Unsourced material may be challenged and
231:
217:
117:Learn how and when to remove this message
199:This cryptography-related article is a
152:) is changed, every bit of the output (
242:
187:
51:adding citations to reliable sources
18:
13:
14:
266:
191:
66:"Completeness" cryptography
23:
1:
179:
203:. You can help Knowledge by
7:
164:
10:
271:
186:
156:) has an average of 50%
171:Correlation immunity
47:improve this article
255:Cryptography stubs
212:
211:
127:
126:
119:
101:
16:Cryptography term
262:
233:
226:
219:
195:
188:
135:boolean function
122:
115:
111:
108:
102:
100:
59:
27:
19:
270:
269:
265:
264:
263:
261:
260:
259:
240:
239:
238:
237:
184:
182:
176:
167:
123:
112:
106:
103:
60:
58:
44:
28:
17:
12:
11:
5:
268:
258:
257:
252:
236:
235:
228:
221:
213:
210:
209:
196:
181:
178:
174:
173:
166:
163:
137:is said to be
125:
124:
31:
29:
22:
15:
9:
6:
4:
3:
2:
267:
256:
253:
251:
248:
247:
245:
234:
229:
227:
222:
220:
215:
214:
208:
206:
202:
197:
194:
190:
189:
185:
177:
172:
169:
168:
162:
159:
155:
151:
146:
145:input bits.
144:
140:
136:
132:
121:
118:
110:
99:
96:
92:
89:
85:
82:
78:
75:
71:
68: –
67:
63:
62:Find sources:
56:
52:
48:
42:
41:
37:
32:This article
30:
26:
21:
20:
250:Cryptography
205:expanding it
198:
183:
175:
147:
142:
138:
131:cryptography
128:
113:
104:
94:
87:
80:
73:
61:
45:Please help
33:
158:probability
244:Categories
180:References
154:ciphertext
77:newspapers
150:plaintext
107:June 2009
34:does not
165:See also
139:complete
91:scholar
55:removed
40:sources
93:
86:
79:
72:
64:
98:JSTOR
84:books
201:stub
133:, a
70:news
38:any
36:cite
143:all
129:In
49:by
246::
232:e
225:t
218:v
207:.
120:)
114:(
109:)
105:(
95:·
88:·
81:·
74:·
57:.
43:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
