Jason Scott Mcmullan

US Patent:

20060136904, Jun 22, 2006

Filed:

Dec 22, 2004

Appl. No.:

11/019961

Inventors:

Lawrence Weidman - Pittsburgh PA, US
Manas Saksena - Pittsburgh PA, US
Jason McMullan - Pittsburgh PA, US

International Classification:

G06F 9/44

US Classification:

717172000

Abstract:

Systems and methods for generating a plurality of different software builds from a common base code and different combinations of other components are described in the context of a collaborative framework in which multiple parties maintain a shareable base of software used for generating such builds. Systems and methods for generating a plurality of different hardware build designs from a common collection of hardware elements and different combinations of other hardware components are also described.

US Patent:

20200139932, May 7, 2020

Filed:

Nov 26, 2018

Appl. No.:

16/199832

Inventors:

- San Francisco CA, US
Jason Scott McMullan - Pittsburgh PA, US
Matthew James Harris - Pittsburgh PA, US

International Classification:

B60R 25/30
H04L 9/08
H04W 12/00
H04L 9/32
G05D 1/00
B60R 25/24
B60R 25/01

Abstract:

Systems and methods are directed to detecting tampering with a secured area of an autonomous vehicle. In one example, a computing system performs operations including generating a first key pair comprising a first private key and a first public key as part of a vehicle registration process; providing the first public key to one or more remote computing systems; determining whether a reset event occurred at a vehicle; in response to determining that the reset event occurred, discarding the first key pair and generating a second key pair comprising a second private key and a second public key; receiving a status query from one of the one or more remote computing systems; generating a response to the status query, the response being signed using either the first private key or the second private key; and providing the response to the one of the one or more remote computing systems.

US Patent:

20140201728, Jul 17, 2014

Filed:

Jan 14, 2013

Appl. No.:

13/741310

Inventors:

ROELOF NICO DU TOIT - PORTERSVILLE PA, US
NOAH ZEV ROBBIN - SWISSVALE PA, US
JASON SCOTT MCMULLAN - PITTSBURGH PA, US

Assignee:

NETRONOME SYSTEMS, INC. - SANTA CLARA CA

International Classification:

G06F 9/445

US Classification:

717171, 717168

Abstract:

Software update information is communicated to a network appliance either across a network or from a local memory device. The software update information includes kernel data, application data, or indicator data. The network appliance includes a first storage device, a second storage device, an operating memory, a central processing unit (CPU), and a network adapter. First and second storage devices are persistent storage devices. In a first example, both kernel data and application data are updated in the network appliance in response to receiving the software update information. In a second example, only the kernel data is updated in the network appliance in response to receiving the software update information. In a third example, only the application data is updated in the network appliance in response to receiving the software update information. Indicator data included in the software update information determines the data to be updated in the network appliance.

US Patent:

20140201734, Jul 17, 2014

Filed:

Jan 15, 2013

Appl. No.:

13/742311

Inventors:

Jason Scott McMullan - Pittsburgh PA, US
Trevor William Patrie - Pittsburgh PA, US
Peter Liudmilov Djalaliev - Pittsburgh PA, US
Roelof Nico du Toit - Portersville PA, US

Assignee:

Netronome Systems, Inc. - Santa Clara CA

International Classification:

G06F 9/455

US Classification:

718 1

Abstract:

A device has physical network interface port through which a user can monitor and configure the device. A backend process and a virtual machine (VM) execute on a host operating system (OS). A front end user interface process executes on the VM, and is therefore compartmentalized in the VM. There is no front end user interface executing on the host OS outside the VM. The only management access channel into the device is via a first communication path through the physical network interface port, to the VM, up the VM's stack, and to the front end process. If the backend process is to be instructed to take an action, then the front end process forwards an application layer instruction to the backend process via a second communication path. The instruction passes down the VM stack, across a virtual secure network link, up the host stack, and to the backend process.