<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
  <channel>
    <title>3jg13's Feed - Programmer's Heaven</title>
    <link>http://www.programmersheaven.com/feed/User/536831/RSS.aspx</link>
    <description>Events at Programmer's Heaven related to the user 3jg13.</description>
    <language>en</language>
    <copyright>Copyright 2013 Programmers Heaven</copyright>
    <pubDate>Tue, 21 May 2013 00:14:47 -0700</pubDate>
    <generator>Argotic Syndication Framework 2007.3.0.1, http://www.codeplex.com/Argotic</generator>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <ttl>360</ttl>
    <item>
      <title>RSA - upgrading key size on clients</title>
      <link />
      <description>&lt;p&gt;Posted a 'new message on the Security forum.&lt;/p&gt;Hi.&lt;br /&gt;
Got a new job, and first task is to upgrade the key sizes on our clients to 2048 bits (from 1024).  The code looks like it will sustain the upgrade fine (by that I mean the data types can support very large integers needed for the bigger key size).&lt;br /&gt;
&lt;br /&gt;
My biggest concern (fyi ... fairly new to RSA) is applying this upgrade to our client programs.  We have 100s of clients running in the wild and they all communicate with each other encrypted via RSA and all share the same key size as we started with 1024 by default.  But now we have to upgrade to bigger key size and the clients will be getting the update at varying times and so there could very well be clients communicating together with different key sizes (one client is 1024 bits and another is 2048 bits).  &lt;br /&gt;
&lt;br /&gt;
Is there anything I need to be aware of here?  Is there potentially anything that would cause the clients to not communicate together?&lt;br /&gt;
&lt;br /&gt;
Please advise, especially if anyone has any kind of experience with this.&lt;br /&gt;
&lt;br /&gt;
Thanks&lt;br /&gt;
Jeff&lt;br /&gt;</description>
      <pubDate>Thu, 10 Mar 2011 18:09:33 -0700</pubDate>
    </item>
  </channel>
</rss>