Search
Pete Silva - Daily Dose of Pete
You are here: DevCentral > Weblogs

posted on Wednesday, September 16, 2009 4:07 PM

According to various history sites, the earliest known lock to be key operated was from Egypt, some 4000 years ago.  It was wooden and actually used moveable pegs that fell into holes to secure the ‘bolt.’  The wooden key would move the pins back into place to allow the lock to be opened.  And, of course, Caesar is credited with inventing the first cipher.  Ahh, love history and always fun to know where some of today’s technologies came from.

In security, specifically cryptography, a key is a specific number value that when used with an algorithm can encrypt and decrypt a block of data – usually text.  The key length or size, typically in bits or bytes, determines how strong the encryption is and thus how difficult it might be to decrypt.

There is Symmetric and Asymmetric encryption.  With symmetric encryption, only one ‘secret key’ is used on both ends to encrypt and decrypt messages.  This is one of the oldest encryption techniques and can be as simple as shifting or replacing a letter.  This works great if both parties have the secret shared key but it needs to stay SECRET.  The bad side is that it’s just a single key and if someone gets a hold of it, then they can possibly intercept and decrypt your hidden messages.  Key management, such as changing the secret key often and distributing it securely to authorized users can be a challenge.

In Asymmetric encryption, also called Public Key – Private Key cryptography, two keys are used – one for encryption and one forring decryption.  The private key is always kept secret while the public key  is out in the wild often in the form of a certificate.  So you can have my public key, in fact I might just give it to you, since that will be what you use to either encrypt a message to me or decrypt a message from me.  It is my private key that will do all the mashing so i can read your encrypted note and respond in secret.  The unique keys are paired and by using the same algorithm we can communicate incognito and no other key (or pair) can decrypt the data.  This infrastructure can also be useful to prove identity and ensure the message has not been tampered.

Then why PKI?  When you send an encrypted message, it is digitally signed with your private key but I’m not standing next to you watching the ink hit the paper.  PKI is what validates trust.  With certificates (your public key) there is usually a Certificate Authority who is essentially a third-party vouch.  Yes you can create self-signed certs but with a Cert Authority, they can verify your identity (or signature) and add their own signature as a stamp of approval.  PKI can store your certificates, revoke certificates, backup/recover keys, time stamp and a bunch of other services.  While public keys are meant to be public, their integrity is essential and PKI can accomplish that. 

Like anything security related, nothing is foolproof.  Secure distribution of keys is essential to prevent Man in the Middle attacks.  You might ask for my public key and I sent it to you, but someone else intercepts it on the way.  They send a forged note to you along with their public key, claiming to be me.  You decrypt the message since you think it’s from me and subsequently send an encrypted note back, but you’ve encrypted it with the interceptor’s key.  They grab it again, in transit, decrypt, keep a copy, re-encrypt with my original public key and forward on.  When I get it, I still believe it came from you and no one’s the wiser.  Simple additions like passwords for private keys or mutual authentication can help defend against MITM among other techniques (pdf).

I realize this was not my usual ‘link-fest’ entry with stats and fun stories, there are a slew of mathematical computations to make this all work and many other components to effective key management and deployment.  But for number 11 of 26 Short Topics, I just wanted to convey that your digital Keys are an integral part of keeping your data secure from eavesdropping and tampering and can verify that you are transmitting it to/from from a trusted entity.  Too bad the trusty TRIX Decoder rings are no longer available.

ps


Related links:



Feedback

9/16/2009 6:04 PM
Gravatar a wooden lock seems kind of pointless but I guess 4,000 years ago it probably would of worked pretty good
alyssa
9/17/2009 6:01 AM
Gravatar yeah but if I remember correctly, they didn't look kindly on thieves & punishments could be severe. Wood might have been all they needed since the laws were deterrent enough.

ps
psdev
9/17/2009 6:41 AM
Gravatar Nowadays you have readily accessible modern technology like steel handsaws and portable torches, and even cordless sawzalls.

I bet 4,000 years ago it took some specialized and very expensive tools to be able to break open a well crafted tropical hardwood lock. Your average thug on the street wasn't going to get through it so easily.

Just like nowadays it takes some specialized and very expensive tools to crack good pki...


Rick
9/18/2009 10:29 AM
Gravatar Brought to you by the Letter L and the Number 7
Pete Silva

Let Me Know What You Think


Please use the form below if you have any comments, questions, or suggestions.

Title:
 
Name:
 
Email: (so we can show your gravatar)
Website:
Comment: Allowed tags: blockquote, a, strong, em, p, u, strike, super, sub, code
 
Please add 6 and 2 and type the answer here:

Blog Stats

Posts:285
Comments:98
Stories:0
Trackbacks:111
  

