Why does my SSH private key still work after changing some bytes? (2016) (crypto.stackexchange.com)

Article summary

The article discusses why an SSH private key remains functional even after modifying some of its bytes. The comments suggest that this is due to the key's format and the specific parts of the key being used or ignored by the client. The discussion revolves around the robustness and fragility of binary and text formats, as well as the history and application of RSA encryption. The original article is not available, but the comments provide insight into the topic.

Main themes

• SSH private key functionality
• binary vs text formats
• RSA encryption history
• cryptography development
• key sharing and management
• format robustness and fragility
• mathematical concepts in cryptography

What commenters say

• Modifying certain parts of an SSH private key does not affect its functionality because those parts are not being used by the client.
• The robustness of binary formats is demonstrated by the key's continued functionality despite modifications.
• Text formats are more prone to errors and inconsistencies due to human interpretation and implementation.
• RSA encryption uses basic math concepts that have been known for centuries, but its practical application was not feasible until the advent of computers.
• The history of cryptography is marked by parallel discoveries and the delayed application of theoretical knowledge.
• The problem of sharing secret keys is an old one, and RSA's development was not solely dependent on the existence of computers.
• The complexity of RSA math is not a significant barrier to manual calculation, but rather the lack of a practical need for it prior to the computer era.
• The distinction between binary and text formats is not always clear-cut, and both have their advantages and disadvantages.