https://github.com/technion/ct_advisor_int

Front End Interface for Google Certificate Transparency Monitoring
https://github.com/technion/ct_advisor_int

Last synced: about 2 months ago
JSON representation

Front End Interface for Google Certificate Transparency Monitoring

• Host: GitHub
• URL: https://github.com/technion/ct_advisor_int
• Owner: technion
• License: mit
• Created: 2015-12-16T09:11:14.000Z (about 9 years ago)
• Default Branch: master
• Last Pushed: 2023-03-18T09:02:07.000Z (almost 2 years ago)
• Last Synced: 2023-03-22T19:32:56.190Z (almost 2 years ago)
• Language: Ruby
• Homepage:
• Size: 639 KB
• Stars: 2
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE.txt

Awesome Lists containing this project

README

        
ct_advisor_int

==========

[![Build Status](https://travis-ci.org/technion/ct_advisor_int.svg?branch=master)](https://travis-ci.org/technion/ct_advisor_int)

ct_advisor is a proactive alerting tool for [Google's Certificate Transparency](https://www.certificate-transparency.org/).

# Shutdown Statement

The production instance of CT Advisor is shutting down. Although this was open source, as far as I'm aware there were no other installations of this application. Accordingly, this repo is being archived. See below for further information.

https://lolware.net/blog/shutdown-ctadvisor/

## Original README

Google offers a number of great options for an administrator to utilise this feature. Unfortunately being an early adopter, particularly if you run Windows servers or run SSL on appliances, makes it difficult to take advantage of this service.

As an alternative option, this service continually polls the CT log, and will trigger alerts if a certificate is ever registered for your domain, by any CA in the CT program. This can be used to identify fraudulent certificates.

This image this ct_advisor in action:

![CT Advisor Email](https://lolware.net/media/images/ct_advisor_email.jpg)

ct_advisor_int is the front-end interface, which manages signups and unubscriptions, to the database shared with the backup.

[The backend source code can be found here](https://raw.githubusercontent.com/technion/ct_advisor)

This service is running live and, unless you are interested in development, users are encouraged to use my existing service in place of running it themselves.

Setup

-----

The following items must configured in .env:

```

DEV_DB_PASS=xx

TEST_DB_PASS=xx

SMTP_HOST=xx

SMTP_USER=xx

SMTP_PASS=xx

RECAPTCHA_SITE_KEY=xx

RECAPTCHA_SECRET_KEY=xx

```

Management

----------

Start: 

```

RAILS_ENV=production puma -C config/puma/production.rb

```

Uninterupted restart:

```

kill -s SIGUSR2 `cat tmp/pids/puma.pid`

```

Contributing

------------

* In line with the above, potential contributors should be aware I am unlikely to merge and changes relating to features that I won't be using.

* Complex functions must include tests

* Leave your politics at the door