Talk:XOR cipher

ROT-13

ROT-13 is not an XOR cipher. ROT-13 is a mono-alphabetic cipher. —Preceding unsigned comment added by 2008 66.92.90.194 (talk • contribs) 20:22, 27 December 2008

You are of course completely correct and I have removed the reference to ROT-13 as erroneous. If anything ROT-13 is a base 26 key with a value of 13 repeated applied to the text through modular addition. In the future please feel welcome to click the "edit" button at the top of any page and make any correction or improvement that you feel will improve the encyclopedia. Please leave an explanation of any such edit in the "Edit summary" box. I know it has been almost a year since you posted that, but perhaps you will see this reply nonetheless. Chillum 00:50, 25 September 2009 (UTC)

Connection: fxf=id, this means if you apply the chipher function twice, you will get the original. —Preceding unsigned comment added by 84.60.25.228 (talk) 22:35, 4 February 2011 (UTC)

Combination with book cipher?

Is there any knowledge or experience how secure an encryption would be that combines book cipher and XOR? Like: State a random offset in a shared file (that is owned by sender and receiver), then XOR any byte of the message byte by byte with each subsequent byte of the shared file (starting at offset)...

Just a thought... —Preceding unsigned comment added by 84.60.25.228 (talk) 22:38, 4 February 2011 (UTC)

Nonzero variant

A variant exists to systematically produce a nonzero cyphertext, which is useful for Null-terminated strings: In this one, whenever the key and plaintext have the same letter, simply copy that letter to the output instead of zero. Medinoc (talk) 20:41, 21 June 2011 (UTC)

Why I changed the Python example

The Python example, as it was this morning, was both over complicated and illustrated the problem rather sub-optimally. A key aspect of this scheme is that the encryption function is its own inverse. But that wasn't true in the Python, which had different encrypt and decrypt functions. This was needed because it used strings to represent plaintext and bytearrays to represent keys and ciphertexts. There's no need for that; it works perfectly well for strings alone. So the version to which I've changed it does away with bytearrays and uses only strings, and thus has only a single function for xoring strings together. 87.115.241.113 (talk) 18:04, 28 January 2014 (UTC)

External links modified

Hello fellow Wikipedians,

I have just modified one external link on XOR cipher. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

• Added archive http://web.archive.org/web/20130413230658/http://chris.dod.net/xor/xor.php to http://chris.dod.net/xor/xor.php

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{Sourcecheck}}).

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 16:04, 16 July 2016 (UTC)