The Generic Encryption Program (GEP)

Aja on 10/1/2009 at 10:14

Quote Posted by denisv

You should release the source code so I can rewrite it in five lines of Haskell

I could do it in four, h4ck3r.

Aja on 10/1/2009 at 10:18

I get this error upon encrypting:

Code:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.IOException: The process cannot access the file 'C:\Users\David\Desktop\albums I need.doc' because it is being used by another process.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode)
at GEP_1._1.Form1.cmdEncrypt_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
GEP 1.3 R1
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/David/AppData/Local/Temp/7zOAF61.tmp/GEP%201.3%20R1.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

dvrabel on 10/1/2009 at 10:57

I took at look at the source code expecting to find mistakes like failing to lock keys into memory. I didn't expect to find this:

Code:

xor_byte = 0x10
[...]
encode_byte = Convert.ToByte(Convert.ToInt32(ret_char) ^ xor_byte);

That's not encryption -- it provides absolutely no security at all.

Security is complex field and should only be tackled by competent people.

denisv on 10/1/2009 at 12:23
Quote Posted by Aja
I could do it in four, h4ck3r.

Code:
lamecrypt = map$ chr.(`xor`0x10).ord
main = interact lamecrypt

beat that, h4x0r.

Ulukai on 10/1/2009 at 18:28
Quote Posted by dvrabel
I took at look at the source code expecting to find mistakes like failing to lock keys into memory. I didn't expect to find this:
Code:

xor_byte = 0x10
[...]
encode_byte = Convert.ToByte(Convert.ToInt32(ret_char) ^ xor_byte);

That's not encryption -- it provides absolutely no security at all.

Security is complex field and should only be tackled by competent people.

How do you think these competent people became competent in the first place? By experimenting with their own programs and learning from their mistakes.

No-one is suggesting you encrypt your collection of lesbian vampire porn with it.

Controversially, you could choose to stop being a bit of a tit and explain why this is bad.

denisv on 10/1/2009 at 18:38
Quote:
How do you think these competent people became competent in the first place? By experimenting with their own programs and learning from their mistakes.

Experimenting might be how you learn to play an instrument. It's not how you learn cryptography.

37637598 on 10/1/2009 at 19:01
Yeah, I mean... It's not like whoever invented cryptography experimented at all, they just one day knew exactly what to do. If any of you knew anything, you would know that.

Kolya on 10/1/2009 at 19:45
Quote Posted by Ulukai
lesbian vampire porn

(http://www.youtube.com/watch?v=-Vm8MTl5kMo) Yes please. :cool:

Fingernail on 10/1/2009 at 20:52
don't try and do things, guys... in any field there are already EXPERTS who can do it better than you can.

Fringe on 10/1/2009 at 21:25
That's why I'm here on the Internet, as opposed to doing things.

Oh, shit, wait.

<_<

>_>

What if there are people who can Internet better than me?