search for: cooperi

...and blue typeface). How do I create a dataset only with unique set of longitude and latitude for each species? Thanks in advance. Species_name Longitude Latitude Abies concolor -106.601 35.868 Abies concolor -106.493 35.9682 Abies concolor -106.489 35.892 Abies concolor -106.496 35.8542 Accipiter cooperi -119.688 34.4339 Accipiter cooperi -119.792 34.5069 Accipiter cooperi -118.797 34.2581 Accipiter cooperi -77.38333 39.68333 Accipiter cooperi -77.38333 39.68333 Accipiter cooperi -75.99153 40.633335 Accipiter cooperi -75.99153 40.633335 - Kumar -- Section of Integrative Biology University of Tex...

...ble OpenSSH Version: 7.1p1 Hardware: Other OS: Solaris Status: NEW Severity: enhancement Priority: P5 Component: sshd Assignee: unassigned-bugs at mindrot.org Reporter: alex+mailinglists_openssh-dev at cooperi.net Created attachment 2761 --> https://bugzilla.mindrot.org/attachment.cgi?id=2761&action=edit patch On Illumos/Solaris we can drop fine-grained privileges using setppriv, both for the sshd sandbox and also where appropriate in other utilities like sftp-server and ssh-agent. This has a...

I was involved with the issues building OpenSSH 7.2p1 to use the Solaris sandbox, but I ended up dropping out of the discussion due to being on the road for most of the last couple of weeks. Anyway, the problems persist with OpenSSH 7.2p2 when building with --with-sandbox=solaris. I found that there's an error in openbsd-compat/port-solaris.h on line 30, because the type priv_set_t

Hi, I'm not sure how interested anybody here is in this, but I've been working lately on getting rid of the horror that is SunSSH for some distros of Illumos (mostly SmartOS). One of the patches we're carrying around at the moment is one that simply drops fine-grained privileges in sshd, ssh-agent and sftp-server. Since the privilege dropping here is roughly equivalent to a more

On 11/12/15 6:24 PM, Darren Tucker wrote: > > As long as someone is willing to do the work and help with tests > (which it sounds like you are), the support doesn't compromise other > platforms or make maintenance significantly harder then I have no > objections to it going in. Sounds good to me. We're already running with this patch in (pre-)production, and I'm

On 04/04/18 21:56, Damien Miller wrote: > > I don't follow - clients always have to know that the last message sent > was, otherwise they wouldn't be able to disambiguate the shared > SSH_AGENT_SUCCESS / SSH_AGENT_FAILURE. The format of that message doesn't change though -- it's always a single byte (so you don't need that information in the function that actually

Hi, I've been reading the RFC draft for the OpenSSH agent protocol and trying to understand the extension mechanism. It seems like a client, after sending an extension message, will have to then interpret any following success (0x6) message differently according to the extension request just sent. The example with the "query" extension returning a success message with extra data

I know this is pretty left-field, but I'm working on a custom ssh-agent implementation and looking at ways to detect forwarded agent connections, with the hope to have a "confirm" mode which can apply just to those (or those, plus non-whitelisted local processes). I realise this has been discussed a bit before, but I have thought up a method which seems to be working in my tests

On 2/17/16 9:50 AM, Carson Gaspar wrote: > Solaris 10 has setppriv, but does not have priv_basicset. To work on > Solaris 10, the call would need to be replaced with the equivalent set > of explicitly listed privs: The prior art in other apps on the system seems to suggest that priv_str_to_set is a better fallback if priv_basicset is not available. I've attached a patch that seems