Curl Solaris 10 Sparc |BEST| Download
Argelia Long
I currently have curl 7.28.0. I have to upgrade to latest. I dont have yum instead have pkgadd. how do I do? I tried to do pkgadd by downloading latest pkg but it installs under /opt/csw/bin. I need under /usr/bin
At the moment this will give you curl v7.45 which is at least fairly recent. It will install in /usr/bin as you request. If you want the cutting edge then I don't think you have any other option than to build yourself.
Now ./x.py build fails with:...downloading -lang.org/dist/2020-11-18/rust-std-beta-sparcv9-sun-solaris.tar.gz######################################################################### 100.0%extracting /opt/rust/build/cache/2020-11-18/rust-std-beta-sparcv9-sun-solaris.tar.gzcurl: (22) The requested URL returned error: 404
The error is happening while trying to download the hash of the rustc component for the sparcv9-sun-solaris target, which is expected since we don't support host tools for that target. Our CI is not building the compiler for that platform, but just the standard library for cross-compiling.
I hope I have the correct venue for a question on retrieving oracle/solaris 10_Recommended.zip files using either wget or curl. I would like to be able to use either wget or curl to pull down the 10_Recommended.zip patch clusters and possibly automating the process on a quarterly basis. When I use either wget or curl it seems I have several issues a) looks like I can authenticate properly with my credentials to the Orion/Services/download location and there does not appear to be any firewall issues b) from what I am seeing it looks like a cookie issue, no cookie being passed to the wget/curl session after my initial authentication with my valid credentials. Does anyone know of a way I can accomplish this download using wget or curl, or can this only be done through gui/https authentication, any help or insight would be greatly appreciated.
Buenos días comunidad queria saber si es posible instalar el splunk en solaris 11.4, si correcto me podria proporcionar los comandos necesarios para realizar la instalacion se lo agradezco (soy novato)
Yes, Sure.
1) On the UF download page, you can find the curl command for downloading the UF agent. copy that curl command and run it in your Solaris, it will download the UF agent package.
Good morning community wanted to know if it is possible to install the splunk in solaris 11.4, if correct could provide me with the necessary commands to perform the installation I appreciate it (I'm newbie)
thank u for ur response my friend its usefull but i know only the big pack its avaible for solaris thats what i need and thats what im using on a red hat and now i want to install on a Solaris 11.4 if u lknow how i can make via Terminal on solaris for install and download i will apreciated
I have control of my client machine but not of the server so if I can avoid it, it would save trouble. I believe I need a .pem file and need a root certificate since using curl to access the server results in unable to get local issuer certificate.
IF your curl was built to use OpenSSL -- as you tagged but which is not the only option for curl, verify with curl -V -- AND the server is correctly serving any/all intermediate cert(s), THEN to trust the server curl-with-openssl needs a local 'truststore' containing the root cert for the server's cert chain (NOT the server's cert itself) in PEM format. (Some other SSL/TLS implmentations will accept nonroot anchor(s), but older versions of OpenSSL cannot do so at all, and even 1.0.2 doesn't do so by default.)
METHOD 0: maybe already there. Packages of curl often include a 'bundle' of widely-trusted CA roots such as Symantec GoDaddy etc., or link to another package that does (typically named something like ca-bundle or trusted-cas). The format(s) of the certs in such a bundle depend on the SSL/TLS library(ies) you use; check curl -V as above. Check if you have such a bundle installed, and if so whether your curl is using it. If you don't have or can't get a package (including the case you build curl yourself) AND use OpenSSL, curl upstream has a bundle of CA roots extracted from Mozilla NSS/Firefox extracted into the concatenated-PEM format needed for OpenSSL (and a tool to do this yourself).
openssl commandline need not use the same default truststore location(s) as curl -- and even if it does, until recent versions the s_client command had a bug that didn't use the default truststore correctly. If you do have a concatenated-PEM bundle, specify it to s_client with -CAfile bundlefile and see if that makes a difference.
Take this file (copy to the curl machine if you created it somewhere else) and either add it to your truststore (depends on your packaging system; may be a simple as concatenating it to the existing concatenated-PEM file) or specify it by itself to curl with option --cacert filename.
According to the curl source code, that message shows up on Mac / iOS builds when curl isn't able to set the TCP keepalive option on the socket. I can't tell you why it wouldn't be able to set that option, though. Could be something to do with the NIC, or some networking software or drivers.
Node isn't available for sparc, and I can't see that changing.
The problem isn't Node as such - most of the Node-specific code is portable. The underlying V8 javascript engine simply hasn't been ported to sparc so, unless someone does that work (and it's likely to be quite a bit of work), Node.js will never be available for sparc.
python setup.py build_ext --curl-config=/usr/local/bin/curl-config
Using /usr/local/bin/curl-config (libcurl 7.23.1)
running build_ext
building 'pycurl' extension
gcc -shared build/temp.solaris-2.10-i86pc-2.6/src/docstrings.o build/temp.solaris-2.10-i86pc-2.6/src/easy.o build/temp.solaris-2.10-i86pc-2.6/src/module.o build/temp.solaris-2.10-i86pc-2.6/src/multi.o build/temp.solaris-2.10-i86pc-2.6/src/oscompat.o build/temp.solaris-2.10-i86pc-2.6/src/pythoncompat.o build/temp.solaris-2.10-i86pc-2.6/src/share.o build/temp.solaris-2.10-i86pc-2.6/src/stringcompat.o build/temp.solaris-2.10-i86pc-2.6/src/threadsupport.o -L/usr/local/lib -L/usr/local/lib -L/usr/lib -L/usr/openwin/lib -L/usr/local/ssl/lib -L/usr/X11R6/lib -L/usr/local/BerkeleyDB.4.7/lib -L/usr/local/mysql/lib -L/usr/local/ssl/lib -L/usr/local/lib -L/usr/openwin/lib -L/usr/local/ssl/lib -L/usr/X11R6/lib -L/usr/local/BerkeleyDB.4.7/lib -L/usr/local/mysql/lib -lcurl -lidn -lssh2 -lssl -lcrypto -lrt -lsocket -lnsl -lssl -lcrypto -lsocket -lnsl -ldl -lz -lssh2 -lsocket -lnsl -lcrypto -o build/lib.solaris-2.10-i86pc-2.6/pycurl.so -R/usr/local/lib -R/usr/lib -R/usr/openwin/lib -R/usr/local/ssl/lib -R/usr/X11R6/lib -R/usr/local/BerkeleyDB.4.7/lib -R/usr/local/mysql/lib
collect2: ld terminated with signal 8 [Arithmetic Exception], core dumped
error: command 'gcc' failed with exit status 1
Of course, when you're using curl to interact with web services, you need to use a command that works with those services. In this example, we're just confirming the connection and asking about the services that are running.
To get a list of the options available, just use the command curl --help. The output shown below is less than a third of what you'll see, but should give you an idea about how many options are available.
Clearly, curl is not a tool that you will completely conquer in one sitting. Then again, you probably won't need to learn any more than how to use it with your web services and in your environment. But it's clearly a tool to keep in mind whether you're trying a very simple "does it respond?" test or interacting with your server using some interesting queries.
I an new to Elasticsearch and am having some start-up problems.
I've successfully installed it and am able to connect to the server and create an index.
However when I attempt to load data either via curl or the Perl Search::Elastic interface I receive
the following error message:
solaris is indeed not a supported platform (see here), but I have the feeling that this issue is more on the client side of things, as Elasticsearch misses a HTTP body to process, however my solaris skills pretty much end here. Something like set -x and more verbose output for curl would be helpful, but not sure that is supported by the shell you are using (requires bash).
When curl is given a hostname to pass along to a SOCKS5 proxy that is greater than 255 bytes in length, it will switch to local name resolution in order to resolve the address before passing it on to the SOCKS5 proxy. However, due to a bug introduced in 2020, this local name resolution could fail due to a slow SOCKS5 handshake, causing curl to pass on the hostname greater than 255 bytes in length into the target buffer, leading to a heap overflow.
First, exploiting the buffer is only possible when an application using a vulnerable version of libcurl either does not configure the buffer size in CURLOPT_BUFFERSIZE or has set it to a value less than 65541. Additional requirements:
On October 11, curl version 8.4.0 was released. Various Linux and Unix distributions are rolling out patches as well. Applications that embed libcurl will also need to update to the patched version. We anticipate that projects using libcurl will be releasing updates soon.
curl is one of the most widely used open source projects, as it is in use in a variety of applications and devices worldwide. It is deployed with Windows from Windows 10 and later as well as many Linux distributions.
curl 8.4.0 was released on October 11. The Tenable Research team began immediately working on plugin coverage to address both CVEs and will continue to release coverage as more patches are released to address these flaws. A list of Tenable plugins to identify affected systems can be located on the individual CVE page for each of the CVEs mentioned here:
9738318194