Take a look here, it has the up to date info on sles package: http://www.mono-project.com/docs/getting-started/install/linux/#opensuse-and-sles
Alan On 1 December 2015 at 11:48, Kaushik Velusamy <kaushikvelus...@gmail.com> wrote: > Thanks for the info Alan. > > This issue is with SUSE Linux Enterprise Server 11 SP3. I don't see a > Linux version in 4.X series in mono. > > Sorry, i m new to this. Could you tell me if there is any work around? > > - Kaushik > > > > On Tue, Dec 1, 2015 at 3:39 PM, Alan <alan.mcgov...@gmail.com> wrote: > >> I'd say trying a newer mono build first would be the best option. Either >> 4.2, 4.3 or master. SHA2 certs have been supported for a very long time, so >> if you are still having issues maybe you could provide access to some certs >> to reproduce the problem with? >> >> Alan >> >> On 30 November 2015 at 12:04, Edward Ned Harvey (mono) < >> edward.harvey.m...@clevertrove.com> wrote: >> >>> > From: mono-list-boun...@lists.ximian.com [mailto:mono-list- >>> > boun...@lists.ximian.com] On Behalf Of Kaushik Velusamy >>> > >>> > I have a query regarding SHA-2 supported version in mono. >>> > >>> > Novell iFloder ( On OpenEnterpriseServer11SP3) which runs on SLES11SP3 >>> > ran into an issue because of SHA2 certificates. eDirectory has moved >>> to SHA- >>> > 2 certificates and hence all components of OES needs to be compatible. >>> > However iFloder is having issue since MONO that is part of SLES11SP3 ( >>> > mono-core-2.6.7-0.9.1.x86_64.rpm) does not support SHA-2. >>> > >>> > I tried in mono-3.6 as well. >>> > >>> > Could you tell me which is the supported mono version for SHA-2? >>> >>> I think there's something wrong in your question. SHA2 (generally SHA256 >>> to SHA512) is definitely supported in mono. >>> >>> Your error message does say " Unsupported hash algorithm: >>> 1.2.840.113549.1.1.11" and the OID does map to sha256WithRSAEncryption, but >>> the problem is in Mono.Security.X509.X509Certificate, which is all kinds of >>> messed up, and barely functional at all. I have not heard of anyone working >>> on it - but that doesn't mean they're not. >>> >>> If I'm not mistaken, iFolder is not actively maintained, right? That >>> would be a problem. Yes, there is a limitation of mono in the brokenness of >>> X509Certificate, but assuming that's not going to be fixed anytime soon, >>> the iFolder developers will basically need to find a way to workaround the >>> problem... >>> _______________________________________________ >>> Mono-list maillist - Mono-list@lists.ximian.com >>> http://lists.ximian.com/mailman/listinfo/mono-list >>> >> >> >
_______________________________________________ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
