Search

Jeffrey M Homme

from Stanwood, WA
Age ~57
Get Report
Also known as:
Jeffrey Martin Homme, Jeff M Homme, Jeffrey M Hommie, Jeff Omme
Related to:
Hoien TeresaSandra Sowells, 60Lois J DuncanKandis Hoien, 39Maria Ramos, 64
Connected to:
Jennifer E Homme, 29Justin K Homme, 35Sandy K Homme, 72Tamara L Homme, 40Amy J Hommel, 67Charity A Hommel, 46Holly F Hommel, 51Lisa A Hommel, 56Matthew Hommel, 43Richard D Hommel, 78

Jeffrey Homme Phones & Addresses

  • Stanwood, WA
  • 16653 46Th St, Redmond, WA 98052 (425) 922-5205
  • Gig Harbor, WA
  • Bellevue, WA
  • Kiona, WA

Work

Company: Hks Mar 2013 Address: Dallas/Fort Worth Area Position: Forum

Education

School / High School: Loyola University of Chicago 2009 to 2009

Industries

Architecture & Planning

Resumes

Resumes

Jeffrey Homme Photo 1

Forum At Hks

View page
Position:
Forum at HKS
Location:
Dallas, Texas
Industry:
Architecture & Planning
Work:
HKS - Dallas/Fort Worth Area since Mar 2013
Forum
RTKL - Dallas/Fort Worth Area Dec 2010 - Mar 2013
Project Coordinator
MKTG INC Aug 2007 - Jan 2011
Captain Morgan
Media Star Promotions - Greater Chicago Area Sep 2009 - Mar 2010
Promotional Marketing Specialist
Education:
Loyola University of Chicago 2009 - 2009
Southern Illinois University, Carbondale 2009
Bachelors, Healthcare Management, Marketing Minor Manhattan Prep

Publications

Us Patents

Security Mechanism For Developmental Operating Systems

View page
US Patent:
20130067238, Mar 14, 2013
Filed:
Sep 12, 2011
Appl. No.:
13/230708
Inventors:
Jeffrey M. Homme - Redmond WA, US
Mariusz H. Jakubowski - Bellevue WA, US
Jeremy S. Russell - Bellevue WA, US
Scott A. Kupec - Kirkland WA, US
Dragos C. Sambotin - Issaquah WA, US
Assignee:
Microsoft Corporation - Redmond WA
International Classification:
G06F 21/00
US Classification:
713189
Abstract:
A security technique to reduce the risk of unauthorized release of a software object. The technique allows identification of an individual responsible for the unauthorized release by marking each object with information, which acts as a fingerprint from which a person manipulating the object in a development environment can be identified. The development environment may be configured to quickly and automatically mark the object whenever a manipulation that may precede an unauthorized release occurs. To prevent circumventing the security technique, the object may be configured to enforce a requirement for a valid fingerprint such that the object is disabled if the fingerprint is removed or altered. Despite the marking, personally identifiable information is not revealed because the fingerprint is generated through a one-way cryptographic function performed on identifying information.
Control profile
Jeffrey M Homme from Stanwood, WA, age ~57 Get Report