1 / 31

The Aerospace Clinic 2002

The Aerospace Clinic 2002. Team Members Nick Hertl (Project Manager) Will Berriel Richard Fujiyama Chip Bradford Faculty Advisor Professor Michael Erlinger Aerospace Liaisons Joseph Betser, PhD Rayford Sims. Overview. Background Information Tunnel Technical Approach

manthey
Download Presentation

The Aerospace Clinic 2002

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Aerospace Clinic 2002 Team Members Nick Hertl (Project Manager) Will Berriel Richard Fujiyama Chip Bradford Faculty Advisor Professor Michael Erlinger Aerospace Liaisons Joseph Betser, PhD Rayford Sims

  2. Overview • Background Information • Tunnel • Technical Approach • Completed work • Tunnel Demo • Future work • Questions

  3. Background • TCP/IP • Network Security • Firewalls • BEEP • IDXP

  4. TCP/IP • Main protocols used over the Internet • Provides reliable, full-duplex, peer-to-peer communication • Most current application protocols use this directly: HTTP (web), SMTP (email), etc. • Multiple connections to the same machine are handled using ports

  5. Network Security • Only authorized users should be able to access private networks • Some data and services should only be available internally • Firewalls are used in most corporations to restrict access to network resources

  6. Firewalls • Set of rules to restrict network traffic • Can filter by any combination of: • Source IP • Destination IP • Port • Protocol • Rule sets are usually static

  7. BEEP • Blocks Extensible Exchange Protocol • General framework for the rapid creation of application-level protocols • Requires an underlying transport protocol • Provides a message framing mechanism and many common service "profiles" • Profiles provide transparent addition of properties to a connection (i.e. security)

  8. Existing BEEP Profiles • SSL/TLS • SASL • IDXP • Others that don’t apply to our system. • Tunnel (soon… :-)

  9. IDXP • Intrusion Detection eXchange Protocol • Standard communication of Intrusion Detection messages (IDMEF) • Firewall must not block authorized messages

  10. Tunnel • General purpose proxy routing BEEP profile • Our focus is Tunnel for IDXP message

  11. Tunnel • Uses XML messages to establish a tunnel: <tunnel fqdn=“host1.example.com" port="10289"> <tunnel /> </tunnel> • Other XML attributes allow routing by IP address, service, or potentially user defined extensions.

  12. Alternatives to Tunnel • SSH • Application not intended for this purpose • VPN • Long lived • Invasive to client • IPsec • Requires kernel modification • Few organizations use this

  13. Completed Work • Evaluated Tunnel Specification • Chose BEEP Implementations • Implemented • No-Hop Tunnel • One-Hop Tunnel • Some interoperability testing

  14. Fall Schedule

  15. Tunnel Evaluation • No standard way to extend the DTD. • Previously no IPv6 support in the DTD. • Possibility for loops with misconfigured servers. • No way to specify a Time-To-Live when using a dynamic route, ie: connecting to a service rather than a host.

  16. Beep Implementations: • JAVA: • PermaBEEP 0.8 (Better API) • Beepcore–java 0.9.07 (TLS support) • C • Roadrunner 0.9 (More fully implemented) • Beepcore–C 0.2 (Abandoned)

  17. No-Hop Tunnel • Profile and application can successfully open a tunnel to a host with no firewall in between.

  18. One-Hop Tunnel

  19. Let’s take a look.

  20. Tunnel host1.example.com host2.example.com proxy.example.com Transport Connect Usually TCP

  21. Tunnel host1.example.com host2.example.com proxy.example.com Transport Connect BEEP Greeting Advertise services (Tunnel, maybe others)

  22. Tunnel host1.example.com host2.example.com proxy.example.com Transport Connect BEEP Greeting Start Tunnel <tunnel fqdn="host2.example.com" port="10288"> <tunnel /> </tunnel>

  23. Tunnel host1.example.com host2.example.com proxy.example.com Transport Connect BEEP Greeting Start Tunnel Transport Connect Usually TCP

  24. Tunnel host1.example.com host2.example.com proxy.example.com Transport Connect BEEP Greeting Start Tunnel Transport Connect BEEP Greeting Advertise services (Tunnel, maybe others)

  25. Tunnel host1.example.com host2.example.com proxy.example.com Transport Connect BEEP Greeting Start Tunnel Transport Connect BEEP Greeting Start Tunnel <tunnel />

  26. Tunnel host1.example.com host2.example.com proxy.example.com Transport Connect BEEP Greeting Start Tunnel Transport Connect BEEP Greeting Start Tunnel OK <ok />

  27. Tunnel host1.example.com host2.example.com proxy.example.com Transport Connect BEEP Greeting Start Tunnel Transport Connect BEEP Greeting Start Tunnel OK OK <ok /> proxy now transparently forwards messages

  28. Tunnel host1.example.com host2.example.com proxy.example.com Transport Connect BEEP Greeting Start Tunnel Transport Connect BEEP Greeting Start Tunnel OK OK BEEP Greeting Advertise services (proxy now invisible)

  29. Future Work • Firewall daemon (Enforce Security Policy) • Multi–Hop Proxying • More interoperability testing between C and Java implementations. • Support for java server as proxy? • Bug squashing • Final report

  30. Spring Schedule

  31. Questions?

More Related