The evolution of the 'master' branch

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: The evolution of the 'master' branch
From: rsalz@xxxxxxxxxx (Salz, Rich)
Date: Tue, 10 Feb 2015 22:00:35 +0000
In-reply-to: <37FA559B-F877-42C5-9166-12DE5B320FC7@pobox.com>
References: <20150203220231.GA12587@openssl.org> <54D23F42.3060203@wisemo.com> <453ad2042e6c43e5897f1689e230883f@ustx2ex-dag1mb2.msg.corp.akamai.com> <54D4E5D3.6090808@wisemo.com> <37FA559B-F877-42C5-9166-12DE5B320FC7@pobox.com>

> Is there any plan to make libcrypto go completely opaque, such that _only_
> the APIs exposed in libssl will be available?

Absolutely not.

Thanks for asking!

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

References:
- The evolution of the 'master' branch
  - From: Rich Salz
- The evolution of the 'master' branch
  - From: Jakob Bohm
- The evolution of the 'master' branch
  - From: Salz, Rich
- The evolution of the 'master' branch
  - From: Jakob Bohm
- The evolution of the 'master' branch
  - From: Tom Francis

Prev by Date: [openssl-dev] Proposed cipher changes for post-1.0.2
Next by Date: The evolution of the 'master' branch
Previous by thread: The evolution of the 'master' branch
Next by thread: The evolution of the 'master' branch
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Security] [Bugtraq] [Linux] [Linux OMAP] [Linux MIPS] [ECOS] [Asterisk Internet PBX] [Linux API]

Powered by Linux