Skip to content

Commit c0517eb

Browse files
committed
plot color
1 parent 2a5a087 commit c0517eb

1 file changed

Lines changed: 0 additions & 30 deletions

File tree

python/heap_invariant_attack.ipynb

Lines changed: 0 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,5 @@
11
{
22
"cells": [
3-
{
4-
"cell_type": "markdown",
5-
"metadata": {},
6-
"source": [
7-
"I'm still not sure to get it, who is calling `data[i] = new`, ie., is it supposed to be a normal use of your object? If it is, then why is it? If it's not then just prevent accessing `__setitem__` on your heap. To me `data[i] = new` looks like an attack on your heap. If you really need to deal with this, then sorting your heap every time someone is attacking it seems perfectly fine to me. You could even do this in a lazier fashion, resorting only if someone is using normal heap methods. In any case your attacker code `data.index(old)` is so slow that any strategy will do. "
8-
]
9-
},
103
{
114
"cell_type": "code",
125
"execution_count": 1,
@@ -152,8 +145,6 @@
152145
"metadata": {},
153146
"outputs": [],
154147
"source": [
155-
"from collections import defaultdict\n",
156-
"\n",
157148
"results = []\n",
158149
"max_int = 500\n",
159150
"nb_updates = 1\n",
@@ -238,27 +229,6 @@
238229
" hue=\"method\",\n",
239230
")"
240231
]
241-
},
242-
{
243-
"cell_type": "code",
244-
"execution_count": null,
245-
"metadata": {},
246-
"outputs": [],
247-
"source": []
248-
},
249-
{
250-
"cell_type": "code",
251-
"execution_count": null,
252-
"metadata": {},
253-
"outputs": [],
254-
"source": []
255-
},
256-
{
257-
"cell_type": "code",
258-
"execution_count": null,
259-
"metadata": {},
260-
"outputs": [],
261-
"source": []
262232
}
263233
],
264234
"metadata": {

0 commit comments

Comments
 (0)