Recent changes to bugs

null(default) cipher failure

gvon — Thu, 03 Jun 2010 13:32:10 -0000

when using the default null cipher and the set key button is hit, an error message pops up and says there is an error at applications.cryptotoolj.KeyDialog.<init>(KeyDialog.java:92)

Ceasar Error/Limitation

Jeff Young — Mon, 23 Nov 2009 23:11:45 -0000

The documentation says with Caesar it should work with any ASCII character. From my understanding a ~ is ASCII 126. However, when run in the applet, I select Caesar, and "all ASCII" under select key, a ~ is encrypted to a blank. I ran it with many different shift lengths, and it returned the same blanked encryption.

When I copy the blank, and decrypt it, the applet does produce a ~.

The same happens with other characters, such as }, when they are shifted beyond 126.

I don't know if this qualifies as a bug, or a limitation of the algorithm.

Applet Error

Jeff Young — Sun, 22 Nov 2009 21:54:06 -0000

When the applet is used to run the Affine engine an error is produced. After selecting Affine, and then selecting AZ in the key window this error
java.lang.Exception: ERROR: Plain and cipher alphabets must be the same size
at hcrypto.cipher.HistoricalKey.initKeyArrays(HistoricalKey.java:265)
at hcrypto.cipher.HistoricalKey.initKey(HistoricalKey.java:175)
at hcrypto.engines.AffineKey.init(AffineKey.java:96)
at applications.cryptotoolj.CipherFrame.actionPerformed(CipherFrame.java:387)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1882)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2202)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
at java.awt.Component.processMouseEvent(Component.java:5602)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3135)
at java.awt.Component.processEvent(Component.java:5367)
at java.awt.Container.processEvent(Container.java:2010)
at java.awt.Component.dispatchEventImpl(Component.java:4068)
at java.awt.Container.dispatchEventImpl(Container.java:2068)
at java.awt.Component.dispatchEvent(Component.java:3903)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4256)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3936)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3866)
at java.awt.Container.dispatchEventImpl(Container.java:2054)
at java.awt.Window.dispatchEventImpl(Window.java:1801)
at java.awt.Component.dispatchEvent(Component.java:3903)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:176)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)

is produced in the console, and the applet does not allow you to run the applet. Either it should allow for both sizes of letters, or the option shouldn't be present for the Affine engine.

Run Time Error

Jeff Young — Sun, 22 Nov 2009 21:51:25 -0000

The Affine engine is producing this error...
Exception in thread "main" java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1768)
at hcrypto.engines.AffineKey.init(AffineKey.java:98)
at applications.TestCipher.main(TestCipher.java:81)
This occurred with the arguments "Affine 5,11/az+AZ testMEssAge", the same occurred with arguments such as Affine 5/az+AZ and Affine 5/,11/az+AZ/az+AZ.

Railfence keyspec

Nicolae Dragu — Tue, 10 Nov 2009 00:27:51 -0000

Railfence keyspec in the documentation is different from the one accepted
by the algorithm.

Playfair key problem

Todor Mitev — Thu, 05 Nov 2009 19:38:35 -0000

When the key does not consist of only letters the following error appears:

Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: -48
at hcrypto.engines.PlayfairKey.initKeySquare(PlayfairKey.java:236)
at hcrypto.engines.PlayfairKey.init(PlayfairKey.java:107)
at hcrypto.examples.TestCipher.main(TestCipher.java:78)

Playfair empty key problem

Todor Mitev — Thu, 05 Nov 2009 19:37:11 -0000

When the key is empty, the program returns the following exception:
Exception in thread "main" java.lang.Exception: Invalid key specification:
at hcrypto.cipher.HistoricalKey.initKey(HistoricalKey.java:159)
at hcrypto.engines.PlayfairKey.init(PlayfairKey.java:103)
at hcrypto.examples.TestCipher.main(TestCipher.java:78)

Affine lack of user documentation

Dimitar Gochev — Thu, 05 Nov 2009 19:31:58 -0000

I was not able to get the Affine algorithm to run from the run configurations, although it works from the applet. I looked for some documentation on how to run it (possibly an example) but was not able to find one.

Affine argument problems

Dimitar Gochev — Thu, 05 Nov 2009 19:30:04 -0000

The Affine algorithm ran in the CryptoToolJ applet with all sorts of arguments. However, it did not run in eclipse from Run configurations with arguments: Affine 3,3/azAZ09 text
I also tried varying the argument with 3,3/az+AZ+09 text and "3,19/azAZ09" and many others but none seemed to work. I was getting an error stating Invalid A_E_Key.

VigenereKey format

tisdallya — Thu, 05 Nov 2009 19:05:17 -0000

The documentation regarding proper formation of the keyword and alphabet pair in VigenereKey.java appears to be inaccurate and missing some details. It states that the keyword may use az, AZ, and 0-9. The alphabet may also use az, AZ, and 09 but it must match the characters used in the keyword. The documentation states that the key format would be something like: theKEYWORD01/azAZ09. When I used this type of format, it threw an "illegal alphabet descriptor" error. Using a keyword comprised only of lowercase letters and the alphabet az: keyword/az will encrypt only lowercase letters. Using a format not mentioned in the documentation where the descriptor is formed using the plus operator will encrypt everything. For example: theKEYWORD01/az+AZ+09 will properly encrypt something like "I saw 10 dogs". I think this should definitely be made more clear in the documentation but I'm not 100% sure of the proper descriptor format(s).