safe_bro 0.1.0 → 0.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: c4906ce3efcad72d1fe0d51afcd111672739b28a722a4745bf4b012b8f611fda
-  data.tar.gz: ba294a2ffd0d1434f2dd99463a6f858fc8ea1be017dcd0a17217d199726d4a6c
+  metadata.gz: f0dca904398773a1fab1742da124c6d90dce7448ab51f97a6affa2df152aba70
+  data.tar.gz: 3e391dd86e14a9f8dfad4d47ef1887eb3ea8bbb5b9665282f598a64ed2939483
 SHA512:
-  metadata.gz: 38c8fc9959f76ccc547f8a7aa661a36270a1239a1a53c6c8c75816e88516fd46dc1e33ac9f5b0d373102de83479c801eec7de54f42acc0631985655bebabbe39
-  data.tar.gz: e1d93726cfd4dde7107fd6f0abbc1cd08144203657178e04dfa139d313720909373bd57f71b1bff5507fa25f5d6d3dca31b105a0e1ffd38b722abf37b7c29557
+  metadata.gz: 7cc7293d600d9796449ae72f4a96510e7aec5ea563c559a43e25b62e64d41fc66801ccc8c6f619b0bb3ffd16f2f3d2d86de56502086219c123d3e44e21485d0e
+  data.tar.gz: 616249c036d3a46b7b9866ae7c35937cc27840c6b3e80d3a3356c54d52eeb9b4378d983828889a5b04d7f50a9336d9dff622e7666cade051bc97d449098bee1a

data/README.md

@@ -200,6 +200,19 @@ Not covered: `rails dbconsole`, a raw `psql`/`mysql` session, other process mana
 - `rails runner` sessions can be recorded; notifications are `ActiveSupport::Notifications`.
 - Not carried over: Pry and other console support (SafeBro hooks IRB only).
 
+## Switching from console1984 + audits1984
+
+1. **Don't run both.** Both hook IRB at startup and would record every command twice, so remove `console1984` and
+   `audits1984` from the Gemfile when you add `safe_bro`, and remove their mount (`mount Audits1984::Engine`) and
+   initializer settings. `bin/rails g bro_hub:install --remove-direct-mounts` only retires SafeBro/EnvBro mounts, so do this by hand.
+2. **Existing audit data stays where it is.** SafeBro uses its own `safe_bro_*` tables and doesn't read console1984's
+   (`console1984_*`, `audits1984_*`). Nothing is migrated: the old sessions can't be reviewed in SafeBro's UI.
+   Keep the old tables (read them from a console or SQL) for as long as you need the history, then drop them in a migration.
+   Sessions already encrypted with Active Record Encryption need those keys for as long as you keep them.
+3. Map the settings: console1984's `protected_environments` → the same option in SafeBro
+   in `config/initializers/safe_bro.rb`; audits1984's auditor check → `config.can_audit`.
+4. Set `CONSOLE_USER` for everyone (see above), then run `bin/rails g safe_bro:install` and `bin/rails db:migrate`.
+
 ## Development
 
 ```sh

data/lib/generators/safe_bro/install/install_generator.rb

@@ -13,7 +13,7 @@ module SafeBro
       desc "Sets up the BroHub dashboard (the review UI lives in it), adds the SafeBro initializer and copies the migrations."
 
       def copy_initializer
-        copy_file "safe_bro.rb", "config/initializers/safe_bro.rb"
+        copy_config_once "safe_bro.rb", "config/initializers/safe_bro.rb"
       end
 
       def copy_migrations

data/lib/safe_bro/version.rb

@@ -1,3 +1,3 @@
 module SafeBro
-  VERSION = "0.1.0"
+  VERSION = "0.1.1"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: safe_bro
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.1.1
 platform: ruby
 authors:
 - Ruby Dev SRL
@@ -43,14 +43,14 @@ dependencies:
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '0.1'
+        version: 0.1.1
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '0.1'
+        version: 0.1.1
 description: Records Rails console sessions (who, why, what), asks for a justification
   before sensitive data is touched, blocks tampering and risky methods, and ships
   a mountable engine where auditors review sessions. One gem instead of console1984