search for: tranport

Hello everyone, I am trying to write a wrapper around rsync to do some automated file sync-ing between two servers. I am using ssh as the tranport. How can I avoid the password prompt for ssh? I think I can configure ssh to not require passwords, but this would expose the obvious security risk.What are other users doing to get by this? Is there some tricks I can do in scripting that would allow me to keep the password in place and pass it to...

...(users @ domain.org) -> Works ok if I install dovecot and set the mailbox_transport to be on this machine, both with dovecot and cyrus. What I'm trying to do: Have host (b) to receive mails for that domain, and by setting it's transport_maps to be /etc/postfix/transport, and there (tranport maps) point to host (a), using ltmp: "domain.org lmtp:ip_address_machine_A:24" ("domain.org lmtp:inet:ip_address_machine_A:24" does not work, gives me "fatal: valid hostname or network address required in server description: inet:ip_address_machine_A:24") Bo...

...th However, since i wanted to verify this, I put some debugging code in openssh-3.51p1/packet.c (function packet_send2()), which can be accessed at http://mia.ece.uic.edu/cgi-bin/lxr/http/source/packet.c?v=openssh-3.5p1#L619. I conducted some tests by sending PPP packets and found out that the tranport layer (i think) just appends an extra 14 bytes to the begining of the PPP frame. The first 4 bytes of these are used to put in the packet_length and the next 1 byte is used to put in the padding_length. However the rest 9 bytes remain unused.. Question: 1. Is this observation correct? Or am i...

...46b8242ce..750b62711b01 100644 --- a/net/vmw_vsock/af_vsock.c +++ b/net/vmw_vsock/af_vsock.c @@ -416,13 +416,28 @@ int vsock_assign_transport(struct vsock_sock *vsk, struct vsock_sock *psk) return -ESOCKTNOSUPPORT; } - if (!vsk->transport) + /* We increase the module refcnt to prevent the tranport unloading + * while there are open sockets assigned to it. + */ + if (!vsk->transport || !try_module_get(vsk->transport->module)) { + vsk->transport = NULL; return -ENODEV; + } return vsk->transport->init(vsk, psk); } EXPORT_SYMBOL_GPL(vsock_assign_transport); +stati...

...e increase the module refcnt when a socket is assigned to a transport, and we decrease the module refcnt when the socket is destructed. Reviewed-by: Stefan Hajnoczi <stefanha at redhat.com> Signed-off-by: Stefano Garzarella <sgarzare at redhat.com> --- RFC -> v1: - fixed typo 's/tranport/transport/' in a comment (Stefan) --- drivers/vhost/vsock.c | 2 ++ include/net/af_vsock.h | 2 ++ net/vmw_vsock/af_vsock.c | 20 ++++++++++++++++---- net/vmw_vsock/hyperv_transport.c | 2 ++ net/vmw_vsock/virtio_transport.c | 2 ++ net/vmw_vsock/vmci_transport...

Hi all, this series adds the multi-transports support to vsock, following this proposal: https://www.spinics.net/lists/netdev/msg575792.html With the multi-transports support, we can use vsock with nested VMs (using also different hypervisors) loading both guest->host and host->guest transports at the same time. Before this series, vmci-transport supported this behavior but only using

Hi all, this series adds the multi-transports support to vsock, following this proposal: https://www.spinics.net/lists/netdev/msg575792.html With the multi-transports support, we can use vsock with nested VMs (using also different hypervisors) loading both guest->host and host->guest transports at the same time. Before this series, vmci-transport supported this behavior but only using

This series adds the multi-transports support to vsock, following this proposal: https://www.spinics.net/lists/netdev/msg575792.html With the multi-transports support, we can use VSOCK with nested VMs (using also different hypervisors) loading both guest->host and host->guest transports at the same time. Before this series, vmci-transport supported this behavior but only using VMware

This series adds the multi-transports support to vsock, following this proposal: https://www.spinics.net/lists/netdev/msg575792.html With the multi-transports support, we can use VSOCK with nested VMs (using also different hypervisors) loading both guest->host and host->guest transports at the same time. Before this series, vmci-transport supported this behavior but only using VMware