Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Mission statement and target audience #5

Closed
tiran opened this issue Aug 7, 2013 · 5 comments
Closed

Mission statement and target audience #5

tiran opened this issue Aug 7, 2013 · 5 comments
Labels
administrative
Milestone
Fourth Release

Comments

@tiran
Copy link
Contributor

tiran commented Aug 7, 2013

As discussed on twitter let's add a mission statement to cryptography.

It should explain:

  • reason for a new Python crypto package
  • purpose
  • target audience
  • target platforms (Python 2.7+, 3.2+, PyPy)
  • supported OS (Linux, *BSD, Windows, ???)
  • supported architectures (X86, X86_64, X32, ARMv6+ ?)
  • supported compilers (GCC 4.x, clang, MSVC)
  • C standard (C89 or partial C99, optional GNU extension?)
@alex
Copy link
Member

alex commented Aug 7, 2013

#6 begins to address this.

@hynek hynek mentioned this issue Aug 11, 2013
Closed
alex added a commit that referenced this issue Aug 11, 2013
@alex
Better describe why this library exists. Refs #5
9f3468d
hynek added a commit that referenced this issue Aug 11, 2013
@hynek
Merge pull request #38 from alex/why-cryptography
f0091d0 
Better describe why this library exists. Refs #5
@hynek
Copy link
Contributor

hynek commented Aug 11, 2013

point 1 is covered by #38, purpose/scope is still open, but the platforms derive themselves from CFFI so I’m not sure we should explain them. At least not until we’ll be forced to polluted the repo with C files.

Maybe make it a check list like @alex in #28 ?

@reaperhulk reaperhulk added this to the Third Release milestone Feb 18, 2014
@Ayrx
Copy link
Contributor

Ayrx commented Apr 26, 2014

Just to kickstart this again since it's targeted for the 4th release, what is missing before we can close this?

@reaperhulk
Copy link
Member

We mostly have this covered. Architectures (x86_64 is all we test on at the moment), compilers (we don't try to precisely define them although gcc 4.x, clang, MSVC is what we test), and C standard (we're basically constrained to C89 due to MSVC) are not spelled out in the docs.

@alex
Copy link
Member

alex commented Apr 28, 2014

I think what we've documented so far is probably fine.

@alex alex closed this as completed Apr 28, 2014
collisdigital added a commit to collisdigital/cryptography that referenced this issue Apr 29, 2016
@collisdigital @reaperhulk
Update Java verifier to skip past test vector file header if present (p…
d09c510 
…yca#5)

* Update Java verifier to skip past test vector file header if present

* Fix tabs vs. space whitespace
@alyukhan alyukhan mentioned this issue May 12, 2016
Closed
alex pushed a commit that referenced this issue Jun 2, 2016
@reaperhulk @alex
add RSA OAEP SHA2 vectors via custom vector creation (#2829)
3079299 
* add RSA OAEP SHA2 vectors via custom vector creation

* update the docs

* retab

* remove sha2 oaep support (it will be added again in another PR)

* add header to each vector file

* Add Java 8 Bouncy Castle based verification of RSA-OAEP SHA-2 test vectors (#4)

* Update Java verifier to skip past test vector file header if present (#5)

* Update Java verifier to skip past test vector file header if present

* Fix tabs vs. space whitespace

* generate sha1 oaep permutations as well + verify support in java

* address review feedback
joerichter-stash pushed a commit to kiwigrid/cryptography that referenced this issue Nov 15, 2017
@exarkun
Merge pull request pyca#5 from pyca/pypy-fixes
9efd9c6 
Some changes to make the test suite green on PyPy

This adds some missing initialization that is actually necessary to work on PyPy (whereas it is only necessary to work on CPython sometimes).  It also adjusts some garbage collector interactions in one test to satisfy PyPy's somewhat different garbage collection requirements.
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
administrative
Milestone
Fourth Release
Development

No branches or pull requests
5 participants
@alex @hynek @reaperhulk @tiran @Ayrx