search for: compliant

I'm checking back in to see if samba is FIPS compliant, as in using FIPS compliant algorithms ? Can it be built with openssl, which is FIPS compliant ? We're currently running 4.7.5. Please let me know. Regards, Mike

Thanks for the quick reply Jeremy. We have other FIPS compliant libraries, which check for, and ensure the proper FIPS compliant algorithms are used. Is there a link option to specify this kind of library ? ~ Mike -----Original Message----- From: Jeremy Allison <jra at samba.org> Sent: Tuesday, October 2, 2018 2:08 PM To: Tompkins, Michael <Michae...

So....apparently I have some messages which are not RFC compliant sitting in my mailboxes (mostly older ones), and I have some software which is refusing to handle such messages. 1. Does anyone know of a nice way to verify that all my messages are compliant/find those that aren't? (I suppose I could use the existing failing software, but I was hoping for som...

Is samba FIPS compliant ? If so, does it need to use SMB2/SMB3 to be FIPS compliant ? We do not use the Heimdal Kerberos libraries that can be compiled with the samba release. We are use samba 4.0.7. Regards, - Mike ?

On 11/2/2012 11:53 AM, Michael Ilseman wrote: > > > I think Dan was making two points with his example. Dan, correct me if I misrepresent your example, but image a situation where a target has two instructions to choose between in order to perform the operation. The first is IEEE compliant, but the second isn't compliant in how it operates over NaNs (quiet or otherwise). For whatever reason, the second is preferred when we know inputs are not NaN. > > The first point is that I didn't specify if the N bit would allow the target to choose the non-compliant operation. >...

