A Wicked String

By Daniel Miessler on February 6th, 2007: Tagged as Security

So I was on my bank’s site last night and noticed this (among other things) in the URL: 

CIPHER_TEXT_IN_HEX=218EE5C57B46F79D81F1083104A072B
60695EBD29FBF321F21773CADCE5D5C31C71D49062C48792EB4BB356EB745160A4
DD82677FE9086DADAE550675A910FD23BD022D00854E2116A8CD096D420C741F64
17AA341B47C34F0F9F4787DD5CA85DD56DF7482A87502DE727600BA9EE9F661292
E0C30FA8290BCFEFB38DEB4468633B0287F36C7694259A1BADE4AD833713A30587
147127EC353020A998E4E0F38C7BA7AB8611FD35317F1E5047187DD67953EEE9DF
D633F99EE93B48823C63FBD21E2ABD083E2195D&IV=F18C76B534DE358C
&sessionid=YHMAN0IYpO9M2jvUqTXsHMr_szV788EyGidaZAYd201019
That’s a wicked string.

  • Digg
  • Reddit
  • HackerNews
  • StumbleUpon
  • DZone
  • Google Bookmarks
  • Twitter
  • Facebook
  • del.icio.us
  • FriendFeed
  • Posterous
  • RSS
  • email
  

View Comments

  • Chase
    No, it's an encrypted string that they pass through the URL, probably along with an identification string of some sort. Seems normal to me.
  • Tim
    It seems to me that those are two pieces of information that shouldn't be in the url.
blog comments powered by Disqus

 

twitter_icon

Sample Original Content


Information Security

Tutorials and Primers

Culture & Society

Technology & Science

Politics

Philosophy & Religion

Miscellaneous

Tools & Projects


Blog Archives