Server Security Meeting - Friday, 3 March

Gelareh_Taban · February 27, 2017, 2:22pm

Hi all,

Next meeting is this Friday. (ping me if you want me to send you a
calendar invite)

See you then!
Gelareh

···

-------------------------------

Friday, March 3, 2017

Austin 11:00 am - 12 pm CST
San Jose 9:00 am - 10 am PST
London 5:00 pm - 6pm GMT

Agenda
Some of the items on the agenda will be, discussing and finalizing:
- Proposal to send to Swift Evolution:

github.com

swift-server/security/blob/master/README.md

# Status

:warning: This project is unmaintained experimental legacy code. It has been obsoleted by [swift-nio-ssl](https://github.com/apple/swift-nio-ssl) which contains the recommended TLS API of the [Swift Server Work Group](https://swift.org/server/).

It remains here for historical interest only.

# Introduction

Currently there is no standard Swift security library that is compatible with all of the current Swift platforms (Apple and Linux). This lack of standardization has resulted in multiple projects which either write their own Swift security functionality or use their security library of choice (be it OpenSSL, LibreSSL, etc.).  This is not desirable because it can lead to:
- incompatibility of dependencies if more that one security package is needed by different modules (a project cannot have both OpenSSL and LibreSSL in its dependency graph)
- insecurity (using an unpatched or insecure library)
- unmaintainability (using non-standard or non-native libraries)
- more complex code (using different APIs for each platform).

This proposal outlines a set of design goals as well as an approach to be adopted by the Swift Server APIs project's Security Working Group for the creation of a single Swift security component that is cross-compatible on Apple and Linux (Ubuntu) platforms. The Security APIs will consist of both lower level crypto APIs (including hashing, symmetric and asymmetric crypto) as well as higher level APIs (including key/certificate management and secure communication such as TLS).

# Motivation

Having a consistent development experience for Swift across Apple and Linux helps drive higher developer productivity, safer code as well as better reuse of Swift assets/libraries across these platforms.

This file has been truncated. show original

- Who and how to get involved in development
- Process of Server Security API proposals, development, testing and
release
- Our next steps
- Planning of regular upcoming meetings

Please update the initial agenda if you have other items to discuss:

Access Information
Where: https://meetings.webex.com/collabs/#/meetings/joinbynumber
Meeting number: 192 728 101

Joe_Smith · February 27, 2017, 9:21pm

Awesome! I'll try to swing by as well, though I'm mostly coming at it from the backend services/command-line tools than web development.

···

On Feb 27, 2017, at 6:22 AM, Gelareh Taban via swift-server-dev <swift-server-dev@swift.org> wrote:

Hi all,

Next meeting is this Friday. (ping me if you want me to send you a calendar invite)

See you then!
Gelareh

-------------------------------

Friday, March 3, 2017

Austin 11:00 am - 12 pm CST
San Jose 9:00 am - 10 am PST
London 5:00 pm - 6pm GMT

Agenda
Some of the items on the agenda will be, discussing and finalizing:
- Proposal to send to Swift Evolution: https://github.com/swift-server/security/blob/master/README.md
- Who and how to get involved in development
- Process of Server Security API proposals, development, testing and release
- Our next steps
- Planning of regular upcoming meetings

Please update the initial agenda if you have other items to discuss:
Swift Server APIs: Security stream meeting 4 - Google Docs <Swift Server APIs: Security stream meeting 4 - Google Docs;

Access Information
Where: https://meetings.webex.com/collabs/#/meetings/joinbynumber
Meeting number: 192 728 101

_______________________________________________
swift-server-dev mailing list
swift-server-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-server-dev