Post Categories

  Cloud Computing
  Security
  SSL VPN
  Information security
  pci
  PKI
  application attacks
  malware
  mitigation
  client security
  compliance
  notification laws
  social media
  social networks
  twitter
  facebook
  youtube
  digg
  peter silva
  social media stats
  ipv6
  ipv4
  2012
  context
  contextual aware
  user centric
  decision
  game show
  granular
  control
  identity
  cloud security
  virtualization
  sys-con
  cloud expo
  virtual
  glenn brunette
  sun microsystems
  Bruce Schneier
  Schneier on security
  research
  2009
  blog
  2010
  threat
  pci dss
  regulations
  espionage
  pentagon
  crown jewels
  tower of london
  health care
  banking
  prediction
  cybercrime
  cybercrime kits
  dyi
  dnssec
  dummies
  l0pht
  2600
  breach
  privacy
  breaches
  web security
  spam
  trojan
  gogrid
  blogger
  personal
  business
  H1N1 flu
  emergency preparedness
  disaster recovery
  network security
  oracle
  sso
  single sign on
  big-ip
  oracle access manager
  f5
  personal devices
  mobile devices
  mobile security
  windows
  microsoft
  windows 7
  desktop
  games
  gaming
  online games
  DDoS
  scams
  consolidation
  data center
  tech sector
  single purpose
  dedicated
  management
  access security
  policy enforcement
  utm
  processing power
  video
  audio
  multi-media
  dns
  webinar
  interview
  ioactive
  kaminsky
  dan kaminsky
  partner
  rsa
  xml
  splunk
  instructional
  in 5
  education
  training
  idc
  smart city
  smart grid
  infrastructure
  web 2.0
  standards
  inter-cloud
  interoperability
  application mobility
  peering
  confusion
  cloud confusion
  cloud survey
  edge gateway
  v10.1
  history
  words and meanings
  lists
  fun
  patent
  intellectual property
  trade secrets
  confucius
  cloudfucius
  series
  blog series
  a-z
  law
  constitution
  court
  fourth amendment
  gps
  government
  legal
  vmotion
  vmware
  case study
  interop
  v10.2
  database
  csrf
  asm
  adc
  arx
  data manager
  netapp
  storage
  WAN optimization
  application delivery
  optimization
  compression
  whitepaper
  statistics
  cloud research
  cloud stats
  LTM VE
  travel
  firepass
  encryption
  music
  humor
  uptime
  cloud outage
  SLA
  availability
  customer
  vmworld
  yankee group
  sports
  NFL
  performance
  acceleration
  peoplesoft
  rman
  recovery manager
  oow
  openworld
  replication
  integration
  apm
  wi-fi
  numbers
  firepass
  risk
  open source
  authentication
  smart card
  kerberos
  Business Challenges
  evidence
  SSL
  SSL offload
  NIST
  2048-bit
  certificate
  rss
  blog analytics
  web traffic
  e-cards
  hardware
  support
  diagnostics
  iHealth
  apple
  iPhone
  iPad
  iOS
  itunes
  smartphone
  v10.2.1
  citrix
  vdi
  parody
  satire
  entertainment
  andriod
  virus
  google
  mac
  comscore
  ID theft
  social security
  ssn
  synthetic ID theft
  credit report
  data privacy
  cyber threat
  reports
  50 ways
  2011
  trade show
  silva
  emc
  emc world
  ixia
  viprion
  ssl tps
  vCMP
  outtakes
  acting
  theatre
  tokens
  vpn
  remote access
  intrusion 2.0
  toys
  v11
  ajax
  SANS
  devcentral
  whitehat
  sentinel
  waf
  scanner
  grossman
  iApps
  wan op
  file virtualization
  hawaii
  emea
  ipexpo
  london
  UK
  human behavior
  risk managment
  tech center
  secure vault
  fips
  appliance mode
  copyright
  pearl harbor
  Dec 7
  punchbowl
  honolulu
  staffing
  jobs
  irules
  AppSec
  TradSec
  icsa
  v11.1
  community
  

82,243 Members in 102 Countries and Growing!

Join DevCentral Today!

About DevCentral

DevCentral has been a successful, thriving community for many years. We have always strived to bring you the best technical documentation, discussion forums, blogs, media and much more that we can.

So dive in, get familiar with DevCentral. We hope you like it, we hope it makes your job easier, and lets you get that much more power out of the community. To learn more, make sure to check out the Getting Started section. And if you have any problems, or think something could be easier to use, drop us a line to let us know.

Got It !

We've received your comment and transmitted it directly to DevCentral HQ.

Thanks for taking time to let us know what's on your mind. At DevCentral | Community Matters!

Get In Touch With Us

Have questions, suggestions or just want to get something off your chest?

Use our handy form below to Direct Connect with DevCentral Mission Control.

Send Us Feedback       or