ARC Questions Version 4.6 ------------------------------------------------------------------------ 1. What specifically is the proposal that we are reviewing? - What is the technical content of the project? An amendment to PSARC/2002/557 (SSL Support for NL7C). This project supercedes PSARC/2002/557, and offers in-kernel SSL proxy in general, and not limited to HTTP, nor content cacheable by NL7C only. The internal SSL protocol code, and the configuration and administration model are taken unchanged from PSARC/2002/557 see Overview section in greyhound_amendment.pdf - Is this a new product, or a change to a pre-existing one? If it is a change, would you consider it a "major", "minor", or "micro" change? See the Release Taxonomy in: Mincro/Patch. - If your project is an evolution of a previous project, what changed from one version to another? Change to an approved but never delivered project. - What is the motivation for it, in general as well as specific terms? (Note that not everyone on the ARC will be an expert in the area.) See Background, Motivation, and Changes from PSARC/2002/557 section of greyhound_amendment.pdf - What are the expected benefits for Sun? see same paragraph above. - By what criteria will you judge its success? SunONE Webserver with the kernel SSL proxy performs 20% better thab without. 2. Describe how your project changes the user experience, upon installation and during normal operation. - What does the user perceive when the system is upgraded from a previous release? N/A 3. What is its plan? - What is its current status? Has a design review been done? Are there multiple delivery phases? design and code review done. project has been under tuning for a few months now, and being used to prepare Ontario's Specweb2005 announcement. 4. Are there related projects in Sun? - If so, what is the proposal's relationship to their work? Which not-yet- delivered Sun (or non-Sun) projects (libraries, hardware, etc.) does this project depend upon? What other projects, if any, depend on this one? Chihuahua (PSARC/2005/596). This projects lays the foundation for a long term SSL offloading solution from Sun. - Are you updating, copying or changing functional areas maintained by other groups? How are you coordinating and communicating with them? Do they "approve" of what you propose? If not, please explain the areas of disagreement. Hooks in sockfs/stream head and TCP are added, following the advice of the their responsible engineers, after code review. They approve. 5. How is the project delivered into the system? - Identify packages, directories, libraries, databases, etc. this in unchanged from PSARC/2002/557 6. Describe the project's hardware platform dependencies. - Explain any reasons why it would not work on both SPARC and Intel? no 7. System administration - How will the project's deliverables be installed and (re)configured? - How will the project's deliverables be uninstalled? - Does it use inetd to start itself? - Does it need installation within any global system tables? - Does it use a naming service such as NIS, NIS+ or LDAP? - What are its on-going maintenance requirements (e.g. Keeping global tables up to date, trimming files)? - How does this project's administrative mechanisms fit into Sun's system administration strategies? E.g., how does it fit under the Solaris Management Console (SMC) and Web-Based Enterprise Management (WBEM), how does it make use of roles, authorizations and rights profiles? Additionally, how does it provide for administrative audit in support of the Solaris BSM configuration? - What tunable parameters are exported? Can they be changed without rebooting the system? Examples include, but are not limited to, entries in /etc/system and ndd(8) parameters. What ranges are appropriate for each tunable? What are the commitment levels associated with each tunable (these are interfaces)? this in unchanged from PSARC/2002/557 8. Reliability, Availability, Serviceability (RAS) - Does the project make any material improvement to RAS? - How can users/administrators diagnose failures or determine operational state? (For example, how could a user tell the difference between a failure and very slow performance?) - What are the project's effects on boot time requirements? - How does the project handle dynamic reconfiguration (DR) events? - What mechanisms are provided for continuous availability of service? - Does the project call panic()? Explain why these panics cannot be avoided. - How are significant administrative or error conditions transmitted? SNMP traps? Email notification? - How does the project deal with failure and recovery? - Does it ever require reboot? If so, explain why this situation cannot be avoided. - How does your project deal with network failures (including partition and re- integration)? How do you handle the failure of hardware that your project depends on? - Can it save/restore or checkpoint and recover? - Can its files be corrupted by failures? Does it clean up any locks/files after crashes? this in unchanged from PSARC/2002/557 9. Observability - Does the project export status, either via observable output (e.g., netstat) or via internal data structures (kstats)? - How would a user or administrator tell that this subsystem is or is not behaving as anticipated? - What statistics does the subsystem export, and by what mechanism? - What state information is logged? - In principle, would it be possible for a program to tune the activity of your project? this in unchanged from PSARC/2002/557 10. What are the security implications of this project? - What security issues do you address in your project? - The Solaris BSM configuration carries a Common Criteria (CC) Controlled Access Protection Profile (CAPP) -- Orange Book C2 -- and a Role Based Access Control Protection Profile (RBAC) -- rating, does the addition of your project effect this rating? E.g., does it introduce interfaces that make access or privilege decisions that are not audited, does it introduce removable media support that is not managed by the allocate subsystem, does it provide administration mechanisms that are not audited? - Is system or subsystem security compromised in any way if your project's configuration files are corrupt or missing? - Please justify the introduction of any (all) new setuid executables. - Include a thorough description of the security assumptions, capabilities and any potential risks (possible attack points) being introduced by your project. A separate Security Questionnaire http://sac.sfbay/cgi-bin/bp.cgi?NAME=Security.bp is provided for more detailed guidance on the necessary information. Cases are encouraged to fill out and include the Security questionnaire (leveraging references to existing documentation) in the case materials. Projects must highlight information for the following important areas: - What features are newly visible on the network and how are they protected from exploitation (e.g. unauthorized access, eavesdropping) - If the project makes decisions about which users, hosts, services, ... are allowed to access resources it manages, how is the requestor's identity determined and what data is used to determine if the access granted. Also how this data is protected from tampering. - What privileges beyond what a common user (e.g. 'noaccess') can perform does this project require and why those are necessary. - What parts of the project are active upon default install and how it can be turned off. this in mainly unchanged from PSARC/2002/557 It has a security emprovement over it, by addressing the security concern from the requirement of cleartext caching of sensitive content. See Background, Motivation, and Changes from PSARC/2002/557 section of greyhound_amendment.pdf 11. What is its UNIX operational environment: - Which Solaris release(s) does it run on? - Environment variables? Exit status? Signals issued? Signals caught? (See signal(3HEAD).) - Device drivers directly used (e.g. /dev/audio)? .rc/defaults or other resource/configuration files or databases? - Does it use any "hidden" (filename begins with ".") or temp files? - Does it use any locking files? - Command line or calling syntax: What options are supported? (please include man pages if available) Does it conform to getopt() parsing requirements? - Is there support for standard forms, e.g. "-display" for X programs? Are these propagated to sub-environments? - What shared libraries does it use? (Hint: if you have code use "ldd" and "dump -Lv")? - Identify and justify the requirement for any static libraries. - Does it depend on kernel features not provided in your packages and not in the default kernel (e.g. Berkeley compatibility package, /usr/ccs, /usr/ucblib, optional kernel loadable modules)? - Is your project 64-bit clean/ready? If not, are there any architectural reasons why it would not work in a 64-bit environment? Does it interoperate with 64-bit versions? - Does the project depend on particular versions of supporting software (especially Java virtual machines)? If so, do you deliver a private copy? What happens if a conflicting or incompatible version is already or subsequently installed on the system? - Is the project internationalized and localized? - Is the project compatible with IPV6 interfaces and addresses? this in unchanged from PSARC/2002/557 12. What is its window/desktop operational environment? - Is it ICCCM compliant (ICCCM is the standard protocol for interacting with window managers)? - X properties: Which ones does it depend on? Which ones does it export, and what are their types? - Describe your project's support for User Interface facilities including Help, Undo, Cut/Paste, Drag and Drop, Props, Find, Stop? - How do you respond to property change notification and ICCCM client messages (e.g. Do you respond to "save workspace")? - Which window-system toolkit/desktop does your project depend on? - Can it execute remotely? Is the user aware that the tool is executing remotely? Does it matter? - Which X extensions does it use (e.g. SHM, DGA, Multi-Buffering? (Hint: use "xdpyinfo") - How does it use colormap entries? Can you share them? - Does it handle 24-bit operation? N/A 13. What interfaces does your project import and export? - Please provide a table of imported and exported interfaces, including stability levels. Pay close attention to the classification of these interfaces in the Interface Taxonomy -- e.g., "Standard," "Stable," and "Evolving;" see: http://sac.sfbay/cgi-bin/bp.cgi?NAME=interface_taxonomy.bp Use the following format: Interfaces Exported Interface Classification Comments so_kssl_endpt_type Project private fileds in the sonode_t so_kssl_ent private socket structure so_kssl_ctx tcp_kssl_endpt_type Project private fileds in the tcp_t tcp_kssl_ent private TCP structure tcp_kssl_ctx T_SSL_PROXY_BIND_REQ Project Private private TPI primitives T_SSL_PROXY_CONN_IND kssl_check_proxy() Project kernel SSL API entry point kssl_find_fallback() Private private to this project kssl_input() Consolidation kernel SSL API entry points kssl_handle_record() Private intended to continue to be kssl_build_record() used by Chihuahua so_tail Consolidation extension to the SO_TAIL Private stroptions(9S) sd_rputdatafunct Consolidation Hooks in the stream head sd_wputdatafunct Private structure MSGCOOKED Consolidation message b_flag Private - Exported public library APIs and ABIs Protocols (public or private) Drag and Drop ToolTalk Cut/Paste - Other interfaces - What other applications should it interoperate with? How will it do so? - Is it "pipeable"? How does it use stdin, stdout, stderr? - Explain the significant file formats, names, syntax, and semantics. - Is there a public namespace? (Can third parties create names in your namespace?) How is this administered? - Are the externally visible interfaces documented clearly enough for a non-Sun client to use them successfully? 14. What are its other significant internal interfaces inter-subsystem and inter-invocation)? - Protocols (public or private) - Private ToolTalk usage - Files - Other - Are the interfaces re-entrant? 15. Is the interface extensible? How will the interface evolve? - How is versioning handled? - What was the commitment level of the previous version? - Can this version co-exist with existing standards and with earlier and later versions or with alternative implementations (perhaps by other vendors)? - What are the clients over which a change should be managed? - How is transition to a new version to be accomplished? What are the consequences to ISV's and their customers? this in unchanged from PSARC/2002/557 16. How do the interfaces adapt to a changing world? - What is its relationship with (or difficulties with) multimedia? 3D desktops? Nomadic computers? Storage-less clients? A networked file system model (i.e., a network-wide file manager)? this in unchanged from PSARC/2002/557 17. Interoperability - If applicable, explain your project's interoperability with the other major implementations in the industry. In particular, does it interoperate with Microsoft's implementation, if one exists? - What would be different about installing your project in a heterogeneous site instead of a homogeneous one (such as Sun)? - Does your project assume that a Solaris-based system must be in control of the primary administrative node? this in unchanged from PSARC/2002/557 18. Performance - How will the project contribute (positively or negatively) to "system load" and "perceived performance"? - What are the performance goals of the project? How were they evaluated? What is the test or reference platform? - Does the application pause for significant amounts of time? Can the user interact with the application while it is performing long-duration tasks? - What is your project's MT model? How does it use threads internally? How does it expect its client to use threads? If it uses callbacks, can the called entity create a thread and recursively call back? - What is the impact on overall system performance? What is the average working set of this component? How much of this is shared/sharable by other apps? - Does this application "wake up" periodically? How often and under what conditions? What is the working set associated with this behavior? - Will it require large files/databases (for example, new fonts)? - Do files, databases or heap space tend to grow with time/load? What mechanisms does the user have to use to control this? What happens to performance/system load? 20% performance boost of Web perforemance measured by Specweb2005 Banking benchmark. 19. Please identify any issues that you would like the ARC to address. - Interface classification, deviations from standards, architectural conflicts, release constraints... - Are there issues or related projects that the ARC should advise the appropriate steering committees? 20. Appendices to include - greyhound_amendment.pdf