similar to: [PATCH nbdkit] Add cainfo and capath options to curl plugin

Displaying 20 results from an estimated 300 matches similar to: "[PATCH nbdkit] Add cainfo and capath options to curl plugin"

2020 Jul 20
1
Re: [PATCH nbdkit v2] curl: Implement header and cookie scripts.
On 7/15/20 3:53 PM, Richard W.M. Jones wrote: > This rather complex feature solves a problem for certain web services > that require a cookie or token for access, especially one which must > be periodically renewed. > > For motivation for this feature see the included documentation, and > item (1)(b) here: > >
2020 Jul 14
3
[PATCH nbdkit RFC 0/2] curl: Implement authorization scripts.
This is an RFC only, at the very least it lacks tests. This implements a rather complex new feature in nbdkit-curl-plugin allowing you to specify an external shell script that can be used to fetch an authorization token for services which requires a token or cookie for access, especially if that token must be renewed periodically. The motivation can be seen in the changes to the docs in patch 2.
2020 Jul 14
0
[PATCH nbdkit RFC 2/2] curl: Implement authorization scripts.
This rather complex feature solves a problem for certain web services that require a cookie or token for access, especially one which must be periodically renewed. For motivation on this see the included documentation, and item (1)(b) here: https://www.redhat.com/archives/libguestfs/2020-July/msg00069.html --- plugins/curl/nbdkit-curl-plugin.pod | 120 +++++++++++ plugins/curl/Makefile.am
2020 Jul 15
2
[PATCH nbdkit v2] curl: Implement header and cookie scripts.
Evolution of this patch series: https://www.redhat.com/archives/libguestfs/2020-July/thread.html#00073 Instead of auth-script, this implements header-script and cookie-script. It can be used for similar purposes but the implementation is somewhat saner. Rich.
2020 Jul 15
0
[PATCH nbdkit v2] curl: Implement header and cookie scripts.
This rather complex feature solves a problem for certain web services that require a cookie or token for access, especially one which must be periodically renewed. For motivation for this feature see the included documentation, and item (1)(b) here: https://www.redhat.com/archives/libguestfs/2020-July/msg00069.html --- plugins/curl/nbdkit-curl-plugin.pod | 142 ++++++++++++
2014 Nov 01
5
Pregunta (creo que simple) para usar twitteR
Hola Alfonso, buenos días: Lo he probado pero no me va, eso sí ha cambiado el error, el código utilizado es: library(ROAuth)library(twitteR) download.file(url="http://curl.haxx.se/ca/cacert.pem", destfile="cacert.pem") reqURL <- "https://api.twitter.com/oauth/request_token"accessURL <- "http://api.twitter.com/oauth/access_token"authURL <-
2020 Feb 27
0
ANNOUNCE: nbdkit 1.18 - high performance NBD server
I'm pleased to announce the release of nbdkit 1.18, a high performance plugin-based Network Block Device (NBD) server. Key features of nbdkit: * Multithreaded NBD server written in C with good performance. * Minimal dependencies for the basic server. * Liberal license (BSD) allows nbdkit to be linked to proprietary libraries or included in proprietary code. * Well-documented, simple
2013 Jul 08
0
"error setting certificate" issue in R-studio
Hi all, I'm a newbie to R and I can't figure out how to fix this error I keep getting in R-studio: > "error setting certificate verify locations:\n CAfile: \n CApath: none\n" Error in twInterfaceObj$doAPICall(cmd,params,"GET",...) : Error: error setting certificate verify locations: CAfile: CApath: none I'm trying to use the twitteR package to gather tweets
2013 Nov 22
1
Descargar tweets con package twitteR
Hola a tod@s! Estoy dando mis primeros pasos con R, y mi objetivo es conseguir descargar tweets de cuentas concretas de twitter. Encontre documentación sobre el package twitteR, y he intentado aplicarlo, pero siempre tengo problemas a la hora de conseguir la autentificación con OAuth. Este es el código que estoy utilizando: options( RCurlOptions = list(verbose = TRUE, proxy =
2013 Oct 30
2
Re: Using certtool to generate certificates for ESXi
Hi Daniel, thanks for the reply - The procedure I use is the same as I use for XenServer, and the certificate exchange works just fine. The only thing I'm a bit unclear on, is the location of the CA cert, which in the case of XenServer, I simply put it in /etc/pki/CA. And when I start the libvirtd daemon, it successfully picks it up. If I put the Server key and cert in /etc/vmware/ssl for
2014 Nov 01
2
Pregunta (creo que simple) para usar twitteR
Hola comunidad, ¿Qué tal? Tengo una duda que creo que es sencilla, pero me veo algo torpe. Estoy tratando de darme de alta para poder acceder, vía R a la api de Twitter, soy un poco novato en esto y por esto lanzo la pregunta. Aunque ya me han ayudado y me han pasado alguno link del pasado, aún no consigo dar con la solución que seguro es algo que se me escapa He usado este código
2009 Jun 10
1
[PATCH] add cmd line option for server vnc port
--- internal.h | 3 +++ main.c | 3 +++ tunnel.c | 7 ++----- 3 files changed, 8 insertions(+), 5 deletions(-) diff --git a/internal.h b/internal.h index 80e675e..bd65922 100644 --- a/internal.h +++ b/internal.h @@ -71,6 +71,9 @@ extern gboolean check_cert; /* server we're connecting to */ extern const char* hostname; +/* port which to connect to the server via vnc */
2012 Nov 08
1
twitteR return error message
I am new to the packge twitteR when using this package I came across several problems, can anybody help me on those problems? Many Thanks rm(list=ls()) library(bitops) library(RCurl) library(rjson) library(twitteR) library(digest) library(ROAuth) requestURL <- "https://api.twitter.com/oauth/request_token" accessURL =
2016 Nov 10
2
service doveadm : ssl problems
Hello, I'm using dovecot 2.2.13 on Debian stable. My users are authenticated through PAM, and stored in an LDAP backend I'm trying to set-up replication with ssl, following (mainly) this : http://wiki2.dovecot.org/Replication 1) I only diverted from the instructed setup by not setting "doveadm_port = 12345", as it would give me errors of the like: > Fatal:
2015 Jul 27
2
LMPT SSL
Hello, I tryed to eneble TLS connection from postfix to dovecot lmtp. Unfortunely I have problem with certificate, postfix shows, 2015-07-27T12:51:15.025333+02:00 k30 postfix/lmtp[4572]: Untrusted TLS connection established to 192.168.67.30[192.168.67.30]:24: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits) I checked certs by openssl s_client: #openssl s_client -connect
2009 Jul 23
1
viewer updates for fedora submission
This patchset provides updates to the viewer in preperation for its fedora submission. Included are patches cmd-line parameterizing hostname/user/pass/vm, the addition of a man page, cleanup of the project's structure, and updates to the spec.
2009 Jul 13
0
[PATCH viewer] permit hostname / username / password / vm to be passed in via the cmd line
passing in --hostname <value> will bypass the hostname form passing --username <value> --password <value> will bypass the login form passing in --vm <name> will attempt to connect to the vm on login --- internal.h | 9 ++++- main.c | 100 +++++++++++++++++++++++++++++++++++++++++++++++---------- wui_thread.c | 15 +-------- 3 files changed, 90 insertions(+),
2018 Jul 20
4
autogenerated self-signed certificate problem
Hi people, i have a problem with trying ldaps i use autogenerated self-signed certificate, i write in smb this: tls enabled = yes tls keyfile = tls/key.pem tls certfile = tls/cert.pem without cafile when i try to verify with: openssl verify /usr/local/samba/private/tls/myCert.pem it said me unable to verify the first certificate and if add -CApath works! and finally when i try from another
2012 Mar 19
0
Sankey Diagrams in R
Dear R-list, I am trying to visualize where the dropout happens in our patient flow. We are currently using traditional flowcharts and it bothers me that I can't visualize both the percentage and the flow in one diagram. The other day I came across some interesting diagrams doing exactly what I wanted, they had both flow and percentages visualized on one diagram. Here is some nice examples
2011 Feb 04
2
All DomU failing SSLv3 handshake (curl, apt-get, wget, etc.) but OK on Dom0
Hi, First of all I''ve googled this subject a lot (several hours) but right now I''m simply stuck. All my 4 DomU fails SSL handshake: > niklas@stats:~$ curl -vI https://graph.facebook.com > * About to connect() to graph.facebook.com port 443 (#0) > * Trying 69.63.181.58... connected > * Connected to graph.facebook.com (69.63.181.58) port 443 (#0) > * successfully