asherah 0.9.1 → 0.10.0

metadata

@@ -1,66 +1,76 @@
 --- !ruby/object:Gem::Specification
 name: asherah
 version: !ruby/object:Gem::Version
-  version: 0.9.1
+  version: 0.10.0
 platform: ruby
 authors:
-- GoDaddy
+- Jay Gowdy
+- Bo Thompson
+- Michael Micco
+- Dalibor Nasevic
 autorequire:
-bindir: exe
+bindir: bin
 cert_chain: []
-date: 2026-04-23 00:00:00.000000000 Z
+date: 2026-06-05 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
-  name: cobhan
+  name: ffi
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.2.0
+        version: '1.15'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.2.0
-description: |
-  Asherah is an application-layer encryption SDK that provides advanced
-  encryption features and defense in depth against compromise.
-email:
-- oss@godaddy.com
+        version: '1.15'
+- !ruby/object:Gem::Dependency
+  name: logger
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.6'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.6'
+description: Asherah application-layer encryption for Ruby with automatic key rotation,
+  powered by the native Rust implementation.
+email: oss@godaddy.com
 executables: []
 extensions:
 - ext/asherah/extconf.rb
 extra_rdoc_files: []
 files:
-- ".env.secrets.example"
-- ".rspec"
-- ".rubocop.yml"
-- ".ruby-version"
-- CHANGELOG.md
-- CODE_OF_CONDUCT.md
-- CONTRIBUTING.md
-- Gemfile
-- LICENSE.txt
+- NATIVE_VERSION
 - README.md
-- Rakefile
-- SECURITY.md
-- asherah.gemspec
-- ext/asherah/checksums.yml
+- ext/asherah/asherah.c
 - ext/asherah/extconf.rb
-- ext/asherah/native_file.rb
+- ext/asherah/fetch_native.rb
 - lib/asherah.rb
 - lib/asherah/config.rb
 - lib/asherah/error.rb
+- lib/asherah/hooks.rb
+- lib/asherah/native.rb
+- lib/asherah/session.rb
+- lib/asherah/session_factory.rb
 - lib/asherah/version.rb
-homepage: https://github.com/godaddy/asherah-ruby
+homepage: https://github.com/godaddy/asherah-ffi
 licenses:
-- MIT
+- Apache-2.0
 metadata:
-  homepage_uri: https://github.com/godaddy/asherah-ruby
-  source_code_uri: https://github.com/godaddy/asherah-ruby
-  changelog_uri: https://github.com/godaddy/asherah-ruby/blob/main/CHANGELOG.md
+  homepage_uri: https://github.com/godaddy/asherah-ffi
+  source_code_uri: https://github.com/godaddy/asherah-ffi
+  github_repo: https://github.com/godaddy/asherah-ffi
+  changelog_uri: https://github.com/godaddy/asherah-ffi/releases
+  bug_tracker_uri: https://github.com/godaddy/asherah-ffi/issues
   rubygems_mfa_required: 'true'
 post_install_message:
 rdoc_options: []
@@ -70,15 +80,15 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: 2.7.0
+      version: '3.0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.4.19
+rubygems_version: 3.5.22
 signing_key:
 specification_version: 4
-summary: Application Layer Encryption SDK
+summary: Asherah application-layer encryption for Ruby with automatic key rotation.
 test_files: []

data/.env.secrets.example

@@ -1,9 +0,0 @@
-# Example secrets file for KMS integration tests
-# Copy this file to .env.secrets and fill in actual values
-# 
-# IMPORTANT: Never commit .env.secrets to version control
-# The .env.secrets file is already in .gitignore
-
-# AWS KMS Key ARN for integration tests (optional)
-# Only needed if running spec/kms_spec.rb
-# KMS_KEY_ARN=arn:aws:kms:us-west-2:123456789012:key/12345678-1234-1234-1234-123456789012

data/.rspec

@@ -1,3 +0,0 @@
---format documentation
---color
---require spec_helper

data/.rubocop.yml

