https://github.com/leoloobeek/keyserver

Easily serve HTTP and DNS keys for proper payload protection
https://github.com/leoloobeek/keyserver

Last synced: about 1 month ago
JSON representation

Easily serve HTTP and DNS keys for proper payload protection

• Host: GitHub
• URL: https://github.com/leoloobeek/keyserver
• Owner: leoloobeek
• License: bsd-3-clause
• Created: 2018-09-30T21:04:35.000Z (over 5 years ago)
• Default Branch: master
• Last Pushed: 2018-11-10T02:33:34.000Z (over 5 years ago)
• Last Synced: 2024-02-15T07:33:00.579Z (4 months ago)
• Language: Go
• Homepage:
• Size: 24.4 KB
• Stars: 60
• Watchers: 4
• Forks: 9
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Lists

• awesome-go-security - keyserver - Easily serve HTTP and DNS keys for proper payload protection. (Command and Control)
• cybersecurity-golang-security - keyserver - Easily serve HTTP and DNS keys for proper payload protection. (Command and Control)

README

        
# keyserver

### Compiled Binaries

You can retrieve the latest release of keyserver binaries in the Releases page.

### Build

If you would prefer to build the source yourself, make sure Go 1.10+ is 

installed and execute the following:

```

go get -u github.com/leoloobeek/keyserver

```

This project uses the following dependencies:

- github.com/op/go-logging

- github.com/miekg/dns

- github.com/chzyer/readline

### Usage

Head on over to the wiki for more usage information.

### Contributions

I'm sure there will definitely be bugs, but also this tool was written to match my workflow. If there's something you would find useful feel free to submit an Issue or even a PR!

### HUGE Thanks

Thanks to the following people for their awesome code:

- OJ [@TheColonial](https://twitter.com/TheColonial) as I took most of his DNS code from one of his [live streams](https://www.youtube.com/watch?v=FeH2Yrw68f8)

- [evilsocket](https://twitter.com/evilsocket) for [bettercap](https://github.com/bettercap/bettercap), a really well written Go application which I used as a reference point multiple times, including his readline usage. I almost don't want to mention him here, as my Go code is nowhere near his level and this might look bad on him :D