Micah Lee
Micah Lee
Just in case the user included the wrong public key, or doesn't know how to decrypt the email they received, the plaintext one should give them instructions on what to...
Right now it requires users to attach their public key. Based on Seth's comment in #3 I think it should continue to require this, but it should also search key...
We should have usage analytics. At the very least the number of emails the bot reads, but at most the properties of each email that was sent. That way we...
I think this has to be a long-term feature, but doesn't it make sense to localize the response email template? People who speak all different languages will want to use...
After installing the .deb version of keybase, running `apt update` includes the following warning: ``` W: http://prerelease.keybase.io/deb/dists/stable/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in...
Flock will have a database of what versions of software everyone has installed. NIST's National Vulnerability Database (NVD) provides a JSON feed of new vulnerabilities: https://nvd.nist.gov/ We should integrate Flock...
We're collecting [differential osquery logs](https://github.com/osquery/osquery/blob/master/docs/wiki/deployment/logging.md#differential-logs), which means we only get data when something changes. For example when an OS is upgraded, we get two results with the same timestamp and...
We should make a new authenticated API route `/heartbeat` which all clients routinely load (every 2 minutes?). The response should include the logged in user's name (#16), as well as...
For all of the same things that trigger keybase notifications to the security team (#15), we'll want to notify the user themselves as well. This includes: - After they successfully...
In the far future of Flock, I'd like to add support for providing the server with a list of Indicators of Compromise (IOCs), and have the agents proactively alert on...