@@ -1,112 +0,0 @@
-AllCops:
-  TargetRubyVersion: 2.7
-  NewCops: enable
-  SuggestExtensions: false
-  Exclude:
-    - 'vendor/**/*' # Github Actions
-    - 'tmp/**/*'
-
-Layout/LineLength:
-  Max: 120
-
-# Metrics cops with reasonable limits
-Metrics/BlockLength:
-  Max: 25
-  Exclude:
-    - 'spec/**/*'
-    - '*.gemspec'
-    - 'Rakefile'
-
-Metrics/MethodLength:
-  Max: 15
-  Exclude:
-    - 'spec/**/*'
-    - 'tasks/**/*'
-
-Metrics/AbcSize:
-  Max: 20
-  Exclude:
-    - 'spec/**/*'
-    - 'tasks/**/*'
-
-Metrics/CyclomaticComplexity:
-  Max: 10
-  Exclude:
-    - 'spec/**/*'
-
-Metrics/PerceivedComplexity:
-  Max: 10
-  Exclude:
-    - 'spec/**/*'
-
-Metrics/ClassLength:
-  Max: 150
-  Exclude:
-    - 'spec/**/*'
-
-Metrics/ModuleLength:
-  Max: 150
-  Exclude:
-    - 'spec/**/*'
-
-# Style cops that were disabled but should be enabled
-Style/WordArray:
-  MinSize: 3
-  EnforcedStyle: brackets
-
-Style/SymbolArray:
-  MinSize: 3
-  EnforcedStyle: brackets
-
-Style/MultilineBlockChain:
-  Enabled: true
-  Exclude:
-    - 'spec/**/*'
-
-Style/BlockDelimiters:
-  EnforcedStyle: semantic
-  FunctionalMethods:
-    - let
-    - let!
-    - subject
-    - before
-    - after
-  Exclude:
-    - 'asherah.gemspec'
-    - 'ext/asherah/native_file.rb'
-
-Style/GuardClause:
-  MinBodyLength: 3
-  Exclude:
-    - 'ext/asherah/native_file.rb'
-
-# Naming cop adjustment
-Naming/AccessorMethodName:
-  Exclude:
-    - 'lib/asherah.rb' # set_env is intentionally named
-
-# Documentation cops
-Style/Documentation:
-  Enabled: true
-  Exclude:
-    - 'spec/**/*'
-    - 'features/**/*'
-
-Style/DocumentationMethod:
-  Enabled: false # YARD comments are optional
-
-Style/EmptyClassDefinition:
-  Enabled: false
-
-# Additional cops for code quality
-Lint/UnusedMethodArgument:
-  Enabled: true
-
-Lint/UnusedBlockArgument:
-  Enabled: true
-
-Security/Eval:
-  Enabled: true
-
-Security/JSONLoad:
-  Enabled: true

data/.ruby-version

@@ -1 +0,0 @@
-3.2.2

data/CHANGELOG.md

@@ -1,135 +0,0 @@
-## [Unreleased]
-
-## [0.9.1] - 2026-04-23
-
-- Upgrade to use asherah-ffi v0.6.90
-
-## [0.9.0] - 2026-03-20
-
-- Replace asherah-cobhan with asherah-ffi v0.6.44
-- Remove null_data_check configuration option
-
-## [0.8.2] - 2026-03-09
-
-- Upgrade to use asherah-cobhan v0.5.3
-- Add null_data_check configuration option
-
-## [0.8.1] - 2026-03-05
-
-- Upgrade to use asherah-cobhan v0.5.1
-- Fix buffer undersize from float truncation in estimate_buffer
-
-## [0.8.0] - 2026-03-04
-
-- Upgrade to use asherah-cobhan v0.5.0
-- Expose disable_zero_copy config option to disable zero-copy FFI input buffers
-
-## [0.7.0] - 2025-08-15
-
-- Fix memory leak risks in buffer management
-- Fix inconsistent NotInitialized error handling across all methods
-- Fix overly permissive RuboCop configuration
-- Add Dependabot configuration for automated dependency updates
-- Update dependencies and Github actions
-- Update Go version to 1.24 for cross-language tests
-
-## [0.6.0] - 2025-03-19
-
-- Upgrade to use asherah-cobhan v0.4.35
-- Requires minimum GLIBC 2.32 version
-
-## [0.5.2] - 2024-01-15
-
-- Upgrade to use asherah-cobhan v0.4.32
-
-## [0.5.1] - 2023-10-25
-
-- Add `sql_metastore_db_type` config option to support PostgresSQL adapter for Asherah
-- Upgrade to use asherah-cobhan v0.4.31
-
-## [0.5.0] - 2023-10-16
-
-- Upgrade to use asherah-cobhan v0.4.30
-- Expose `test-debug-static` kms type and `test-debug-memory` metastore type to skip warnings in tests
-- Check initialized flag on setup/shutdown and raise appropriate errors
-
-## [0.4.10] - 2023-08-10
-
-- Upgrade to use asherah-cobhan v0.4.25
-
-## [0.4.9] - 2023-07-05
-
-- Upgrade to use asherah-cobhan v0.4.24
-
-## [0.4.8] - 2023-06-06
-
-- Upgrade to use asherah-cobhan v0.4.23
-
-## [0.4.7] - 2023-04-20
-
-- Upgrade to use asherah-cobhan v0.4.22
-- Change detault ruby version to 3.2.2
-
-## [0.4.6] - 2023-03-17
-
-- Upgrade to use asherah-cobhan v0.4.20
-- Change detault ruby version to 3.2
-- Add ruby 3.2 to build matrix
-- Remove ruby 2.5 and 2.6 from build matrix
-
-## [0.4.5] - 2022-10-31
-
-- Upgrade to use asherah-cobhan v0.4.18
-
-## [0.4.4] - 2022-09-14
-
-- Upgrade to use asherah-cobhan v0.4.17
-
-## [0.4.3] - 2022-08-31
-
-- Upgrade to use asherah-cobhan v0.4.16
-
-## [0.4.2] - 2022-07-25
-
-- Upgrade to use asherah-cobhan v0.4.15
-- Add `set_env` method to set environment variables for Asherah
-
-## [0.4.1] - 2022-03-25
-
-- Build and release platform gems
-
-## [0.4.0] - 2022-03-25
-
-- Download native file during gem install and verify checksum
-- Upgrade to use asherah-cobhan v0.4.11
-
-## [0.3.0] - 2022-03-22
-
-- Free up cobhan buffers after encrypt/decrypt to prevent growing heap memory
-- Use local `estimate_buffer` calculation instead of FFI call
-- Upgrade to use asherah-cobhan v0.4.3
-
-## [0.2.0] - 2022-03-21
-
-- Implement versioning for asherah-cobhan binaries
-- Upgrade to use asherah-cobhan v0.3.1
-- Add BadConfig error and expose error codes
-- Remove DRR methods and use JSON exclusively
-- Cross language testing using Asherah Go
-
-## [0.1.0] - 2022-03-14
-
-- First official release
-
-## [0.1.0.beta2] - 2022-03-14
-
-- Add smoke tests for native gems
-- Change to use `SetupJson` instead of `Setup`
-- Update config options to make them consistent with Asherah Go
-- Add `shutdown`
-- Add `encrypt_to_json` and `decrypt_from_json`
-- Add coverage report
-
-## [0.1.0.beta1] - 2022-03-07
-
-- Initial proof of concept

