-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathvita.html
446 lines (436 loc) · 51.7 KB
/
vita.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
<!DOCTYPE html>
<html>
<head>
<title>Vita</title>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<meta name="keywords" content="R Markdown, academic CV, template" />
<style>
/* make sure the resources are "tight" against their related metadata... */
div.references div p {
margin: 0;
padding: 0;
}
/* ...but make a little space between bib items */
.resource-container {
padding-bottom: 1rem;
}
/* text box for abstract should have a little space */
.resource-container div.abstract-text-container {
margin: 1rem;
padding: 1rem;
}
/* resource buttons should have a little space between them (+ text shouldn't be underlined) */
.btn {
margin: 0.1rem;
text-decoration: none;
}
span.author {
text-decoration: underline;
font-style: italic;
}
</style>
<!-- Latest compiled and minified CSS -->
<link rel="stylesheet" href="https://stackpath.bootstrapcdn.com/bootstrap/3.4.1/css/bootstrap.min.css" integrity="sha384-HSMxcRTRxnN+Bdg0JdbxYKrThecOKuH5zCYotlSAcp1+c8xmyTe9GYg1l9a69psu" crossorigin="anonymous">
<link rel="stylesheet" href="bib.css" />
</head>
<body>
<!-- Genereated on Mon Apr 22 22:23:03 EDT 2019 -->
<h1 id="hi">Hi!</h1>
<p>I’m <strong>Travis Peters</strong>, an n^th year PhD student at <a href="https://dartmouth.edu">Dartmouth</a>. I am advised by <a href="http://www.cs.dartmouth.edu/~dfk/">Dr. David Kotz</a>. My “condition,” however, is terminal: In Fall 2019 I will join as an Assistant Professor of Computer Science in the <a href="https://www.cs.montana.edu">Gianforte School of Computing</a> at <a href="http://www.montana.edu">Montana State University</a>.</p>
<p>My research covers a range of topics in Security & Privacy and Ubiquitous Computing including network traffic analysis, embedded system security, ad hoc networks, operating systems, trusted computing, and security and privacy in the <em>Internet of Things (IoT)</em>. I am currently a member of the <a href="https://thaw.org/">Trustworthy Health & Wellness (THaW)</a> project where I’m exploring research problems in mobile health and IoT systems and networks. I am also a former member of the <a href="https://amulet-project.org/">Amulet</a> project where I worked on the design of a low-power and secure wearable device, as well as a software framework that enables developers to create safe, secure, and efficient mobile health applications. My work targets top venues such as USENIX Security, CCS, NDSS, Oakland, MobiSys, MobiCom, and SenSys.</p>
<p>I will obtain my Ph.D. in 2019 from <a href="https://dartmouth.edu">Dartmouth</a> where I have been advised by <a href="http://www.cs.dartmouth.edu/~dfk/">David Kotz</a>. I obtained my B.S. in 2012 from <a href="https://www.wwu.edu">Western Washington University</a> where I was mentored by <a href="https://cse.wwu.edu/computer-science/fizzanp">Perry Fizzano</a>. I spent two summers (2015 & 2016) at Intel Labs as a security researcher in their Security & Privacy Research group.</p>
<p><strong>Looking for bright students</strong></p>
<p>I am looking for bright and passionate students to work with! Email me if your are interested in working with me. Before you do, please read this FAQ.</p>
<h1 id="research-interests">Research Interests <!-- SQUEEZE --></h1>
<p>Mobile Health and IoT Security; <!-- SQUEEZE --> Computer and Wireless Network Security; <!-- SQUEEZE --> Trusted Computing; <!-- SQUEEZE --> Mobile and Wireless Systems; <!-- SQUEEZE --> Machine Learning & Multivariate Statistics <!-- SQUEEZE --></p>
<h1 id="current-appointments">Current Appointments </h1>
<p><strong>Assitant Professor</strong>, <em>Gianforte School of Computing, Montana State University</em> August 2019 - Present</p>
<p><strong>Director of Cybersecurity</strong>, <em>clinicIQ</em> August 2019 - Present</p>
<h1 id="education">Education</h1>
<!-- Dartmouth College (September 2013 - June 2019 (expected)) -->
<p><strong>Ph.D., Computer Science</strong> 2013 - Present (Expected: June 2019)<br />
<em>Dartmouth College</em>, Hanover, NH<br />
Dissertation Title: “Enabling Trustworthy Interactions Between User-Centric Ubiquitous Devices”<br />
Advisor: Dr. David Kotz <!-- SQUEEZE --> Doctoral Committee: Dr. David Kotz, Dr. Sean Smith, Dr. Xia Zhou, Dr. José Camacho <!-- SQUEEZE --></p>
<!-- Western Washington University (September 2008 - December 2012) -->
<p><strong>B.S., Mathematics & Computer Science</strong> 2008 - 2012<br />
<em>Western Washington University (WWU)</em>, Bellingham, WA</p>
<h1 id="teaching-experience">Teaching Experience</h1>
<h2 id="instructor">Instructor</h2>
<p><strong>Problem Solving via Object-Oriented Programming (COSC 10)</strong>, <em>Dartmouth College</em> Winter 2015<br />
<em>Class details: approximately 120 students; majors and non-majors; course staff of 13 TAs</em><br />
<em>My course website is available at <a href="https://www.traviswpeters.com/cs10/" class="uri">https://www.traviswpeters.com/cs10/</a>.</em></p>
<h2 id="teaching-assistant">Teaching Assistant</h2>
<!-- Professor: David Kotz -->
<p><strong>Software Design & Implementation (COSC 50)</strong>, <em>Dartmouth College</em> Spring 2016<br />
<em>Class details: approximately 50 students; majors</em></p>
<!--
Designed a new culminating project where students work in teams to program smartwatch programs and a backend server
that facilitate a capture-the-flag-style game.
I designed built the infrastructure and assisted in design reviews, and final reviews.
-->
<!-- Professor: Hany Farid -->
<p><strong>Introduction to Programming & Computing (COSC 1)</strong>, <em>Dartmouth College</em> Spring 2014<br />
<em>Class details: approximately 180 students; majors and non-majors</em></p>
<!-- Professor: Chris Bailey-Kellogg -->
<p><strong>Problem Solving via Object-Oriented Programming (COSC 10)</strong>, <em>Dartmouth College</em> Winter 2014<br />
<em>Class details: approximately 100 students; majors and non-majors</em></p>
<!-- Professor: Tom Cormen -->
<p><strong>Introduction to Programming & Computing (COSC 1)</strong>, <em>Dartmouth College</em> Fall 2013<br />
<em>Class details: approximately 120 students; majors and non-majors</em></p>
<!-- Computer Science Teaching Assistant - Western Washington University -->
<p><strong>Programming Fundamentals in C++ (CSCI 140)</strong>, <em>Western Washington University</em> Fall 2012<br />
<em>Class details: approximately 40 students; majors and non-majors</em></p>
<!--
- Proctored two lab sections for Computer Science 140 (Programming Fundamentals in C++), held regular office hours, and graded laboratory assignments.
- Helped students understand fundamental concepts behind the C++ programming language, elementary data structures, basic building and compilation on UNIX systems, and simple sorting/searing algorithms.
-->
<!-- Head Teacher: Lisa Mustion -->
<p><strong>Teaching Assistant (K-8)</strong>, <em>Family House Academy</em> Summer 2009<br />
<em>Class details: approximately 20 students; subjects: mathematics, reading, and writing</em></p>
<h2 id="guest-lecturer">Guest Lecturer</h2>
<!-- Debugging with GDB and Valgrind - Professors (Gevorg'18, Kotz'17, Kotz'16) -->
<p><strong>Debugging with GDB and Valgrind</strong>, <em>Dartmouth College (COSC 50)</em> April 2016, April 2017, January 2018<br />
<em>A 65-minute lecture on debugging program logic and memory leaks with GDB and Valgrind.</em><br />
<em>Notes available at <a href="https://www.traviswpeters.com/classes/debugging-gdb-valgrind/" class="uri">https://www.traviswpeters.com/classes/debugging-gdb-valgrind/</a>.</em></p>
<!--
This lesson includes an exercise where students get to discover and fix a buffer-overflow vulnerability.
-->
<!-- Introduction to Pebble Development - Professors (Kotz) -->
<p><strong>Introduction to Pebble Development</strong>, <em>Dartmouth College (COSC 50)</em> April 2016<br />
<em>A 65-minute lecture on programming on Pebble smartwatches and a culminating team project.</em><br />
<em>Notes available at <a href="https://www.traviswpeters.com/classes/pebble-project-intro/" class="uri">https://www.traviswpeters.com/classes/pebble-project-intro/</a>.</em></p>
<!-- Three Kinds of Memory - Professors (Kotz) -->
<p><strong>Three Kinds of Memory</strong>, <em>Dartmouth College (COSC 50)</em> April 2016<br />
<em>A 65-minute lecture on understanding the different kinds of memory and basic memory management in C.</em><br />
<em>Notes available at <a href="https://www.traviswpeters.com/classes/memory/" class="uri">https://www.traviswpeters.com/classes/memory/</a>.</em></p>
<h1 id="research-experience">Research Experience</h1>
<!--
Need to make it clear what is YOUR work.
TODO: who do you collaborate with?
TODO: WHAT do you do? build systems? analyze data? use active words.
collaborated.. oversaw... led...
Sought out collaborators at.... to enhance research...
-->
<!-- Research Assistant @ Dartmouth - Advisor: David Kotz -->
<p><strong>Research Assistant</strong>, <em>Dartmouth College, Hanover, NH</em> January 2014 - Present<br />
I collaborate with multidisciplinary teams to research security and privacy threats in mobile health (mHealth). My work focuses on system and network security within personal area networks and body area networks of health and wellness devices. My work achieves security through the design and experimental validation of novel hardware and software architectures. My current research is investigating how to detect malicious or errant devices in networks of personal devices by developing models based on network traffic and conducting comparative analysis. <!--
For more information, visit our project websites:
Trustworthy Health and Wellness (\url{thaw.org}) and The Amulet Project (\url{amulet-project.org}).
--></p>
<!-- Security Research Intern @ Intel - Mentors: Srikanths Varadarajan, Pradeep Pappachan, Reshma Lal -->
<p><strong>Security Research Intern</strong>, <em>Intel Labs, Hillsboro, OR</em> June 2016 - September 2016<br />
Worked with industry experts to conduct a survey on security and privacy threats in the Internet of Things (IoT). Presented findings to researchers and product groups; aided team in developing a larger IoT security research agenda.</p>
<!-- Security Research Intern @ Intel - Mentors: Srikanths Varadarajan, Pradeep Pappachan, Reshma Lal -->
<p><strong>Security Research Intern</strong>, <em>Intel Labs, Hillsboro, OR</em> June 2015 - September 2015<br />
Designed and implemented a security architecture to enhance Bluetooth security on Intel’s SGX-enabled platforms. Published and presented a paper in <em>HASP’18</em>, and filed for a related patent.</p>
<h1 id="industry-experience">Industry Experience</h1>
<p><!-- DevOps Engineer (Contractor) - https://www.microfocus.com/attachmate/ --> <strong>DevOps Engineer</strong>, <em>Attachmate, Bellingham/Seattle, WA</em> January 2013 - August 2013</p>
<ul>
<li>Designed and built an automated virtual machine (VM) template management infrastructure using Chef and VMware’s vCloud Director. The infrastructure automated how VMs running various operating systems (Windows, Red Hat Linux, SUSE) are deployed and maintained (patched & updated).</li>
<li>Developed automation routines in Ruby, Bash, and Batch (install software, configure machine settings, etc.).</li>
<li>Wrote and maintained design specifications and unit tests.</li>
</ul>
<!--
Luminet = Enterprise Fraud Management system; insider fraud, failed audits
Sentinel� is a full-featured Security Information and Event Management (SIEM) solution that simplifies the deployment, management and day-to-day use of SIEM,
readily adapts to dynamic enterprise environments and delivers the true "actionable intelligence" security professionals need to quickly understand their threat posture and prioritize response.
Software Engineer Intern - https://www.microfocus.com/attachmate/
-->
<p><strong>Software Engineer Intern</strong>, <em>Attachmate, Bellingham, WA</em> August 2012 - December 2012</p>
<ul>
<li>Extended Luminet (enterprise fraud management system) to integrate with various Security Information & Event Management (SIEM) systems. The extensions used our customizable XML configuration file to enable network operators to configure Luminet to log to various SIEMs.</li>
<li>Demonstrated correctness of code through implementation of unit tests & automated testing methods.</li>
<li>Presented project results and live demo to the Luminet product team.</li>
</ul>
<!-- Developer & Intern Team Lead - https://explore.emergencyreporting.com/ -->
<p><strong>Mobile Developer & Intern Team Lead</strong>, <em>Emergency Reporting, Bellingham, WA</em> January 2012 - June 2012</p>
<ul>
<li>Designed and implemented a mobile application to aid Fire/Rescue and EMS responders. This application enabled better in-the-field access to Emergency Reporting’s cloud-based record and reporting management system. (Our work spearheaded what is now the InspectER mobile app.)</li>
<li>Led team of four interns to implement compatible mobile application on iOS and Android platforms.</li>
<li>Implemented data security (at-rest and in-transit), database access, and integration with Google Maps.</li>
</ul>
<h1 id="other-work-experience">Other Work Experience</h1>
<!-- Vice President for Business & Operations -->
<p><strong>Vice President for Business & Operations</strong>, <em>Associated Students of WWU</em> June 2011 - June 2012</p>
<ul>
<li>Elected by the student body of Western Washington University (more than <span class="math inline">15, 000</span> students).</li>
<li>Charged with overseeing the internal operations of the Associated Students programs, services, and facilities. <!-- and the facilities in which they operate. --></li>
<li>Managed six other student managers of departments with as many as 20 employees each.</li>
<li>Facilitated organizational budgeting process, employee hiring process, and internal program assessment.</li>
<li>Chaired committee to develop operating & non-operating budget for fiscal year 2012 ($<span class="math inline">3.1</span> million budget).</li>
</ul>
<!-- Marketing & Technical Associate -->
<p><strong>Marketing & Technical Associate</strong>, <em>Caso Inc., San Antonio, TX</em> June 2010 - January 2011</p>
<ul>
<li>Collaborated with the marketing team to implement search engine optimization of company website.</li>
<li>Advised a team of department leaders to pilot a new organizational management system. <!-- (data storage of products, project information/status, and client records). --></li>
</ul>
<h1 id="publications">
Publications
</h1>
<div id="refs" class="references" role="doc-bibliography" role="doc-bibliography">
<div id="ref-pierson:snap">
<p>
Timothy J. Pierson, <span class="author">Travis Peters</span>, Ronald Peterson, and David Kotz. <strong>Proximity Detection with Single-Antenna IoT Devices</strong>. In <em>Proceedings of the ACM International Conference on Mobile Computing and Networking (MobiCom)</em>, pages 1–12. ACM Press, October 2019. Accepted for Publication. Acceptance Rate 24%.
</p>
<div class="resource-container">
<a class="btn btn-primary btn-xs" role="button" href="https://www.traviswpeters.com/papers/pierson-snap-mobicom2019.pdf">PDF</a><a class="btn btn-primary btn-xs" role="button" href="https://doi.org/10.1145/3300061.3300120">DOI</a><button class="btn btn-primary btn-xs abstract-btn" type="button" data-toggle="collapse">Abstract</button>
<div class="collapse well panel-body abstract-text-container">
Providing secure communications between wireless devices that encounter each other on an ad-hoc basis is a challenge that has not yet been fully addressed. In these cases, close physical proximity among devices that have never shared a secret key is sometimes used as a basis of trust; devices in close proximity are deemed trustworthy while more distant devices are viewed as potential adversaries. Because radio waves are invisible, however, a user may believe a wireless device is communicating with a nearby device when in fact the user’s device is communicating with a distant adversary. Researchers have previously proposed methods for multi-antenna devices to ascertain physical proximity with other devices, but devices with a single antenna, such as those commonly used in the Internet of Things, cannot take advantage of these techniques.We present theoretical and practical evaluation of a method called SNAP – SiNgle Antenna Proximity – that allows a single-antenna Wi-Fi device to quickly determine proximity with another Wi-Fi device. Our proximity detection technique leverages the repeating nature Wi-Fi’s preamble and the behavior of a signal in a transmitting antenna’s near-field region to detect proximity with high probability; SNAP never falsely declares proximity at ranges longer than 14 cm.
</div>
</div>
</div>
<div id="ref-pierson:closetalker">
<p>
Timothy Pierson, <span class="author">Travis Peters</span>, Reza Rawassizadeh, Ronald Peterson, and David Kotz. <strong>CloseTalker: Secure, Short-Range Ad Hoc Wireless Communication</strong>. In <em>Proceedings of the ACM International Conference on Mobile Systems, Applications, and Services (MobiSys)</em>, pages 1–12. ACM Press, June 2019. Accepted for Publication. Acceptance Rate 23%.
</p>
<div class="resource-container">
<button class="btn btn-primary btn-xs abstract-btn" type="button" data-toggle="collapse">
Abstract
</button>
<div class="collapse well panel-body abstract-text-container">
Secure communication is difficult to arrange between devices that have not previously shared a secret. Previous solutions to the problem are susceptible to man-in-the-middle attacks, require additional hardware for out-of-band communication, or require an extensive public-key infrastructure. Furthermore, as the number of wireless devices explodes with the advent of the Internet of Things, it will be impractical to manually configure each device to communicate with its neighbors or with the local WLAN.Our system, <em>CloseTalker</em>CloseTalker, allows simple, secure, ad hoc communication between devices in close physical proximity, while jamming the signal so it is unintelligible to any receivers more than a few centimeters away. CloseTalker does not require any specialized hardware or sensors in the devices, does not require complex algorithms or cryptography libraries, occurs only when intended by the user, and can transmit a short burst of data or an address and key that can be used to establish long-term or long-range communications at full bandwidth.In this paper we present a theoretical and practical evaluation of CloseTalker, which exploits Wi-Fi MIMO antennas and the fundamental physics of radio to establish secure communication between devices that have never previously met. We demonstrate that CloseTalker is able to facilitate secure in-band communication between devices in close physical proximity (about 5 cm), even though they have never met nor shared a key.
</div>
</div>
</div>
<div id="ref-peters:bastionsgx">
<p>
<span class="author">Travis Peters</span>, Reshma Lal, Srikanth Varadarajan, Pradeep Pappachan, and David Kotz. <strong>BASTION-SGX: Bluetooth and Architectural Support for Trusted I/O on SGX</strong>. In <em>Proceedings of the International Workshop on Hardware and Architectural Support for Security and Privacy (HASP)</em>, pages 1–9. ACM, June 2018. Acceptance Rate 42%.
</p>
<div class="resource-container">
<a class="btn btn-primary btn-xs" role="button" href="https://www.traviswpeters.com/papers/peters-hasp2018.pdf">PDF</a><a class="btn btn-primary btn-xs" role="button" href="https://doi.org/10.1145/3214292.3214295">DOI</a><button class="btn btn-primary btn-xs abstract-btn" type="button" data-toggle="collapse">Abstract</button>
<div class="collapse well panel-body abstract-text-container">
This paper presents work towards realizing architectural support for Bluetooth Trusted I/O on SGX-enabled platforms, with the goal of providing I/O data protection that does not rely on system software security. Indeed, we are primarily concerned with protecting I/O from all software adversaries, including privileged software. In this paper we describe the challenges in designing and implementing Trusted I/O at the architectural level for Bluetooth. We propose solutions to these challenges. In addition, we describe our proof-of-concept work that extends existing over-the-air Bluetooth security all the way to an SGX enclave by securing user data between the Bluetooth Controller and an SGX enclave.
</div>
</div>
</div>
<div id="ref-pierson:snap-poster">
<p>
Timothy J. Pierson, <span class="author">Travis Peters</span>, Ronald Peterson, and David Kotz. <strong>Poster: Proximity Detection with Single-Antenna IoT Devices</strong>. In <em>Proceedings of the ACM International Conference on Mobile Computing and Networking (MobiCom)</em>, pages 663–665. ACM Press, October 2018. Best Poster Award. Acceptance Rate 50%.
</p>
<div class="resource-container">
<a class="btn btn-primary btn-xs" role="button" href="https://www.traviswpeters.com/papers/posters/mobicom2018_snap_poster.pdf">PDF</a><a class="btn btn-primary btn-xs" role="button" href="https://doi.org/10.1145/3241539.3267751">DOI</a><button class="btn btn-primary btn-xs abstract-btn" type="button" data-toggle="collapse">Abstract</button>
<div class="collapse well panel-body abstract-text-container">
Close physical proximity among wireless devices that have never shared a secret key is sometimes used as a basis of trust. In these cases, devices in close proximity are deemed trustworthy while more distant devices are viewed as potential adversaries. Because radio waves are invisible, however, a user may believe a wireless device is communicating with a nearby device when in fact the user’s device is communicating with a distant adversary. Researchers have previously proposed methods for multi-antenna devices to ascertain physical proximity with other devices, but devices with a single antenna, such as those commonly used in the Internet of Things, cannot take advantage of these techniques. We investigate a method for a single-antenna Wi-Fi device to quickly determine proximity with another Wi-Fi device. Our approach leverages the repeating nature Wi-Fi’s preamble and the characteristics of a transmitting antenna’s near field to detect proximity with high probability. Our method never falsely declares proximity at ranges longer than 14 cm.
</div>
</div>
</div>
<div id="ref-tiopatent2018">
<p>
Srikanth Varadarajan, Reshma Lal, Steven B. McGowan, Hakan Magnus Eriksson, and <span class="author">Travis W. Peters</span>. <strong>System, Apparatus and Method for Providing Trusted Input/Output Communications</strong>. May 2018. Patent Pending. Priority date 2016-11-21; Filing date 2016-11-21; Publication date 2018-05-24.
</p>
<div class="resource-container">
<a class="btn btn-primary btn-xs" role="button" href="https://patents.google.com/patent/US20180145951A1/en">Patent</a><button class="btn btn-primary btn-xs abstract-btn" type="button" data-toggle="collapse">Abstract</button>
<div class="collapse well panel-body abstract-text-container">
In one embodiment, an apparatus includes a wireless controller, which may include a byte stream parser to receive a stream of data from one or more wireless devices and parse the stream of data to identify a first data packet associated with a first channel identifier associated with a trusted application, and a cryptographic engine coupled to the byte stream parser to encrypt a payload portion of the first data packet in response to the identification of the first data packet associated with the first channel identifier. Other embodiments are described and claimed.
</div>
</div>
</div>
<div id="ref-kotz:safethings">
<p>
David Kotz and <span class="author">Travis Peters</span>. <strong>Challenges to Ensuring Human Safety Throughout the Life-Cycle of Smart Environments</strong>. In <em>Proceedings of the ACM Workshop on the Internet of Safe Things (SafeThings)</em>, pages 1–7. ACM, November 2017. Acceptance Rate 54%.
</p>
<div class="resource-container">
<a class="btn btn-primary btn-xs" role="button" href="http://www.traviswpeters.com/papers/kotz-safethings2017.pdf">PDF</a><a class="btn btn-primary btn-xs" role="button" href="https://doi.org/10.1145/3137003.3137012">DOI</a><button class="btn btn-primary btn-xs abstract-btn" type="button" data-toggle="collapse">Abstract</button>
<div class="collapse well panel-body abstract-text-container">
The homes, offices, and vehicles of tomorrow will be embedded with numerous “Smart Things,” networked with each other and with the Internet. Many of these Things are embedded in the physical infrastructure, and like the infrastructure they are designed to last for decades – far longer than is normal with today’s electronic devices. What happens then, when an occupant moves out or transfers ownership of her Smart Environment? This paper outlines the critical challenges required for the safe long-term operation of Smart Environments. How does an occupant identify and decommission all the Things in an environment before she moves out? How does a new occupant discover, identify, validate, and configure all the Things in the environment he adopts? When a person moves from smart home to smart office to smart hotel, how is a new environment vetted for safety and security, how are personal settings migrated, and how are they securely deleted on departure? When the original vendor of a Thing (or the service behind it) disappears, how can that Thing (and its data, and its configuration) be transferred to a new service provider? What interface can enable lay people to manage these complex challenges, and be assured of their privacy, security, and safety? We present a list of key research questions to address these important challenges.
</div>
</div>
</div>
<div id="ref-tc-peters-tr2017">
<p>
<span class="author">Travis Peters</span>. <strong>A Survey of Trustworthy Computing on Mobile & Wearable Systems</strong>. Technical Report TR2017-823, Dartmouth Computer Science, May 2017.
</p>
<div class="resource-container">
<a class="btn btn-primary btn-xs" role="button" href="https://www.traviswpeters.com/papers/peters-trusted-comp-tr2017.pdf">PDF</a><button class="btn btn-primary btn-xs abstract-btn" type="button" data-toggle="collapse">Abstract</button>
<div class="collapse well panel-body abstract-text-container">
Mobile and wearable systems have generated unprecedented interest in recent years, particularly in the domain of mobile health (mHealth) where carried or worn devices are used to collect health-related information about the observed person. Much of the information – whether physiological, behavioral, or social – collected by mHealth systems is sensitive and highly personal; it follows that mHealth systems should, at the very least, be deployed with mechanisms suitable for ensuring confidentiality of the data it collects. Additional properties – such as integrity of the data, source authentication of data, and data freshness – are also desirable to address other security, privacy, and safety issues. Developing systems that are robust against capable adversaries (including physical attacks) is, and has been, an active area of research. While techniques for protecting systems that handle sensitive data are well-known today, many of the solutions in use today are not well suited for mobile and wearable systems, which are typically limited with respect to power, memory, computation, and other capabilities. In this paper we look at prior research on developing trustworthy mobile and wearable systems. To survey this topic we begin by discussing solutions for securing computing systems that are not subject to the type of strict constraints associated with mobile and wearable systems. Next, we present other efforts to design and implement trustworthy mobile and wearable systems. We end with a discussion of future directions.
</div>
</div>
</div>
<div id="ref-hester:amulet">
<p>
Josiah Hester, <span class="author">Travis Peters</span>, Tianlong Yun, Ronald Peterson, Joseph Skinner, Bhargav Golla, Kevin Storer, Steven Hearndon, Kevin Freeman, Sarah Lord, Ryan Halter, David Kotz, and Jacob Sorber. <strong>Amulet: An Energy-Efficient, Multi-Application Wearable Platform</strong>. In <em>Proceedings of the ACM Conference on Embedded Networked Sensor Systems (SenSys)</em>, pages 216–229. ACM Press, November 2016. Acceptance Rate 18%.
</p>
<div class="resource-container">
<a class="btn btn-primary btn-xs" role="button" href="https://www.traviswpeters.com/papers/hester-amulet-sensys2016.pdf">PDF</a><a class="btn btn-primary btn-xs" role="button" href="https://doi.org/10.1145/2994551.2994554">DOI</a><button class="btn btn-primary btn-xs abstract-btn" type="button" data-toggle="collapse">Abstract</button>
<div class="collapse well panel-body abstract-text-container">
Wearable technology enables a range of exciting new applications in health, commerce, and beyond. For many important applications, wearables must have battery life measured in weeks or months, not hours and days as in most current devices. Our vision of wearable platforms aims for long battery life but with the flexibility and security to support multiple applications. To achieve long battery life with a workload comprising apps from multiple developers, these platforms must have robust mechanisms for app isolation and developer tools for optimizing resource usage.We introduce the Amulet Platform for constrained wearable devices, which includes an ultra-low-power hardware architecture and a companion software framework, including a highly efficient event-driven programming model, low-power operating system, and developer tools for profiling ultra-low-power applications at compile time. We present the design and evaluation of our prototype Amulet hardware and software, and show how the framework enables developers to write energy-efficient applications. Our prototype has battery lifetime lasting weeks or even months, depending on the application, and our interactive resource-profiling tool predicts battery lifetime within 6-10% of the measured lifetime.
</div>
</div>
</div>
<div id="ref-hester:amulet-demo">
<p>
Josiah Hester, <span class="author">Travis Peters</span>, Tianlong Yun, Ronald Peterson, Joseph Skinner, Bhargav Golla, Kevin Storer, Steven Hearndon, Sarah Lord, Ryan Halter, David Kotz, and Jacob Sorber. <strong>The Amulet Wearable Platform: Demo Abstract</strong>. In <em>Proceedings of the ACM Conference on Embedded Networked Sensor Systems (SenSys)</em>, pages 290–291. ACM Press, November 2016.
</p>
<div class="resource-container">
<a class="btn btn-primary btn-xs" role="button" href="https://www.traviswpeters.com/papers/hester-amulet-demo-sensys2016.pdf">PDF</a><a class="btn btn-primary btn-xs" role="button" href="https://doi.org/10.1145/2994551.2996527">DOI</a><button class="btn btn-primary btn-xs abstract-btn" type="button" data-toggle="collapse">Abstract</button>
<div class="collapse well panel-body abstract-text-container">
In this demonstration we present the Amulet Platform; a hardware and software platform for developing energy- and resource-efficient applications on multi-application wearable devices. This platform, which includes the Amulet Firmware Toolchain, the Amulet Runtime, the ARP-View graphical tool, and open reference hardware, efficiently protects applications from each other without MMU support, allows developers to interactively explore how their implementation decisions impact battery life without the need for hardware modeling and additional software development, and represents a new approach to developing long-lived wearable applications. We envision the Amulet Platform enabling long-duration experiments on human subjects in a wide variety of studies.
</div>
</div>
</div>
<div id="ref-peters-IntelLabs2016-IoTposter">
<p>
<span class="author">Travis Peters</span>, Srikanth Varadarajan, and Reshma Lal. <strong>Poster: Security in IoT: What is IoT Security, Really?!</strong> <em>Intel Labs Open House</em>, September 2016.
</p>
<div class="resource-container">
<button class="btn btn-primary btn-xs abstract-btn" type="button" data-toggle="collapse">
Abstract
</button>
<div class="collapse well panel-body abstract-text-container">
In this work we conduct a survey of the Internet of Things, primarily focused around identifying security, privacy, and safety concerns in consumer-centric scenarios (e.g., SmartHealthcare, SmartHomes, SmartCars). Our primary goal in this work is to identify gaps in the security and threat models that are being considered today in order to gain insight into what needs to be done in the future to ensure the security of our interconnected things. To begin to try to understand the threats in the IoT we began by first trying to understand the usages, technologies, and standards that are driving the adoption of IoT.
</div>
</div>
</div>
<div id="ref-peters-IntelLabsOH2015-poster-demo">
<p>
<span class="author">Travis Peters</span>, Srikanth Varadarajan, Pradeep Pappachan, and Reshma Lal. <strong>Poster & Demo: Protecting Bluetooth Input from Malware</strong>. <em>Intel Labs Open House</em>, September 2015.
</p>
<div class="resource-container">
<button class="btn btn-primary btn-xs abstract-btn" type="button" data-toggle="collapse">
Abstract
</button>
<div class="collapse well panel-body abstract-text-container">
The role of securing I/O data is generally understood to be a responsibility of a modern OS. This is, however, inherently assuming that we trust the OS and the various drivers that handle I/O data with potentially sensitive information. Of particular interest in I/O data security is the security of input data for authentication such as passwords and PINs, as well as other sensitive information that is entered in popular applications including, but not limited to, addresses, phone numbers, social security numbers, and credit/debit card information. When input data is entered via a Bluetooth Human Interface Device (HID) such as a keyboard, this data is secured over the air, however, upon arriving in the Bluetooth Controller of the host machine, the data is decrypted and passed up through various drivers in the OS before ultimately reaching an application. Trusted I/O (TIO) for Bluetooth devices aims to secure data between a Trusted Application (e.g., an application running in a Trusted Execution Environment (TEE)) and the Bluetooth Controller which receives Bluetooth data over the air. In this document, I will present some of the challenges that must be addressed in implementing TIO for Bluetooth devices, review our plan for a firmware-based approach to cryptographically protecting Bluetooth keyboard input data and our actual Proof of Concept work which (1) implements an interface by which a Trusted Application can program/clear a TIO session key into the Bluetooth Controller, (2) modifies the Bluetooth Controller’s firmware to maintain TIO-related connection information for connected devices, and (3) modifies the firmware to implement L2CAP-level packet parsing to identify packets containing HID Report data and encrypt the data if a TIO session has been enabled for that device. I will close with an overview of remaining challenges and future work.
</div>
</div>
</div>
<div id="ref-peters-IntelLabsIPS2015-poster">
<p>
<span class="author">Travis Peters</span>, Srikanth Varadarajan, Pradeep Pappachan, and Reshma Lal. <strong>Poster: Trusted I/O and Bluetooth Devices</strong>. <em>Intel Labs Intern Poster Show</em>, August 2015.
</p>
<div class="resource-container">
<button class="btn btn-primary btn-xs abstract-btn" type="button" data-toggle="collapse">
Abstract
</button>
<div class="collapse well panel-body abstract-text-container">
The role of securing I/O data is generally understood to be a responsibility of a modern OS. This is, however, inherently assuming that we trust the OS and the various drivers that handle I/O data with potentially sensitive information. Of particular interest in I/O data security is the security of input data for authentication such as passwords and PINs, as well as other sensitive information that is entered in popular applications including, but not limited to, addresses, phone numbers, social security numbers, and credit/debit card information. When input data is entered via a Bluetooth Human Interface Device (HID) such as a keyboard, this data is secured over the air, however, upon arriving in the Bluetooth Controller of the host machine, the data is decrypted and passed up through various drivers in the OS before ultimately reaching an application. Trusted I/O (TIO) for Bluetooth devices aims to secure data between a Trusted Application (e.g., an application running in a Trusted Execution Environment (TEE)) and the Bluetooth Controller which receives Bluetooth data over the air. In this document, I will present some of the challenges that must be addressed in implementing TIO for Bluetooth devices, review our plan for a firmware-based approach to cryptographically protecting Bluetooth keyboard input data and our actual Proof of Concept work which (1) implements an interface by which a Trusted Application can program/clear a TIO session key into the Bluetooth Controller, (2) modifies the Bluetooth Controller’s firmware to maintain TIO-related connection information for connected devices, and (3) modifies the firmware to implement L2CAP-level packet parsing to identify packets containing HID Report data and encrypt the data if a TIO session has been enabled for that device. I will close with an overview of remaining challenges and future work.
</div>
</div>
</div>
<div id="ref-molina-markham:wmmadd">
<p>
Andrés Molina-Markham, Ronald Peterson, Joseph Skinner, Tianlong Yun, Bhargav Golla, Kevin Freeman, <span class="author">Travis Peters</span>, Jacob Sorber, Ryan Halter, and David Kotz. <strong>Amulet: A Secure Architecture for mHealth Applications for Low-Power Wearable Devices</strong>. In <em>Proceedings of the Workshop on Mobile Medical Applications – Design and Development (WMMADD)</em>, pages 16–21. November 2014. Acceptance Rate 57%.
</p>
<div class="resource-container">
<a class="btn btn-primary btn-xs" role="button" href="https://www.traviswpeters.com/papers/molina-markham-wmmadd2014.pdf">PDF</a><a class="btn btn-primary btn-xs" role="button" href="https://doi.org/10.1145/2676431.2676432">DOI</a><button class="btn btn-primary btn-xs abstract-btn" type="button" data-toggle="collapse">Abstract</button>
<div class="collapse well panel-body abstract-text-container">
Interest in using mobile technologies for health-related applications (mHealth) has increased. However, none of the available mobile platforms provide the essential properties that are needed by these applications. An mHealth platform must be (i) secure; (ii) provide high availability; and (iii) allow for the deployment of multiple third-party mHealth applications that share access to an individual’s devices and data. Smartphones may not be able to provide property (ii) because there are activities and situations in which an individual may not be able to carry them (e.g., while in a contact sport). A low-power wearable device can provide higher availability, remaining attached to the user during most activities. Furthermore, some mHealth applications require integrating multiple on-body or near-body devices, some owned by a single individual, but others shared with multiple individuals. In this paper, we propose a secure system architecture for a low-power bracelet that can run multiple applications and manage access to shared resources in a body-area mHealth network. The wearer can install a personalized mix of third-party applications to support the monitoring of multiple medical conditions or wellness goals, with strong security safeguards. Our preliminary implementation and evaluation supports the hypothesis that our approach allows for the implementation of a resource monitor on far less power than would be consumed by a mobile device running Linux or Android. Our preliminary experiments demonstrate that our secure architecture would enable applications to run for several weeks on a small wearable device without recharging.
</div>
</div>
</div>
<div id="ref-emg-peters-tr2014">
<p>
<span class="author">Travis Peters</span>. <strong>An Assessment of Single-Channel EMG Sensing for Gestural Input</strong>. Technical Report TR2015-767, Dartmouth Computer Science, September 2014.
</p>
<div class="resource-container">
<a class="btn btn-primary btn-xs" role="button" href="https://www.traviswpeters.com/papers/peters-emg-tr2014.pdf">PDF</a><button class="btn btn-primary btn-xs abstract-btn" type="button" data-toggle="collapse">Abstract</button>
<div class="collapse well panel-body abstract-text-container">
Wearable devices of all kinds are becoming increasingly popular. One problem that plagues wearable devices, however, is how to interact with them. In this paper we construct a prototype electromyography (EMG) sensing device that captures a single channel of EMG sensor data corresponding to user gestures. We also implement a machine learning pipeline to recognize gestural input received via our prototype sensing device. Our goal is to assess the feasibility of using a BITalino EMG sensor to recognize gestural input on a mobile health (mHealth) wearable device known as Amulet. We conduct three experiments in which we use the EMG sensor to collect gestural input data from (1) the wrist, (2) the forearm, and (3) the bicep. Our results show that a single channel EMG sensor located near the wrist may be a viable approach to reliably recognizing simple gestures without mistaking them for common daily activities such as drinking from a cup, walking, or talking while moving your arms.
</div>
</div>
</div>
<div id="ref-peters-mobisys2014">
<p>
<span class="author">Travis Peters</span> and Puneet Jain. <strong>MobiSys 2014</strong>, <em>IEEE Pervasive Computing</em>, 13(4): 93–96, October 2014.
</p>
<div class="resource-container">
<a class="btn btn-primary btn-xs" role="button" href="https://www.traviswpeters.com/papers/peters-mobisys2014.pdf">PDF</a><a class="btn btn-primary btn-xs" role="button" href="https://doi.org/10.1109/MPRV.2014.69">DOI</a><button class="btn btn-primary btn-xs abstract-btn" type="button" data-toggle="collapse">Abstract</button>
<div class="collapse well panel-body abstract-text-container">
This conference report on MobiSys 2014 covers the keynote by James Landay on balancing design and technology to tackle global grand challenges; highlights selected papers from the various conference sessions on topics ranging from wearable computing to security to localization; and discusses some of the posters and demos.
</div>
</div>
</div>
<div id="ref-computing-jackson-umap2012">
<p>
Chip Jackson, Lucas Bourne, and <span class="author">Travis Peters</span>. <strong>Computing Along the Big Long River</strong>, <em>The UMAP Journal for Undergraduate Mathematics & Research</em>, 33(3): 231–246, Fall 2012.
</p>
<div class="resource-container">
<a class="btn btn-primary btn-xs" role="button" href="https://www.traviswpeters.com/papers/peters-umap2012.pdf">PDF</a><button class="btn btn-primary btn-xs abstract-btn" type="button" data-toggle="collapse">Abstract</button>
<div class="collapse well panel-body abstract-text-container">
We develop a model to schedule trips down the Big Long River. The goal is to optimally plan boat trips of varying duration and propulsion so as to maximize the number of trips over the six-month season. We model the process by which groups travel from campsite to campsite. Subject to the given constraints, our algorithm outputs the optimal daily schedule for each group on the river. By studying the algorithm’s long-term behavior, we can compute a maximum number of trips, which we define as the river’s carrying capacity. We apply our algorithm to a case study of the Grand Canyon, which has many attributes in common with the Big Long River. Finally, we examine the carrying capacity’s sensitivity to changes in the distribution of propulsion methods, distribution of trip duration, and the number of campsites on the river.
</div>
</div>
</div>
</div>
<h1 id="talks-presentations">Talks & Presentations</h1>
<p><strong>[Workshop Talk]</strong> BASTION-SGX: Bluetooth and Architectural Support for Trusted I/O on SGX. Workshop on Hardware and Architectural Support for Security and Privacy (HASP) at the International Symposium on Computer Architecture (ISCA), Los Angeles, California, June 2018.</p>
<p><strong>[Workshop Talk]</strong> Physical Emanations and Potential Applications. Annual Trustworthy Health and Wellness Workshop, University of Illinois at Urbana-Champaign, Champaign, IL, September 2017.</p>
<p><strong>[Invited Talk]</strong> An IoT Survey: Security, Privacy, and Safety in the Future of IoT. Intern Tech Talk Series, Intel Labs, Hillsboro, Oregon, September 2016.</p>
<p><strong>[NSF Research Outreach]</strong> Fitbit Project: Discussing the Fitbit System, Data, and Security & Privacy Awareness. Hanover High School (Statistics Class), Hanover, New Hampshire, May 2015.</p>
<p><strong>[Invited Talk]</strong> Delivering Secure Bluetooth Device Input to a Trusted Execution Environment. Intern Tech Talk Series, Intel Labs, Hillsboro, Oregon, September 2015.</p>
<p><strong>[Poster Presentation]</strong> Security in IoT: What is IoT Security, Really?! Intel Labs Open House, Intel Labs, Hillsboro, Oregon, September 2016. <!-- w/ Srikanth Varadarajan, Reshma Lal --></p>
<p><strong>[Poster Presentation & Demo]</strong> Protecting Bluetooth Input from Malware. Intel Labs Open House, Hillsboro, Oregon, September 2015. <!-- w/ Srikanth Varadarajan, Pradeep Pappachan, Reshma Lal --></p>
<p><strong>[Poster Presentation]</strong> Trusted I/O and Bluetooth Devices Intern Poster Show, Intel Labs, Hillsboro, Oregon, August 2015. <!-- w/ Srikanth Varadarajan, Pradeep Pappachan, Reshma Lal --></p>
<h1 id="technical-skills">Technical Skills</h1>
<p><strong>Programming Languages:</strong> Python, C, Java, Javascript, Matlab, x86 assembly, Bash, Ruby, SQL, , HTML/CSS. <strong>Software Development & Prototyping:</strong> Linux, Android, OSX, iOS; Linux and Android Bluetooth stacks; Raspberry Pi, Arduinos, and other custom platforms (e.g., Amulet); Git, SVN, Perforce; Vagrant, Docker, Chef. <strong>System & Software Inspection & Diagnostics:</strong> software inspection, e.g., GDB, dtrace, strace, ptrace, perf; physical inspection, e.g., oscilloscopes, spectrum analyzers. <strong>Data Collection & Analysis:</strong> Wireshark, GNU Radio, Jupyter, MATLAB. <strong>Wireless and Software Defined Radios (SDRs):</strong> Ubertooth; USRP, LimeSDR; GNU Radio. <strong>Databases & Web Frameworks:</strong> MySQL, MongoDB; Node.js.</p>
<h1 id="awards-honors">Awards & Honors</h1>
<p><strong>Funding Acknowledgements</strong> 2014 - 2018<br />
<em>My research as a PhD student has been conducted under the guidance of my advisor, Dr. David Kotz, and has been funded by two large, multidisciplinary NSF grants: Amulet (<a href="https://amulet-project.org/" class="uri">https://amulet-project.org/</a>), a collaboration between Dartmouth College and Clemson University; and Trustworthy Health and Wellness (<a href="https://thaw.org/" class="uri">https://thaw.org/</a>), a collaboration between Dartmouth College, U. Michigan, UIUC, Johns Hopkins, and Vanderbilt.</em></p>
<p><strong>Best Teaching Assistant Award</strong>, Department of Computer Science, Dartmouth College 2015<br />
<em>An award voted on by all CS faculty at Dartmouth.</em> <!-- awarded @ Computer Science Research Symposium (CSRS) --></p>
<p><strong>Outstanding Graduate Student Teacher</strong>, Dartmouth Center for the Advancement of Learning 2015<br />
<em>An award given annually through DCAL; nominated by students.</em></p>
<p><strong>Graduate Student Teaching Award</strong>, Dartmouth College 2014<br />
<!-- \footnote{An award given to only three graduate students across Dartmouth.}, --> <em>An award given to only three graduate students across Dartmouth.</em></p>
<p><strong>Dartmouth Fellowship</strong>, Dartmouth College 2013, 2014<br />
<em>Computer Science fellowship.</em></p>
<p><strong>Outstanding Winner, Frank Giordano Award</strong>, Contest in Mathematical Modeling 2012<br />
<em>Less than 3% of teams (10 out of more than 3,600) are selected as Outstanding Winners of the contest.</em> <!-- *The Mathematical Contest in Modeling challenges students to clarify, analyze, and propose}\\
*solutions to open-ended problems. The contest included over 3,600 teams from 17 countries}\\
*around the world. Only 10 teams are selected as Outstanding Winners of the contest.}--></p>
<p><strong>Oscar Edwin Olson Scholarship</strong>, Western Washington University 2012<br />
<em>Awarded for academic excellence in Computer Science.</em></p>
<p><strong>Kaiser Borsari Scholarship and Giusti Scholarship</strong>, Western Washington University 2011<br />
<em>Awarded for academic excellence in Computer Science.</em></p>
<h1 id="leadership-volunteer-experience">Leadership & Volunteer Experience</h1>
<p><strong>Topo Athletic Ambassador</strong>, Topo Athletic 2018 - present</p>
<p><strong>Co-Webmaster</strong>, Upper Valley Running Club 2018 - present</p>
<p><strong>Couch-to-5k Volunteer Coach</strong>, Upper Valley Running Club 2016 - present</p>
<p><strong>Lead Sunday School Teacher</strong>, Christ Redeemer Church 2014 - present</p>
<p><strong>Assistant Track Coach</strong>, Hanover High School 2016 - 2017</p>
<p><strong>Free Geek Build Volunteer</strong>, Free Geek (Portland, OR) 2016</p>
<p><strong>Organizer & Facilitator</strong>, Graduate Student TA Orientation 2015</p>
<p><strong>Graduate Student Council Rep.</strong>, Dartmouth College Computer Science 2013 - 2015</p>
<p><strong>Graduate Student Web Team</strong>, Dartmouth College Computer Science 2014 - 2015</p>
<p><strong>Lead Teacher & RK Coordinator</strong>, Redeemer Kids at Redeemer Church 2011 - 2013</p>
<p><strong>Vice President of Business & Operations</strong>, Associated Students of WWU 2011 - 2012<br />
- <strong>Chair</strong>, AS Management Council & AS Facilities & Services Council<br />
- <strong>Vice-Chair</strong>, AS Board of Directors & AS Budget Committee<br />
- <strong>Member</strong>, Academic Honesty Board</p>
<p><strong>Big Brother</strong>, Big Brothers Big Sisters of Whatcom County 2010 - 2011</p>
<p><strong>WWU Cross Country and Track & Field</strong>, Western Washington University 2008 - 2012</p>
<h1 id="references">References</h1>
<!-- Available upon request. -->
<p><strong>David Kotz</strong> (PhD Advisor)<br />
Professor<br />
Department of Computer Science<br />
Dartmouth College<br />
Email: <a href="mailto:[email protected]">[email protected]</a></p>
<p><strong>Thomas Cormen</strong> (Teaching Mentor)<br />
Professor<br />
Department of Computer Science<br />
Dartmouth College<br />
Email: <a href="mailto:[email protected]">[email protected]</a></p>
<p><strong>Chris Bailey-Kellogg</strong> (Teaching Mentor)<br />
Professor<br />
Department of Computer Science<br />
Dartmouth College<br />
Email: <a href="mailto:[email protected]">[email protected]</a></p>
<p><strong>Reshma Lal</strong> (Manager)<br />
Security Research Scientist<br />
Intel Security & Privacy Research Labs<br />
Intel Labs<br />
Email: <a href="mailto:[email protected]">[email protected]</a></p>
<!-- jQuery (necessary for Bootstrap's JavaScript plugins) -->
<script src="https://code.jquery.com/jquery-1.12.4.min.js" integrity="sha384-nvAa0+6Qg9clwYCGGPpDQLVpLNn0fRaROjHqs13t4Ggj3Ez50XnGQqc/r8MhnRDZ" crossorigin="anonymous"></script>
<!-- Include all compiled plugins (below), or include individual files as needed -->
<script src="https://stackpath.bootstrapcdn.com/bootstrap/3.4.1/js/bootstrap.min.js" integrity="sha384-aJ21OjlMXNL5UyIl/XNwTMqvzeRMZH2w8c5cRVpzpU8Y5bApTppSuUkhZXN0VxHd" crossorigin="anonymous"></script>
<!-- some custom JS to help with the rendering/animations -->
<script type="text/javascript" src="bib.js"></script>
</body>
</html>