[Deque]

HC-Community Project - Multiencoder

Description:

With this tool written in Python you can simply apply chain encodings to a given text.

You have probably encountered threads with downloads for password protected archives with instructions how to decode the given encoded password. It is cumbersome to search for various online converters and copy&paste several times just to get the plaintext. This tool makes it much simpler.

This tool is a community project, that means every HC member can participate by adding new encodings.

By now it supports 26 different encoding and encrypting algorithms. I am sure there will be more soon.

Here is a screenshot of how it works:

Spoiler:

Download:

https://github.com/HCDevelopers/MultiEnc...master.zip

Usage:

Unzip the archive, open your terminal, go into the archive folder and type:

Code:

python multiencoder.py

Choose your algorithm, decide whether you want to encode or decode. Encoding algorithms are separated with space. Most algorithms have an abbreviation you can write instead. I.e. rot = rot13, base = base64, rev = reverse, ...

You also have the possibility to show a description for certain algorithms that have a (-i) behind.

The intermediate results and the end result will be shown.

Have a look at our Wiki for a detailed guide.

Requirements: Python 2.7

Supported Encodings:

rot13, rot5, rot18, rot47, binary, morse, vigenere, gila, tripo, feron, tigo, esab - @Ex094
base64, hazz15, atom128, megan35, zong22 - @Deque
reverse, leet - @noize
hex, xor, psychosubcipher, shiftcipher, gronsfeld, zara128, atbash - @Psycho_Coder

Upcoming soon:

rsa, more crypo encodings

Authors (by now):

@Psycho_Coder (Encoding Algorithms, Wiki, Algorithm Descriptions, Maintenance, Python Package, Python 3 Branch)
@Ex094 (Encoding Algorithms)
@noize (Encoding Algorithms)
@Deque (Encoding Algorithms, UI, Maintenance)

You want to contribute?

Join us on Github: https://github.com/HCDevelopers/MultiEncoder
Participate in our contest: http://www.hackcommunity.com/Thread-Cont...#pid204688

Changelog:

Spoiler:

Version 0.3

• new encodings: rot5, rot45, rot18
  
• new encryptions: gronsfeld
  
• description for base64 variants
  

Version 0.2

• UI supports encryptions
  
• new encodings: psychosubcipher, hex
  
• new encryptions: vigenere, xor, shiftcipher
  
• bugfix for leet
  
• possible to show a description for encodings and encryptions (by now only implemented by vigenere)
  
• possible to generate keys, if provided by the encoding algorithm (by now only implemented by xor)
  
• new coder on board: @Psycho_Coder
  

Version 0.1

• encodings: rot13, binary, morse, base64, reverse, leet, hazz15, atom128, megan35, zong22
  
• chain encodings
  
• coders on board: @"Ex094" @noize @Deque
  

[Psycho_Coder]

Great tool! I wanna contribute and be a part of this too. Just Wait for some more time

[Psycho_Coder]

Great tool! I wanna contribute and be a part of this too. Just Wait for some more time

[Deque]

Here is a new screenshot of the functionality that comes next:

Spoiler:

Edit: I forgot to show the key generation:

Spoiler:

I will fix the row with authors too.

[Deque]

Here is a new screenshot of the functionality that comes next:

Spoiler:

Edit: I forgot to show the key generation:

Spoiler:

I will fix the row with authors too.

[Deque]

Here is a new screenshot of the functionality that comes next:

Spoiler:

Edit: I forgot to show the key generation:

Spoiler:

I will fix the row with authors too.

[noize]

I don't know if you should be shortening rot13 with rot, base64 with base... What if we add other rot versions or other bases based algorithms? rev = reverse is fine, but for the others I don't think so. Also, you're taking away 2 chars, I think the user could manage the effort.

[noize]

I don't know if you should be shortening rot13 with rot, base64 with base... What if we add other rot versions or other bases based algorithms? rev = reverse is fine, but for the others I don't think so. Also, you're taking away 2 chars, I think the user could manage the effort.

[noize]

I don't know if you should be shortening rot13 with rot, base64 with base... What if we add other rot versions or other bases based algorithms? rev = reverse is fine, but for the others I don't think so. Also, you're taking away 2 chars, I think the user could manage the effort.

[Deque]

I don't know if you should be shortening rot13 with rot, base64 with base... What if we add other rot versions or other bases based algorithms? rev = reverse is fine, but for the others I don't think so. Also, you're taking away 2 chars, I think the user could manage the effort.

rot13 is the most common case of all rot algorithms as well is base64 (i.e. compared to base32), so I will leave those abbreviations, no matter if other algorithms follow.
I myself find it far more easy to type base than base64, because I have to stretch the fingers very far to get to the numbers. I also tend to forget the numbers for hazz, zong and so on, because they are arbitrary (those are still base64 algorithms, just with other alphabets).

It's just a dictionary with abbreviations, I can change that easily if we get more algorithms with similar names. I don't see the problem.