We are looking for a FastCGI protocol compliant RoR executable that can be used to host RoR in FastCGI mode. However, neither Ruby.exe nor Rubyw.exe appear to work with the FastCGI protocol (http://www.fastcgi.com/devkit/doc/fcgi-spec.html). Perhaps we are missing specific command line switches, or environment variables necessary to make this...

Dear R-devel, Recently I ran into trouble installing two separate packages, nloptr and ncdf4, both due to the same issue: they have scripts that have the shebang `#! /bin/sh', but have bashisms in them, i.e. non-POSIX-compliant bash scripts. I use dash [1] as my shell environment, since it's about 4x as fast as bash. It looks like it's recently also become the default shell for Debian (and thus Ubuntu). It took quite a while to figure out what the issue was in great collaboration with the author of ncdf4 (CC)....

On Fri, Aug 14, 2015 at 11:42 AM, Patrick Masotta via Syslinux <syslinux at zytor.com> wrote: >>>>> > website (meaning, HP could test their firmware to be compatible with > Syslinux and with non-Windows OSes). If the HP firmware could be made > (more) compliant with UEFI specs, or if it could be improved and still > be compliant with UEFI specs, wouldn't that be helpful to everyone > involved? > > Regards, > Ady. > <<<< > > HP (and the rest) should just check their firmware against the "UEFI standard"...

...files in the directory listing when it received the command "LIST -a". Reading RFC 959, it appears that the LIST command does not officially support any flags. I found the "force_dot_files" directive in the vsFTPd config file. Enabling the directive appears make vsFTPd RFC compliant with regards to responding to LIST -- returning all files and directories (even "dot files"). So I guess my question is: can anyone confirm that "LIST -a" really is contrary to the RFC? If so, does anyone know why $upstream_vendor would ship a default conf file that is stan...

...ction should > disregard those bits? I'd lean towards undefined behavior, but I don't > have a good feel for LLVM's overall design for undefined behavior, > poison values, etc. I still don't understand Dan's concerns, but a target that traps on a quiet NaN is not IEEE compliant. IEEE754 requires that quiet NaNs get propagated through operands to the results without causing exceptions. -Krzysztof -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation

...disregard those bits? I'd lean towards undefined behavior, but I don't >> have a good feel for LLVM's overall design for undefined behavior, >> poison values, etc. > > I still don't understand Dan's concerns, but a target that traps on a quiet NaN is not IEEE compliant. IEEE754 requires that quiet NaNs get propagated through operands to the results without causing exceptions. > I think Dan was making two points with his example. Dan, correct me if I misrepresent your example, but image a situation where a target has two instructions to choose between in ord...

...r in any bootloader in general), and such improvements could perhaps see their way into the "Linux" category of downloads in the HP support website (meaning, HP could test their firmware to be compatible with Syslinux and with non-Windows OSes). If the HP firmware could be made (more) compliant with UEFI specs, or if it could be improved and still be compliant with UEFI specs, wouldn't that be helpful to everyone involved? Well, as I said, crazy concept :D. At this point, I can only hope. Regards, Ady. > _______________________________________________ > Syslinux mailing l...

...tp://www.faqs.org/rfcs/rfc2087.html) describes the response like as: STORAGE: Sum of messages' RFC822.SIZE, in units of 1024 octets MESSAGE: Number of messages As you can see, the response "MESSAGES" differs from the specified "MESSAGE" which leads to parsing issues on RFC compliant IMAP client implementations. Using *:message=1337 throws a configuration error on Dovecot startup. dovecot-1.1.6/src/plugins/quota/quota.h /* Number of messages. */ #define QUOTA_NAME_MESSAGES "MESSAGES" Greetings, ?Martin -------------- next part -------------- A non-text attachment w...

...CR LF (RFC 4253, section "4.2. Protocol Version Exchange"), but with CR only. I tried two different client versions, with the same result: Openssh V3.8.1p1 (Debian stable package ssh 3.8.1p1-8.sarge.4) Openssh V4.3p2 (Debian testing package openssh-client 4.3p2-3) Is (portable) OpenSSH compliant with RFC 4253? Is it a bug fixed in V4.4? Are Debian packages not compliant with (portable) OpenSSH official packages? Did anybody experience something like this? Thanks in advance, Paolo -- Paolo Vicario, Centro Servizi Informatici e Telematici (CSIT) Universita' degli Studi di Udine e-mail...

It seems we have a few email addresses that are not RFC 5322 compliant, and now that we've started using sieve these are failing. The problem is that we have a few addresses with leading, trailing or double dots in the local part: jan..frode at tanso.net .janfrode at tanso.net janfrode. at tanso.net I believe these has been working fine with everything else i...

Hi, How do I make OpenSSH FIPS compliant? Will just compiling with OpenSSL version that is built with a FIPS validated module, make it FIPS compliant? I see sshd linked to both libcrypt and libcrypto. How do I make sure sshd runs only in FIPS mode? Appreciate any help. Thanks, Chandana

...Fixed String.match implementation for non-global regexps. Joel Holdsworth (29): configure: Maintainer mode requires icotool v0.29.0 or newer. configure: Maintainer mode requires imagemagick. tools: Installed new icon build script. user32: Replaced oic_winlogo.ico with Tango compliant icon. user32: Replaced oic_bang.ico with Tango compliant icon. user32: Replaced oic_hand.ico with Tango compliant icon. user32: Replaced oic_note.ico with Tango compliant icon. user32: Replaced oic_ques.ico with Tango compliant icon. user32: Replace oic_sample.ico with...

...d view where "UDP hole punching" only works in 50% of cases, which is the number I pulled. To be honest I am not quite sure how that follows from the first or second graph. My best guess is that it's simply a direct application of probabilities: if the probability that a NAT is "compliant" is 70%, then the probability that *both* NATs at both ends of the tunnel are "compliant" is only 50% (0.70*0.70). Indeed both NATs need to be compliant in order for UDP hole punching to work. However, that indeed means that my original post was badly worded - I should have said &qu...

...eman wrote: > >> >> >> I think Dan was making two points with his example. Dan, correct me if I >> misrepresent your example, but image a situation where a target has two >> instructions to choose between in order to perform the operation. The first >> is IEEE compliant, but the second isn't compliant in how it operates over >> NaNs (quiet or otherwise). For whatever reason, the second is preferred >> when we know inputs are not NaN. >> >> The first point is that I didn't specify if the N bit would allow the >> target to choos...

asterisk-users-bounces@lists.digium.com wrote: > Is there anyone else with the same problem? Yes, we've seen the same problem. We have found a work around, but I'm unable to to look into it today. -- Andreas Sikkema Rits tele.com Van Vollenhovenstraat 3 3016 BE Rotterdam t: +31 (0)10 2245544 f: +31 (0)10 2245540