From sac-owner Fri Jan 18 00:53:40 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m0I8rdlC023729 for ; Fri, 18 Jan 2008 00:53:40 -0800 (PST) Received: from sunmail5.uk.sun.com (localhost [127.0.0.1]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m0I8rcNx017805 for ; Fri, 18 Jan 2008 08:53:38 GMT Received: (from noaccess@localhost) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/Submit) id m0I8rciN017804 for one-pager-not-2b-used-directly; Fri, 18 Jan 2008 08:53:38 GMT Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m0I8rGrp017659 for <@sunmail2sca.sfbay.sun.com:one-pager@sun.com>; Fri, 18 Jan 2008 08:53:38 GMT Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JUU006030PAZB00@nwk-avmta-1.sfbay.Sun.COM> for one-pager@sun.com (ORCPT one-pager@sun.com); Fri, 18 Jan 2008 00:53:34 -0800 (PST) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JUU00HMK0P9WJ50@nwk-avmta-1.sfbay.Sun.COM> for one-pager@sun.com (ORCPT one-pager@sun.com); Fri, 18 Jan 2008 00:53:34 -0800 (PST) Received: from fe-apac-03.sun.com (fe-apac-03.sun.com [192.18.19.174] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m0I8rWFl003469 for ; Fri, 18 Jan 2008 08:53:33 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0JUU00E010GMU100@mail-apac.sun.com> (original mail from Mayuresh.Nirhali@Sun.COM) for one-pager@sun.com (ORCPT one-pager@sun.com); Fri, 18 Jan 2008 16:53:32 +0800 (SGT) Received: from [129.158.227.167] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JUU00KPU0P8SR30@mail-apac.sun.com> for one-pager@sun.com (ORCPT one-pager@sun.com); Fri, 18 Jan 2008 16:53:32 +0800 (SGT) Date: Fri, 18 Jan 2008 14:21:09 +0530 From: Mayuresh Nirhali Subject: [2008/041]Dante Sender: Mayuresh.Nirhali@sun.com To: one-pager@sun.com Message-id: <4790687D.4030608@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 User-Agent: Thunderbird 2.0.0.0 (X11/20070423) Status: RO Content-Length: 5104 Template Version: @(#)onepager.txt 1.35 07/11/07 SMI Copyright 2007 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: Dante: A Socks server and client implementation 1.2. Name of Document Author/Supplier: Mayuresh Nirhali 1.3. Date of This Document: 01/16/2008 1.3.1. Date this project was conceived: This is a third party software to be integrated into Solaris. The latest version is 1.1.19. 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: Solaris 1.4.2. The ARC(s) you expect to review your project: LSARC 1.4.3. The Director/VP who is "Sponsoring" this project: Chris.Armes@Sun.COM 1.4.4. The name of your business unit: Solaris - RPE 1.5. Email Aliases: 1.5.1. Responsible Manager: Lukas.Rovensky@Sun.COM 1.5.2. Responsible Engineer: Mayuresh.Nirhali@Sun.COM 1.5.3. Marketing Manager: 1.5.4. Interest List: 2. Project Summary 2.1. Project Description: Dante is a circuit-level firewall/proxy that can be used to provide convenient and secure network connectivity to a wide range of hosts while requiring only the server Dante runs on to have external network connectivity. 2.2. Risks and Assumptions: Dante is a third party Socks server and client implementation. There are no risks and assumptions. 3. Business Summary 3.1. Problem Area: Dante provides convinient and secure network connectivity from behind a firewall using Socks protocol. 3.2. Market/Requester: OpenSolaris Community 3.3. Business Justification: Integration of Dante will allow the Solaris host to act a Socks server and client. Such socks implementation has been missing from the Solaris OS. 3.4. Competitive Analysis: The competitor in this regard are really the Operating Systems that include such functionality today. 3.5. Opportunity Window/Exposure: The third party product is ready to be integrated. 3.6. How will you know when you are done?: The product is ready to be integrated. 4. Technical Description: 4.1. Details: http://www.inet.no/dante/ Dante is a circuit-level firewall/proxy that can be used to provide convenient and secure network connectivity to a wide range of hosts while requiring only the server Dante runs on to have external network connectivity. Once installed, Dante can in most cases be made transparent to the clients while offering detailed access control and logging facilities to the server administrator. 4.2. Bug/RFE Number(s): 4.3. In Scope: 4.4. Out of Scope: 4.5. Interfaces: This integration will not modify or delete any interfaces. It will add to binaries, one for the server (/usr/sbin/sockd) and another for the client (/usr/bin/socksify). For the server, /etc/sockd.conf will be used as a configuration file, and for the client, /etc/socks.conf will be used for configuration. 4.6. Doc Impact: This integration will rightly add man entries. None of the existing man entries will be touched. Some of the new man entries are as below, /usr/man/man5/sockd.conf.5 /usr/man/man5/socks.conf.5 /usr/man/man8/sockd.8 4.7. Admin/Config Impact: N/A 4.8. HA Impact: N/A 4.9. I18N/L10N Impact: None 4.10. Packaging & Delivery: Both server and client will be installed with only one package. SUNWdante Dante - A Socks client and server implementation for UNIX 4.11. Security Impact: Socks Server and client will depend on the port configured in the respective configuration file for network connectivity. 4.12. Dependencies: bash-3.00# ldd libsocks.so libpam.so.1 => /lib/libpam.so.1 libsocket.so.1 => /lib/libsocket.so.1 libnsl.so.1 => /lib/libnsl.so.1 libresolv.so.2 => /lib/libresolv.so.2 libc.so.1 => /lib/libc.so.1 libmp.so.2 => /lib/libmp.so.2 libmd.so.1 => /lib/libmd.so.1 libscf.so.1 => /lib/libscf.so.1 libuutil.so.1 => /lib/libuutil.so.1 libgen.so.1 => /lib/libgen.so.1 libm.so.2 => /lib/libm.so.2 5. Reference Documents: http://www.inet.no/dante/ 6. Resources and Schedule: 6.1. Projected Availability: Integration targeted for Indiana release. 6.2. Cost of Effort: Minimum. One resource for integration in SFW consolidation. 6.3. Cost of Capital Resources: None 6.4. Product Approval Committee requested information: 6.4.1. Consolidation or Component Name: SFW 6.4.3. Type of CPT Review and Approval expected: FASTTRACK 6.4.4. Project Boundary Conditions: None 6.4.5. Is this a necessary project for OEM agreements: No 6.4.6. Notes: 6.4.7. Target RTI Date/Release: Indiana Release 6.4.8. Target Code Design Review Date: 6.4.9. Update approval addition: 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open 6.6.1. Rationale: 7. Prototype Availability: 7.1. Prototype Availability: N/A 7.2. Prototype Cost: N/A