From mint-bounce@lists.fishpool.fi Sun Jul 25 16:30:18 2010 Message-ID: <4C4C9E53.3050802@online.no> Date: Sun, 25 Jul 2010 22:28:03 +0200 From: Jo Even Skarstein User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.10) Gecko/20100527 Thunderbird/3.0.5 MIME-Version: 1.0 To: mint@lists.fishpool.fi Subject: Re: [MiNT] The Thing vs. XaAES issue. References: <23937111-F30C-49F5-B7C5-0D87281F9631@gmail.com> <4C4C7D76.7070604@online.no> <7811B7ED-9CD8-4113-BA2E-81E6A8931E6E@gmail.com> In-Reply-To: <7811B7ED-9CD8-4113-BA2E-81E6A8931E6E@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: joska@online.no Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: On 07/25/2010 09:37 PM, Peter Persson wrote: > 25 jul 2010 kl. 20.07 skrev Jo Even Skarstein: > >> Thing 1.29 does not have this problem, only previous versions. So I >> assume that this is a bug that has been fixed. Too bad that 1.29 has a >> couple of new bugs... >> > Thing 1.27 works on all other AES:s afaik, and I kind of dislike the idea of upgrading Thing to a semi-official beta just to be able to use it again. But if it works, I guess that's the only choice I have... > > Still, I wonder what triggered the problem w. v1.27, and why it doesn't work on 1-17? If it's a case of "no idea", the AES is on the wrong track imo. Anyone? > I think this will be hard to debug until the Thing sources are available. The last I heard was that everything was OK to release the sources, but nothing has happened yet. Jo Even