<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to 13: Better error handling of invalid private keys</title><link>https://sourceforge.net/p/aws-eclipse/issue-tracker/13/</link><description>Recent changes to 13: Better error handling of invalid private keys</description><atom:link href="https://sourceforge.net/p/aws-eclipse/issue-tracker/13/feed.rss" rel="self"/><language>en</language><lastBuildDate>Sun, 29 Mar 2009 00:39:44 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/aws-eclipse/issue-tracker/13/feed.rss" rel="self" type="application/rss+xml"/><item><title>Better error handling of invalid private keys</title><link>https://sourceforge.net/p/aws-eclipse/issue-tracker/13/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;If we try to use an invalid private key (ex: the private key for the EC2 certificate, not for the EC2 Key Pair) to execute a remote command or publish files to a remote host, the error message that comes back just says that the command or file copy failed without providing the user enough information to figure out what went wrong.  Users can start Eclipse from the command line to get more verbose logging and see what's happening, but they shouldn't have to rely on that output from the command line.&lt;/p&gt;
&lt;p&gt;We should make sure we're passing as much useful information back in those error messages as possible so that the user can easily figure out what they need to do to get things working.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jason Fulghum</dc:creator><pubDate>Sun, 29 Mar 2009 00:39:44 -0000</pubDate><guid>https://sourceforge.net05b91656123ea6cf7ed743302f6951949d182fc2</guid></item></channel></rss>