kritbit

kritbit Commit Details


Date:2015-12-19 10:37:17 (9 years 2 days ago)
Author:Natalie Adams
Branch:master
Commit:3b6571caa69e8f7062b963f8ea52800c957f6c16
Parents: 4e95b3883ca3e153fb2275be002c2c16e46f01bd
Message:updating README

Changes:

File differences

README.md
1515
1616
1717
18
18
19
20
1921
2022
2123
......
6466
6567
6668
67
69
6870
6971
7072
......
8890
8991
9092
91
9293
9394
9495
95
96
97
98
99
100
101
102
103
104
96105
97106
98107
Note: Kritbit originally had 3 purposes - one of them being running commands remotely. But since you can run any arbitrary script you can run a command remotely via SSH or some other external service. Yes, Windows does not have SSH natively (yet?) - but you can download an implementation [here](http://www.freesshd.com/).
Kritbit is designed to be simple and flexible. It makes no assumptions about your security and only provides minimal security procedures. I am not a crypto expert - but I make tools that work. So while I cannot guarantee that big brother won't be able to decrypt messages from external services - it should be good enough for most implementations. So please, if you find that the crypto security is less than perfect I accept patches of any size, creed, or color. The encryption technology used isn't meant to prevent a guy with a Beowulf cluster from cracking your message - but rather preventing some script kiddie with Firesheep from seeing what you are doing.
# Security
Kritbit is designed to be simple and flexible. It makes no assumptions, or verifications, about your security and only provides minimal security procedures. I am not a crypto expert - but I make tools that work. So while I cannot guarantee that big brother won't be able to decrypt messages from external services - it should be good enough for most implementations. So please, if you find that the crypto security is less than perfect I accept patches of any size, creed, or color. The encryption technology used isn't meant to prevent a guy with a Beowulf cluster from cracking your message - but rather preventing some script kiddie with Firesheep from seeing what you are doing.
# Authentication/Authorization
# Sending script runs to kritbit
There is provided runcommand Python script in the scripts directory. This should be modified to fill in data for your script. This will wrap the encryption and data structure in an easy to use library.
There is a provided runcommand Python script in the scripts directory. This should be modified to fill in data for your script. This will wrap the encryption and data structure in an easy to use library.
To use it just invoke it like so:
- Provide a way to offer more customization for viewing job information. Right now it's very generic - but it might be useful to be able to parse output and present custom columns or other data.
- Permission matrix allowing people to grant fine permissions to jobs and job history
# Patches
Patches are welcome of any kind. But please do note that your code will be integrated into the project under the MIT license. Mention to your contribution may not appear in the code or file. But we can certainly make mention on the README describing your contribution.
Patches are welcome of any kind. But please do note that your code will be integrated into the project under the MIT license. Mention to your contribution may not appear in the specific code or file that it applies to. But we can certainly make mention on the README describing your contribution.
If you do provide a patch changing backend crypto - then you should also provide a patch updating the crypto for the provided scripts.
# Screenshots
[![pic1](https://srchub.org/cdn/kritbit.png)](https://srchub.org/cdn/kritbit.png)
[![pic1](https://srchub.org/cdn/kritbit2.PNG)](https://srchub.org/cdn/kritbit2.PNG)
# Attributions

Archive Download the corresponding diff file

Branches

Number of commits:
Page rendered in 0.05723s using 14 queries.