Initial commit

Previous commits contained sensitive data (all of my text messages). It
was useful to have this for testing and to be able to see what the
output looked like between commits. This is no longer necessary (I have
made realistic but fake data), so to avoid pushing anything that could
be used to retrieve my commits, I'm restarting the commit history.

.editorconfig

@@ -0,0 +1,19 @@
+root = true
+
+[*]
+indent_style = tab
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true
+
+# Markdown is visually shown, so there are different rules
+[*.md]
+indent_style = space
+indent_size = 2
+trim_trailing_whitespace = false
+
+# YAML hates tabs
+[*.yaml]
+indent_style = space
+indent_size = 2

.gitattributes

@@ -0,0 +1,4 @@
+*.backup linguist-generated
+*.prototext linguist-generated
+*.sqlite linguist-generated
+*.xml linguist-generated

.github/workflows/check.yaml

@@ -0,0 +1,27 @@
+name: check
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    branches:
+      - main
+
+jobs:
+  build:
+    name: Build
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out code
+        uses: actions/checkout@v3
+      - name: Set up Go
+        uses: actions/setup-go@v3
+        with:
+          go-version-file: go.mod
+      - name: golangci-lint
+        uses: golangci/golangci-lint-action@v3
+        with:
+          version: latest
+      - name: Test
+        run: go test ./...

.github/workflows/release.yaml

@@ -0,0 +1,41 @@
+name: release
+
+on:
+  push:
+    tags:
+      - "*"
+
+permissions:
+  contents: write
+
+jobs:
+  goreleaser:
+    runs-on: ubuntu-20.04
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v3
+        with:
+          fetch-depth: 0
+      - name: Set up Go
+        uses: actions/setup-go@v3
+        with:
+          go-version-file: go.mod
+      - name: Cross-compilation support
+        run: |
+          # First, set things up for Apple. OSXCross will be used, which needs libssl1.0-dev
+          mkdir ../../osxcross
+          git clone https://github.com/plentico/osxcross-target.git ../../osxcross/target
+          echo 'deb http://security.ubuntu.com/ubuntu bionic-security main' | sudo tee -a /etc/apt/sources.list
+          sudo apt update
+          sudo apt-cache policy libssl1.0-dev
+          # Finally, install libssl1.0-dev, plus MinGW for Windows
+          sudo apt install libssl1.0-dev gcc-multilib gcc-mingw-w64
+      - name: GoReleaser
+        uses: goreleaser/goreleaser-action@v3
+        with:
+          distribution: goreleaser
+          version: latest
+          args: release --rm-dist -f .goreleaser.yaml
+        env:
+          GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
+          HOMEBREW_GITHUB_TOKEN: ${{secrets.HOMEBREW_ACCESS_TOKEN}}

.gitignore

@@ -0,0 +1,14 @@
+# Don't check in the binary
+signal-to-sms
+
+# Try to avoid allowing users to commit any secrets (even phone numbers or backup passwords) inadvertently
+.vscode/launch.json
+*.backup*
+*.xml
+*.sqlite
+*.prototext
+restored/
+backups/
+
+# Allow testdata though! These are cleaned up, and don't have personal info
+!internal/testdata/**

.goreleaser.yaml

@@ -0,0 +1,75 @@
+before:
+  hooks:
+    - go mod download
+builds:
+  - id: apple-silicon
+    goos:
+      - darwin
+    goarch:
+      - arm64
+    env:
+      - CGO_ENABLED=1
+      - CC=/home/runner/work/osxcross/target/bin/oa64-clang
+      - CXX=/home/runner/work/osxcross/target/bin/oa64-clang++
+    flags:
+      - --tags=darwin
+    mod_timestamp: "{{ .CommitTimestamp }}"
+  - id: apple-x64
+    goos:
+      - darwin
+    goarch:
+      - amd64
+    env:
+      - CGO_ENABLED=1
+      - CC=/home/runner/work/osxcross/target/bin/o64-clang
+      - CXX=/home/runner/work/osxcross/target/bin/o64-clang++
+    flags:
+      - --tags=darwin
+    mod_timestamp: "{{ .CommitTimestamp }}"
+  - id: linux-x64
+    goos:
+      - linux
+    goarch:
+      - amd64
+    env:
+      - CGO_ENABLED=1
+    flags:
+      - --tags=linux
+    mod_timestamp: "{{ .CommitTimestamp }}"
+  - id: windows-x64
+    goos:
+      - windows
+    goarch:
+      - amd64
+    env:
+      - CGO_ENABLED=1
+      - CXX=x86_64-w64-mingw32-g++
+      - CC=x86_64-w64-mingw32-gcc
+    mod_timestamp: "{{ .CommitTimestamp }}"
+archives:
+  - name_template: '{{ .ProjectName }}-{{ .Version }}-{{ .Os }}-{{ .Arch }}{{ with .Arm }}v{{ . }}{{ end }}{{ with .Mips }}-{{ . }}{{ end }}{{ if not (eq .Amd64 "v1") }}{{ .Amd64 }}{{ end }}'
+    replacements:
+      darwin: macOS
+      amd64: x64
+    format_overrides:
+      - goos: windows
+        format: zip
+release:
+  prerelease: auto
+brews:
+  - tap:
+      owner: jamescostian
+      name: homebrew-tap
+      token: "{{ .Env.HOMEBREW_GITHUB_TOKEN }}"
+    commit_author:
+      name: James Costian
+      email: [email protected]
+    commit_msg_template: "Update {{ .ProjectName }} formula to {{ .Tag }}"
+    folder: Formula
+    homepage: "https://github.com/jamescostian/signal-to-sms"
+    description: Decrypt and convert Signal for Android backups so they can be restored as SMSes that can be moved to iMessage on iPhones. NOT AFFILIATED WITH OR OFFICIALLY BLESSED BY SIGNAL.
+    license: GPL-3.0-only
+    dependencies:
+      - name: sqlite
+    test: system "#{bin}/signal-to-sms -v"
+    install: bin.install "signal-to-sms"

.vscode/extensions.json

@@ -0,0 +1,7 @@
+{
+	"recommendations": [
+		"golang.go",
+		"editorconfig.editorconfig",
+		"zxh404.vscode-proto3"
+	]
+}

.vscode/settings.json

@@ -0,0 +1,7 @@
+{
+	"go.testFlags": ["-v", "-tags=deterministic_output"],
+	"go.testTimeout": "3s",
+	"protoc": {
+		"options": ["--proto_path=utils/proto/signal"]
+	}
+}

CODE_OF_CONDUCT.md

@@ -0,0 +1,136 @@
+# Contributor Covenant Code of Conduct
+
+## Contribution licensing
+
+When submitting a contribution to this codebase (e.g. through a PR), you should license the work you are submitting under the GPLv3 so that it can be accepted.
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders 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, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[INSERT CONTACT METHOD].
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][mozilla coc].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][faq]. Translations are available
+at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[mozilla coc]: https://github.com/mozilla/diversity
+[faq]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations