similar to: /dev/urandom

ssh won't compile on this platform log: gcc -g -O2 -Wall -I/usr/local/ssl/include -DETCDIR=\"/usr/local/etc\" -DSSH_PROGRAM=\"/usr/local/bin/ssh\" -DSSH_ASKPASS_DEFAULT=\"/usr/local/libexec/ssh/ssh-askpass\" -DHAVE_CONFIG_H -c atomicio.c -o atomicio.o In file included from config.h:294, from bsd-misc.h:39, from includes.h:91,

On Thu, Jan 13, 2000 at 17:34:10, Andre Lucas wrote: > Subject: /dev/urandom > On Thu, Jan 13, 2000 at 09:24:01AM -0700, SysProg - Nathan Paul Simons wrote: > > On Thu, 13 Jan 2000, Ben Taylor wrote: > > > > > On Thu, 13 Jan 2000, Max Shaposhnikov wrote: > > > > why ssh1.27 doesn't requre /dev/urandom on solaris? > > > > i think the

I feel very silly asking this, because I saw the answer to this question one time and can't remember what it was. OpenSSH uses /dev/urandom or /dev/random which Solaris does not have (verified with a call to the Sun software folks). How do I make OpenSSH happy with a Solaris substitute for /etc/urandom? Thanks Tim Nibbe Supervisor of System Administration Sprint IP Dial Support Services

Has anyone had success with getting /dev/random to work after installing SUNWski? After I install the pkg and start /etc/ init.d/cryptorand, the /dev/random file remains 0 bytes. I am running Solaris 2.8 - David

There was some discussion recently about the Solaris /dev/random support that can be downloaded from Sun's patch archive as part of a patch to the Sun Web Server 1.0 product. The SUNWski package is the interesting bit that purports to provide /dev/random. It was noted that domestic and international versions of the patch existed and that only the international (no encryption) version was

Every case is different, but yes, as I said - I would like to take a closer look at the problem again, it might be the case that we don't need this complexity in this particular case, but want to double check. But yeah, in general I agree with you! On Thu, May 9, 2019 at 6:09 PM Jake Ehrlich <jakehehrlich at google.com> wrote: > I think that pretty much hits the nail on the head.

I've installed Sun's SUNWski package on Solaris 8 (32-bit) that provides a /dev/random interface. It appears to as cat'ing it gives me a bunch of well, random data. However, when I ran my configure, it gives me the WARNING.RND message to the effect that I'm using the built-in. I've seen allusions on this list to building openssl with to get random support, so I rebuilt it

Yeah, not sure either. The discussion about minimum compatibility usually comes down to what version is available on long-term OS releases. On Fri, Oct 2, 2020 at 12:38 PM George Rimar <grimar at accesssoftek.com> wrote: > > Is the code currently broken? > > > I don't know. Perhaps the code is fine, I did not try to compile LLVM > with all that compilers > >

On Fri, Oct 2, 2020 at 1:48 AM George Rimar <grimar at accesssoftek.com> wrote: > Thanks, David! > > > Few minor additions to the topic: > > > > I'm not sure which MSVC version on godbolt would be "MSVC 2017" that > the LLVM docs refer to > > > I've found that the minimal available version of MSVC on > godbolt is "WINE MSVC 2015:

Many thanks for the reply, right, this is what the discussion is about. On Mon, Sep 28, 2020 at 10:57 AM David Blaikie <dblaikie at gmail.com> wrote: > To clarify, this is a discussion around whether given some move-only type > X, implicitly convertible to Y and the code "Y func() { X x; return x; }" > is that valid in LLVM? (and, as a corollary, if the type isn't

On Thu, Oct 1, 2020 at 2:08 AM George Rimar <grimar at accesssoftek.com> wrote: > FWIW, I've performed an experiment with the code below at godbolt. > (used -O2, https://godbolt.org/z/nY95nh) > > ``` > #include <vector> > #include "llvm/Support/Error.h" > > llvm::Expected<std::vector<int>> foo() { > std::vector<int> V; >

Hi Jake, many thanks, yea, I have very similar feelings / thoughts. After some thinking it seems to me that this discussion/problem which I have brought up is, in fact, more relevant to the tools which really need a robust mutable model of an object file (like objcopy, strip, install_name_tool, etc), but the particular case of "lipo" might be simpler, I need to double check that / will

Hey everyone! Objcopy is a powerful tool that allows one to modify object files in various manners, for example, modify symbols / symbol tables or copy / remove particular parts of a binary. It also serves as a basis for the strip tool. Currently, llvm-objcopy only supports ELF files while binutils' objcopy can handle Mach-O files as well. Besides extending the existing tool to support Mach-O

*bitcode_strip* is a utility which is used to manipulate (leave / remove) bitcode segments in a Mach-O file. It is a part of Apple’s cctools and it is also distributed with Xcode. The man page of the tool is available here https://www.manpagez.com/man/1/bitcode_strip/. The functionality of *bitcode_strip* naturally maps onto llvm-objcopy’s model and requires only minimal additions to it.

(Again: please send these things to R-devel or R-help !!) >>>>> "Yoko" == Yoko Wong <yoko@math.ubc.ca> writes: Yoko> Dear Martin, Yoko> I run into following errors when I try to compile R-0.63.1 on Yoko> Solaris7. >From all I see in the following, this looks like a Solaris 7 bug. I don't have access to this OS. Anyone else ?

Hey everyone! In October/November 2018 I started the implementation of llvm-objcopy for MachO with the long-term plan to build some popular binary-level tools on top of it. That effort stopped at the stage where some boilerplate code for reading/writing MachO files was reviewed & committed to LLVM/tools/llvm-objcopy. Later I started working on llvm-lipo (a drop-in replacing for the tool

Hello everyone! It looks like in the LLVM codebase (including subprojects) there are some inconsistencies in how values are returned from functions with the following (or similar) signature: Expected<std::vector<int>> createVector() { std::vector<int> V; ... } It would be interesting to find out your opinion on this. After some investigation I have found

Hey Michael, I completely agree that setting the rpath properly the first time around is much preferred. But, changes to the binary, particularly during development is much quicker. Prebuilt libraries which are being repackaged is one use case that is missed. In the past, I’ve even used it to repair am incorrectly built library which was missing the library name. There are a few different

Hey everyone! Recently there has been some progress on LLVM-based tools for manipulating MachO binaries: llvm-objcopy has been gaining a lot of important bits to support MachO (it's relatively close to the point where one can implement the strip-like functionality), llvm-lipo is functional and supports most of cctools' lipo options (https://llvm.org/docs/CommandGuide/llvm-lipo.html). There

Hi! I've added member to a queue like this, from queues.conf: member => SIP/1070@peername It works OK. But, after restaring I see in show queue that Members: SIP/1070@peername (Invalid) ... What does it mean? Why is it Invalid? BTW, reload command fixes it, so the member receives queue calls. Thanks! PS. 1.2.9.1 -- DSS5-RIPE DSS-RIPN 2:550/5068@fidonet 2:550/5069@fidonet