similar to: Enforcing TLS

Hello OpenSSH hackers, The last couple of weeks I've been figuring out how hard it is to replace FreeBSD's <utmp.h> with <utmpx.h>. I don't think utmpx is perfect, but at least it's better than what we have now and at least it has gone through some form of standardisation. I noticed POSIX says the following [1]: | The <utmpx.h> header shall define the utmpx

Hello all, The next version of FreeBSD will use utmpx for its user accounting database, as opposed to utmp which is used right now. Unfortunately wtmpx and lastlog handling isn't standardized at all, which is why we took the liberty to integrate all these databases into a compact API, where setutxdb() can be used to switch to a different database and getutxuser() to search for a USER_PROCESS

https://bugzilla.mindrot.org/show_bug.cgi?id=1732 Summary: Proper utmpx support for FreeBSD HEAD Product: Portable OpenSSH Version: 5.4p1 Platform: Other OS/Version: FreeBSD Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: unassigned-bugs at mindrot.org ReportedBy: ed

On 10 Jan 2015, at 17:35, Dimitry Andric <dimitry at andric.com> wrote: > > It looks like the interpretation of what "__STDC_MB_MIGHT_NEQ_WC__" means differs between the llvm developers and the FreeBSD developers. I'm not sure what a good solution is. I've just read the relevant parts of the C11 spec, and it's not really clear to me what the 'basic

On 12 Jan 2015, at 08:07, Dimitry Andric <dimitry at andric.com> wrote: > > > On 15 Oct 2014, at 19:42, Richard Smith <richard at metafoo.co.uk> wrote: >> On 15 Oct 2014 05:12, "Ed Schouten" <ed at 80386.nl> wrote: > ... >> The test case in the LLVM tree is invalid and should be discarded. It >> erroneously assumes that the encoding of

2015-03-29 3:33 GMT-05:00 Ed Schouten <ed at 80386.nl>: > I am cross-compiling compiler-rt for my specific use-case. That said, > I'm cross-compiling from x86-64 to x86-64, but for a different ABI. > This is what I use: > > > https://github.com/NuxiNL/cloudlibc/wiki/Building-runtime-libraries#user-content-compiler-rt > > -DCMAKE_CROSSCOMPILING=True > > As

* 罗勇刚(Yonggang Luo) <luoyonggang at gmail.com> wrote: > The patch is for version 77784 > And it's fixed the cmake for eclipse win32 mingw makefile output:) > Also a warning in VS 2008 on stub.c > Hope someone apply this patch. > And those files that place the > <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> > Before

The patch is for version 77784 And it's fixed the cmake for eclipse win32 mingw makefile output:) Also a warning in VS 2008 on stub.c Hope someone apply this patch. And those files that place the <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> Before <title> is just because of in tag title may contains strange characters such as Chinese

Hi, I've cross-compiled musl-libc to arm binaries with clang. It needs functions from static runtime library "libcompiler_rt.a". I tried to build compile_rt outside the llvm source tree. Using command like "make clang_linux", I can easily build "libcompiler_rt.a" for my host machine, which is X86_64. But how can I *cross-compile* the compiler_rt runtime

Dear all, When I tried to compile LLVM, I found these annoying warnings. I actually found several other, but this patch deals with the trivial ones Regards, Rizky Herucakra -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100612/d2171b49/attachment.html> -------------- next part -------------- A

Hello everyone, Since yesterday I've been toying around with LLVM on my FreeBSD box at the office. As an ideal test I tried to compile a FreeBSD kernel. I've just sent the following message to the FreeBSD Hackers list, which contains some stats on compile time, binary size, etc. Links: http://lists.freebsd.org/pipermail/freebsd-hackers/2008-May/024600.html

Hi folks, I just tried to build LLVM on FreeBSD/arm. It looks like libSystem doesn't build and requires the following hack: --- lib/System/Memory.cpp +++ lib/System/Memory.cpp @@ -61,7 +61,7 @@ for (intptr_t Line = StartLine; Line < EndLine; Line += LineSize) asm volatile("icbi 0, %0" : : "r"(Line)); asm volatile("isync"); -# elif defined(__arm__)

Hi all, Speaking about warnings, we're seeing the following warnings when building LLVM/Clang on FreeBSD/amd64. When using GCC: http://amd64-clang-bot.qat.freebsd.org:8010/builders/freebsd-clang-amd64/builds/20/steps/compile-llvm.1/logs/warnings When using Clang: http://amd64-clang-bot.qat.freebsd.org:8010/builders/freebsd-clang-amd64/builds/20/steps/compile-llvm.2/logs/warnings -- Ed

Hi there, I'm experiencing some problems accessing some of the services on llvm.org: $ svn co https://llvm.org/svn/llvm-project/llvm/trunk svn: E200029: Couldn't perform atomic initialization https://llvm.org/bugs/show_bug.cgi?id=24734: "undef error - DBD::mysql::st execute failed: Got error 28 from storage engine" On Linux, errno 28 corresponds with ENOSPC, so my suspicion

Hi all, Is there a way to enforce STARTTLS for all connections, regardless their authentication mechanism? disable_plaintext_auth only takes care of the auth conversation, but I would like to have all communication encrypted. As far as I can see, this would only be possible when using imaps and disabling imap. However, I would like to have the other way around; disabling imaps and using imap for

On Sep 12, 2016, at 10:10 AM, Ed Schouten <ed at nuxi.nl> wrote: >> >> ---- end --- > > Just to make sure I get this straight, I can substitute 'this > Software' by the names of components provided by the LLVM project. This is the literal license text that will be included with each of these projects, so no, you cannot literally make that substitution.

On Jun 14, 2010, at 2:26 AM, Ed Schouten wrote: > Hi all, > > Speaking about warnings, we're seeing the following warnings when > building LLVM/Clang on FreeBSD/amd64. > > When using GCC: > http://amd64-clang-bot.qat.freebsd.org:8010/builders/freebsd-clang-amd64/builds/20/steps/compile-llvm.1/logs/warnings > > When using Clang: >

Hi Hans, 2016-07-30 0:57 GMT+02:00 Hans Wennborg via llvm-dev <llvm-dev at lists.llvm.org>: > There are still open merge requests and bugs, but I'd like to get the > real testing started to see where we're at. Just to double-check, is this bug also on people's radar? It causes Clang to crash when trying to build a fair number of Open Source packages/libraries. In my

Hello List, I want to allow plain text passwords only on ssl/tls. Is it possible to have: auth default { mechanisms = cram-md5 ntlm ...... } and then over-ride this when connection is ssl/tls to allow plain and login? I have tried adding "mechanisms = plain login cram-md5 ntlm" to "protocol imaps{}" as an example but I get an error that the protocol does not

On 2020-05-27 00:23, Frank Cox wrote: > On Wed, 27 May 2020 00:05:34 -0400 > mark wrote: > >> The one from their website: file setup.exe >> setup.exe: PE32 executable (GUI) Intel 80386, for MS Windows, Nullsoft >> Installer self-extracting archive > > Are you sure you have 32-bit wine and not 64-bit wine since your installer says 80386? > Really annoying that