Proceedings

More documents

Recommendations

Info

| 272 cooperation. Getting the new “playmates” to adopt the vision, culture and spirit of the original idea and holding true to it during the work on the proposal and negotiation process was a challenge indeed. The formal project organization required by the EU imposed more structure on the previous more free-floating agile process. Roles and responsibilities where staked out, conforming with the requirements of the roles but delegating as much as possible of the responsibilities and decision-making to the core developers. The strategy was to keep “conceptual integrity” (Brooks) of the vision and the idea in the hands of the core developers. A somewhat negative result was the added workload and responsibility on developers regarding EU related work. It is not too surprising that the consortium with its member organisation now employs a version-control/review based scheme regarding EU documents reflecting the technical development approaches. It remains a challenge for all partners of the consortium, universities and companies alike, to connect an ongoing medium-scale open-source project with EU regulations and requirements - not to speak of the fact that companies need to fund 50% of the costs themselves. It is, in fact, too early to judge the overall success of our approaches although we are confident that things work out reasonably well. 2.3 challenges: balancing community interests with EU requirements The nature of sprints changed when EU funding started. The need to meet milestones of promised deliverables and the goal to keep an open sprint process, still welcoming newcomers into the world of Pypy, made the sprints longer (at least 7 days with a break day in the middle) but also changed the nature of the sprints. The team started to distuingish between sprints open for all to attend, without any prior PyPy experience, and sprints requiring earlier PyPy involvement. Tutorials, start up planning meetings as well as daily status meetings evolved, the latest additions to the sprints are closing planning meetings (planning the work between sprints) and work-groups - a version of pair-programming in groups. Some other effects of sprinting within the EUstructure is that the sprint becomes a forum for nondevelopment work - coordinating and tracking the project. The challenge here is not affecting the main work and “disturbing” visiting developers with EUrelated work. It could also be argued that the prolonged sprints could possibly make it more difficult for non consortium members to attend the full time, disturbing other engagements etc. The project continues to try to adapt the method 5 of sprinting, evaluating feedback from sprint participants. Maybe the implementation within the PyPy team is slowly conforming to the Scrum standard of sprinting, but not as a conscious effort? 2.4 Managing diversities: agile business For a diverse group of organisations and people, agility is helpful at various levels: you cannot make all-encompassing plans and hope to statically follow them and succeed. New developments, twists and opportunities evolve all the time. Our experience with evolving PyPy from a loose Open Source project to a partially funded EU research project shows the following: • what first seemed like too diverse interests and views, impossible to tailor into a single project, was instead a fruitful mix of diversities. The challenge is to manage these diversities and channel them into constructive team efforts. Aiming for homogenity is the real threat. • what first seemed like unbeatable odds and too big obstacles sometimes even turned into new possibilities. The challenge is to maintain an atmosphere in which a team can act on those and within short timeframes of opportunities. Change is inevitable - how you handle it is the real challenge. • there are many other projects and organisations who are heading in similar directions of trying to connect and evolve agile open source strategies with business matters. Emerging models for developers distributed between different countries allows people with special interests to effectively work together and learn from each other. Concluding - the cumulative effects of an agile, open and dynamic team process combined with a market and curious first adopters facilitates agile business. A positive result is that a lot of people within the PyPy context found enjoyable jobs and there now already is evolving commercial interest despite the still early stages of the project - mostly from US companies though ... why european companies, especially larger ones, appear to prefer taking rather naive views on agile open-source development (“great, it’s cheaper, no license fees!”) is another interesting topic.
PyPy - the new Python implementation on the block Language/VM R&D, whole program type inference, translation to low level backends, fun Armin Rigo, Carl Friedrich Bolz, Holger Krekel 273 |
Page 2 and 3:
| 2
Page 5 and 6:
22. Chaos Communication Congress Pr
Page 7 and 8:
REPORTS 7 5 Thesis on Informational
Page 9 and 10:
10 5 Thesis on Informational- Cogni
Page 11 and 12:
5 THESIS ON INFORMATIONAL-COGNITIVE
Page 13 and 14:
Page 15 and 16:
Page 17:
Page 20 and 21:
UQBTng: a tool capable of automatic
Page 22 and 23:
IV. UQBT MODIFICATIONS A. Summary A
Page 24 and 25:
• if LHS of A is exactly sem str,
Page 27 and 28:
Advanced Buffer Overflow Methods [o
Page 29 and 30:
ADVANCED BUFFER OVERFLOW METHODS #i
Page 31 and 32:
ADVANCED BUFFER OVERFLOW METHODS 0x
Page 33 and 34:
ADVANCED BUFFER OVERFLOW METHODS in
Page 35:
ADVANCED BUFFER OVERFLOW METHODS }
Page 38 and 39:
| 34 Eine Führung in das europäis
Page 40 and 41:
| 36 Die kryptische Kennung 10 eine
Page 42 and 43:
| 38 senvertreter angewiesen. Die
Page 44 and 45:
| 40 Anonymous Data Broadcasting by
Page 46 and 47:
| 42 operate, consider the setting,
Page 48 and 49:
| 44 Figure 1: Anonymous data broad
Page 51 and 52:
Autodafé: An Act of Software Tortu
Page 53 and 54:
AUTODAFE - AN ACT OF SOFTWARE TORTU
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Bad TRIPs What the WTO Treaty did i
Page 63 and 64:
BAD TRIPS The TRIPS is especially h
Page 65:
BAD TRIPS Extension of the transiti
Page 68 and 69:
| 64 Collateral Damage Consequences
Page 70 and 71:
| 66 If one considers a DNSBL listi
Page 72 and 73:
| 68 • A number of sites do not h
Page 74 and 75:
| 70 to use other mailing software.
Page 76 and 77:
| 72 These kinds of checks tend to
Page 79 and 80:
COMPLETE Hard Disk Encryption with
Page 81 and 82:
COMPLETE HARD DISK ENCRYPTION WITH
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105:
Page 108 and 109:
| 104 x86-64 buffer overflow exploi
Page 110 and 111:
| 106 3 ELF64 LAYOUT AND X86-64 EXE
Page 112 and 113:
| 108 4 THE BORROWED CODE CHUNKS TE
Page 114 and 115:
| 110 5 AND DOES THIS REALLY WORK?
Page 116 and 117:
| 112 6 SINGLE WRITE EXPLOITS 9 48
Page 118 and 119:
| 114 6 SINGLE WRITE EXPLOITS 11 34
Page 120 and 121:
| 116 7 AUTOMATED EXPLOITATION 13 A
Page 122 and 123:
| 118 7 AUTOMATED EXPLOITATION 15 W
Page 124 and 125:
| 120 8 RELATED WORK 17 32 read(soc
Page 126 and 127:
| 122 11 CREDITS 19 11 Credits Than
Page 129 and 130:
Developing Intelligent Search Engin
Page 131 and 132:
DEVELOPING INTELLIGENT SEARCH ENGIN
Page 133 and 134:
DEVELOPING INTELLIGENT SEARCH ENGIN
Page 135 and 136:
Digital Identity and the Ghost in t
Page 137 and 138:
DIGITAL IDENTITY AND THE GHOST IN T
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145:
Page 148 and 149:
| 144
Page 150 and 151:
| 146
Page 153 and 154:
Esperanto, die internationale Sprac
Page 155 and 156:
ESPERANTO, DIE INTERNATIONALE SPRAC
Page 157 and 158:
ESPERANTO, DIE INTERNATIONALE SPRAC
Page 159 and 160:
Fair Code Free/Open Source Software
Page 161 and 162:
FAIR CODE 2. Von Digital Divide zu
Page 163 and 164:
FAIR CODE ökonomisch schlecht gest
Page 165 and 166:
FAIR CODE menschliches Verhalten re
Page 167:
FAIR CODE gewährleistet, und nur d
Page 170 and 171:
��
Page 172 and 173:
| 168 ��
Page 174 and 175:
| 170 ��
Page 176 and 177:
| 172 ��
Page 178 and 179:
| 174 ��
Page 180 and 181:
| 176 ��
Page 183 and 184:
Fuzzing Breaking software in an aut
Page 185 and 186:
FUZZING or protocol and fuzzing fra
Page 187 and 188:
FUZZING #define SOME_MAX 4096 if (y
Page 189 and 190:
Geometrie ohne Punkte, Geraden & Eb
Page 191 and 192:
GEOMETRIE OHNE PUNKTE, GERADEN & EB
Page 193:
GEOMETRIE OHNE PUNKTE, GERADEN & EB
Page 196 and 197:
| 192
Page 198 and 199:
| 194
Page 200 and 201:
| 196
Page 203 and 204:
Hacking OpenWRT Felix Fietkau 199 |
Page 205 and 206:
HACKING OPENWRT 1 Introduction to O
Page 207 and 208:
HACKING OPENWRT 3.2 Makefile This f
Page 209 and 210:
HACKING OPENWRT If your package is
Page 211 and 212:
HACKING OPENWRT 4.2 toolchain/ tool
Page 213 and 214:
HACKING OPENWRT To add a new platfo
Page 215 and 216:
Hopalong Casualty On automated vide
Page 217 and 218:
HOPALONG CASUALTY 2 Intro to Visual
Page 219 and 220:
HOPALONG CASUALTY Appearance As hum
Page 221 and 222:
HOPALONG CASUALTY A thorough review
Page 223 and 224:
Hosting a Hacking Challenge - CTF-s
Page 225 and 226: HOSTING A HACKING CHALLENGE - CTF-S
Page 227 and 228: HOSTING A HACKING CHALLENGE - CTF-S
Page 229: HOSTING A HACKING CHALLENGE - CTF-S
Page 232 and 233: | 228 1 Introduction Intrusion Dete
Page 234 and 235: | 230 • Changing file owner / gro
Page 236 and 237: | 232 Figure 2: Simple correlation
Page 239 and 240: Lyrical I Abschluss des CCC-Poesie-
Page 241 and 242: Magnetic Stripe Technology Joseph B
Page 243 and 244: MAGNETIC STRIPE TECHNOLOGY black re
Page 245 and 246: MAGNETIC STRIPE TECHNOLOGY My curre
Page 247 and 248: MAGNETIC STRIPE TECHNOLOGY MetroCar
Page 249 and 250: ��
Page 251 and 252: Code Listing (dmsb.c) ��
Page 253 and 254: Memory allocator security Yves Youn
Page 255 and 256: MEMORY ALLOCATOR SECURITY 251 |
Page 257 and 258: MEMORY ALLOCATOR SECURITY 253 |
Page 259 and 260: Message generation at the info laye
Page 261 and 262: MESSAGE GENERATION AT THE INFO LAYE
Page 269: MESSAGE GENERATION AT THE INFO LAYE
Page 272 and 273: | 268 Abstract Open Source, EU Fund
Page 274 and 275: | 270 lines of code x1e5 1.8 1.6 1.
Page 278 and 279: | 274 PyPy - The new Python Impleme
Page 280 and 281: | 276 performs abstract interpretat
Page 282 and 283: | 278 adding short cuts for some co
Page 284 and 285: | 280
Page 286 and 287: | 282
Page 288 and 289: | 284
Page 290 and 291: | 286
Page 292 and 293: | 288
Page 294 and 295: | 290
Page 296 and 297: | 292
Page 298 and 299: | 294 Die Risiken der Nanotechnik N
Page 300 and 301: | 296 Neue Materialien, einer der P
Page 302 and 303: | 298 wahrscheinlich nicht ausreich
Page 304 and 305: | 300 „State of the Future 2005
Page 307 and 308: The Web according to W3C How to tur
Page 309 and 310: THE WEB ACCORDING TO W3C 305 |
Page 311 and 312: THE WEB ACCORDING TO W3C 307 |
Page 313: THE WEB ACCORDING TO W3C our proces
Page 316 and 317: | 312 Transparenz der Verantwortung
Page 318 and 319: | 314 Transparenz der Verantwortung
Page 320 and 321: | 316 (6) Wird dem Betroffenen kein
Page 322 and 323: | 318 „anonymes Staatshandeln“
Page 324 and 325: | 320 Die Einschränkungen der Grun
Page 326 and 327:
| 322 11 wie es insbesondere an Hei
Page 328 and 329:
��
Page 330 and 331:
��
Page 332 and 333:
| 328 ��
Page 335 and 336:
Wargames - Hacker Spielen Männlich
Page 337 and 338:
WARGAMES - HACKER SPIELEN 333 |
Page 339 and 340:
Page 341 and 342:
Page 343 and 344:
Page 345 and 346:
Page 347 and 348:
Page 349 and 350:
Page 351 and 352:
Page 353 and 354:
Page 355 and 356:
Was ist technisches Wissen? Philoso
Page 357 and 358:
WAS IST TECHNISCHES WISSEN? ��
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Page 365 and 366:
Page 367 and 368:
��
Page 369 and 370:
��
Page 371 and 372:
Page 373:
Page 376 and 377:
| 372 ��
Page 378 and 379:
��
Page 380 and 381:
��
Page 382 and 383:
| 378
Page 384 and 385:
| 380
Page 386 and 387:
| 382
Page 388 and 389:
| 384
Page 390 and 391:
| 386
Page 392 and 393:
| 388
Page 394:
| 390
show all

Proceedings

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?