kernc / kernc/logkeys

Simple encryption for LogKeys (patch attached)

Open
#124 1 comment 0 reactions 0 assignees View on GitHub
auto-migrated Priority-Medium Type-Defect
Dominant language
C++
Stars
834
Forks
254
PR merge metrics
No merged PRs in 30d

Description

```
Hello,

I didn't want logKeys to store the log files in plain text, in the case if
someone tries obtains my hard-drive, he/she can just read off from the log file
without even authenticating as root through my machine.

So I just added a few lines into main and into the args, that allow the files
to be "" encrypted "" as before they get written. (For now I just offset each
ascii character by 20.. =/)

Of course it is a very weak encryption, but I didn't want to store the files in
plain text. Of course, if someone views the source code he/she will figure out
how to decrypt it, but I was thinking about solving that in future
contributions.

I have commented out the code, tested it and created a patch for you. Hoping to
hear from you.

Best,
Steven Enamakel
```

Original issue reported on code.google.com by `steven...@gmail.com` on 1 Dec 2014 at 12:13

Attachments:
- [encryption.patch](https://storage.googleapis.com/google-code-attachments/logkeys/issue-124/comment-0/encryption.patch)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the attached encryption.patch and the changes it proposes in main and argument handling. Compare the requested protection with the existing log-writing behavior; done requires an agreed, secure design, implementation, and tests that verify logs are not stored in plaintext.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, linux
Domain
operating-systems, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.