data/CODE_OF_CONDUCT.md

@@ -1,77 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, sex characteristics, gender identity and expression,
-level of experience, education, socio-economic status, nationality, personal
-appearance, race, religion, or sexual identity and orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
-  advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies within all project spaces, and it also applies when
-an individual is representing the project or its community in public spaces.
-Examples of representing a project or community include using an official
-project e-mail address, posting via an official social media account, or acting
-as an appointed representative at an online or offline event. Representation of
-a project may be further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at oss@godaddy.com. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
-
-[homepage]: https://www.contributor-covenant.org
-
-For answers to common questions about this code of conduct, see
-https://www.contributor-covenant.org/faq
-

data/CONTRIBUTING.md

@@ -1,118 +0,0 @@
-# Contributing
-
-Everyone is welcome to contribute to GoDaddy's Open Source Software.
-Contributing doesn’t just mean submitting pull requests. To get involved,
-you can report or triage bugs, and participate in discussions on the
-evolution of each project.
-
-No matter how you want to get involved, we ask that you first learn what’s
-expected of anyone who participates in the project by reading the Contribution
-Guidelines and our [Code of Conduct][coc].
-
-## Answering Questions
-
-One of the most important and immediate ways you can support this project is
-to answer questions on [Github][issues]. Whether you’re
-helping a newcomer understand a feature or troubleshooting an edge case with a
-seasoned developer, your knowledge and experience with a programming language
-can go a long way to help others.
-
-## Reporting Bugs
-
-**Do not report potential security vulnerabilities here. Refer to
-[SECURITY.md](./SECURITY.md) for more details about the process of reporting
-security vulnerabilities.**
-
-Before submitting a ticket, please search our [Issue Tracker][issues] to make
-sure it does not already exist and have a simple replication of the behavior. If
-the issue is isolated to one of the dependencies of this project, please create
-a Github issue in that project. All dependencies should be open source software
-and can be found on Github.
-
-Submit a ticket for your issue, assuming one does not already exist:
-
-- Create it on the project's [issue Tracker][issues].
-- Clearly describe the issue by following the template layout
-  - Make sure to include steps to reproduce the bug.
-  - A reproducible (unit) test could be helpful in solving the bug.
-  - Describe the environment that (re)produced the problem.
-
-## Triaging bugs or contributing code
-
-If you're triaging a bug, first make sure that you can reproduce it. Once a bug
-can be reproduced, reduce it to the smallest amount of code possible. Reasoning
-about a sample or unit test that reproduces a bug in just a few lines of code
-is easier than reasoning about a longer sample.
-
-From a practical perspective, contributions are as simple as:
-
-1. Fork and clone the repo, [see Github's instructions if you need help.][fork]
-1. Create a branch for your PR with `git checkout -b pr/your-branch-name`
-1. Make changes on the branch of your forked repository.
-1. When committing, reference your issue (if present) and include a note about
-  the fix.
-1. Please also add/update unit tests for your changes.
-1. Push the changes to your fork and submit a pull request to the 'main
-   development branch' branch of the projects' repository.
-
-If you are interested in making a large change and feel unsure about its overall
-effect, start with opening an Issue in the project's [Issue Tracker][issues]
-with a high-level proposal and discuss it with the core contributors through
-Github comments. After reaching a consensus with core
-contributors about the change, discuss the best way to go about implementing it.
-
-> Tip: Keep your main branch pointing at the original repository and make
-> pull requests from branches on your fork. To do this, run:
->
->   ```sh
-> git remote add upstream https://github.com/godaddy/asherah-ruby.git
-> git fetch upstream
-> git branch --set-upstream-to=upstream/main main
->   ```
->
-> This will add the original repository as a "remote" called "upstream," Then
-> fetch the git information from that remote, then set your local main
-> branch to use the upstream main branch whenever you run git pull. Then you
-> can make all of your pull request branches based on this main branch.
-> Whenever you want to update your version of main, do a regular git pull.
-
-## Code Review
-
-Any open source project relies heavily on code review to improve software
-quality. All significant changes, by all developers, must be reviewed before
-they are committed to the repository. Code reviews are conducted on GitHub
-through comments on pull requests or commits. The developer responsible for a
-code change is also responsible for making all necessary review-related changes.
-
-Sometimes code reviews will take longer than you would hope for, especially for
-larger features. Here are some accepted ways to speed up review times for your
-patches:
-
-- Review other people’s changes. If you help out, others will more likely be
-willing to do the same for you.
-- Split your change into multiple smaller changes. The smaller your change,
-the higher the probability that somebody will take a quick look at it.
-
-**Note that anyone is welcome to review and give feedback on a change, but only
-people with commit access to the repository can approve it.**
-
-## Attribution of Changes
-
-When contributors submit a change to this project, after that change is
-approved, other developers with commit access may commit it for the author. When
-doing so, it is important to retain correct attribution of the contribution.
-Generally speaking, Git handles attribution automatically.
-
-## Code Style and Documentation
-
-Ensure that your contribution follows the standards set by the project's style
-guide with respect to patterns, naming, documentation and testing.
-
-# Additional Resources
-
-- [General GitHub Documentation](https://help.github.com/)
-- [GitHub Pull Request documentation](https://help.github.com/send-pull-requests/)
-
-[issues]: https://github.com/godaddy/asherah-ruby/issues/
-[coc]: ./CODE_OF_CONDUCT.md
-[fork]: https://help.github.com/en/articles/fork-a-repo

data/Gemfile

@@ -1,14 +0,0 @@
-# frozen_string_literal: true
-
-source 'https://rubygems.org'
-
-# Specify your gem's dependencies in asherah.gemspec
-gemspec
-
-gem 'cucumber', '~> 9.2.1'
-gem 'dotenv', '~> 2.8.1'
-gem 'rake', '~> 13.0'
-gem 'rspec', '~> 3.13.1'
-gem 'rubocop', '~> 1.7'
-gem 'simplecov', '~> 0.22.0'
-gem 'simplecov-console', '~> 0.9.1'

data/LICENSE.txt

@@ -1,21 +0,0 @@
-The MIT License (MIT)
-
-Copyright (c) 2022 GoDaddy Operating Company, LLC.
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.

data/Rakefile

@@ -1,29 +0,0 @@
-# frozen_string_literal: true
-
-require 'bundler/gem_tasks'
-require 'rspec/core/rake_task'
-
-RSpec::Core::RakeTask.new(:spec)
-
-require 'rubocop/rake_task'
-
-RuboCop::RakeTask.new
-
-desc 'Download the binary for the current platform'
-task :download do
-  tmp_dir = 'tmp'
-  FileUtils.mkdir_p(tmp_dir)
-  FileUtils.cd(tmp_dir, verbose: true) do
-    system('ruby ../ext/asherah/extconf.rb')
-  end
-end
-
-task default: [:spec, :rubocop]
-task spec: :download
-
-desc 'Print current version'
-task :version do
-  puts Asherah::VERSION
-end
-
-Rake.add_rakelib 'tasks'

data/SECURITY.md

@@ -1,19 +0,0 @@
-# Reporting Security Issues
-
-We take security very seriously at GoDaddy. We appreciate your efforts to
-responsibly disclose your findings, and will make every effort to acknowledge
-your contributions.
-
-## Where should I report security issues?
-
-In order to give the community time to respond and upgrade, we strongly urge you
-report all security issues privately.
-
-To report a security issue in one of our Open Source projects email us directly
-at **oss@godaddy.com** and include the word "SECURITY" in the subject line.
-
-This mail is delivered to our Open Source Security team.
-
-After the initial reply to your report, the team will keep you informed of the
-progress being made towards a fix and announcement, and may ask for additional
-information or guidance.