From mint-bounce@lists.fishpool.fi Sun Jul 25 15:42:09 2010 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=FNE5YWtli0UzEWKPFIxPdpqYTnECx0c75hmWCfoWgUU=; b=mDUuJvi91HuAPUJFlIvHNHQ54h41bcXON3ED/5LNengTKNjcPq+rzG2bygWufYhWc2 LwXJQ4Cdo17j90qhCkgSF2I9Vfve3wbV6LDUqTd41QRVw3owOdB6mMvk4K+XiUnRqHBa iAmF+c5e8HhubJp9Uk/RtvBqRS2kYdZwIv9N0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=YL7p06H5PVZ31uPFnPk69BEHMnEbammw2ZaKfm3tPW9bz4VhIS1bidyM0GRkLGWd0d sC4EHyvXMf+01QWSA4NMzOqlteTryBHQ7BeLz+vpFxoaxv4gUOsxbZe3qz5NH0gTFgxN DUq6qgT1INmdlY2uaVeKb7trOHZBD3ROLRAMk= Subject: Re: [MiNT] The Thing vs. XaAES issue. Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Peter Persson In-Reply-To: <4C4C7D76.7070604@online.no> Date: Sun, 25 Jul 2010 21:37:37 +0200 Cc: mint@lists.fishpool.fi Message-Id: <7811B7ED-9CD8-4113-BA2E-81E6A8931E6E@gmail.com> References: <23937111-F30C-49F5-B7C5-0D87281F9631@gmail.com> <4C4C7D76.7070604@online.no> To: Jo Even Skarstein X-Mailer: Apple Mail (2.1081) X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: pep.fishmoose@gmail.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id o6PJg8LU027854 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? -- PeP