search for: _client_

...] There is nothing in the GPL that prevents a GPL compiler from producing non-GPL code. And LGPL can be statically linked against non-GPL compatible code. So that means the OpenAFS _server_, which is user-space, can be built with GPL GCC and dynamically linked against LGPL GLibC. But the OpenAFS _client_, which is kernel-space, cannot be statically linked into the GPL kernel program. [ I believe there is an OpenAFS client that is GPL, missing various IBM code. ] -- Bryan J. Smith mailto:b.j.smith at ieee.org

Hi So far when I have streamed Vorbis, the headers (the 3 first frames/packets) was not included in the stream, but communicated out of band typically in an SDP file as unparsed A-lines. Rethinking that concept, I'm wondering if it is really necessary to do it that way. Isn't it possible in a platform independent way to regenerate useable headers on the client side using just the

Why is that when you create a share, the default is 'msdfs root = yes'? Also, why is that a share that is set 'msdfs root = yes' -- or, rather, a share that does /not/ set 'msdfs root = no' -- advertises that it is a DFS root to the Linux CIFS client, /even /when 'host msdfs = no'? This sounds like A) a bug (ignoring 'host msdfs', and B) a misfeature (msdfs

Hi all, I have a centos 5 box I have setup, current with updates. (I have done this many times on centos 4). I did the yum install tftp-server, changed the /etc/xinetd.d/tftp file as shown. # default: off # description: The tftp server serves files using the trivial file transfer \ # protocol. The tftp protocol is often used to boot diskless \ # workstations, download

On 24/07/2020 12:35, Christian Naumer via samba wrote: > I can't say much about the NFS part here. However, my laptop uses SSSD > as client software and I mount our Samba shares via pam_mount and > kerberos. This all works fine. So I suspect that this should also work > with NFS. The IDs of your users need to be the same as on the server > otherwise I haven't found a

This falls under the 'getting clearcase to work with samba' category. Does anybody know if the clearcase albd server actually uses samba to access files (or anything else) on the unix side? I am having 'discussions' with rational (the clearcase people). The nt user running clearcase to access some unix-side views connects to the unix side using a set of credentials that have

..., smbd must now go > through winbind, sssd uses some of the winbind code, so it is > incompatible with winbind. > > As I said, you can use sssd for authentication, but if you want to > server files, you will have to use Samba with winbind. Hi Rowland, I was just referring to use a _client_! I am aware of the other limitations and use winbind on the server side. Regards Christian -- Dr. Christian Naumer Unit Head Bioprocess Development B.R.A.I.N Aktiengesellschaft Darmstaedter Str. 34-36, D-64673 Zwingenberg e-mail cn at brain-biotech.com, homepage www.brain-biotech.com fon +49-6...

Recently, I attempted to add what I previously suggested to this mailing list of an $SSH_USER_HOME environment variable with which to move the contents of ~/.ssh, which worked fairly well for files used by the SSH _client_ as run by the user. However, it turned out that this was effectively impossible to use in order to relocate the ~/.ssh/rc and ~/.ssh/environment files, obviously due to the fact that these are used by the sshd _server_ component, which runs as root and has no knowledge of any environment variables...

...an't. The priniciples to SmartCards are pretty simple. You send in a public key encrypted information (typically a symmetric key or maybe a challenge string), you get the information out. Then you can use that information as appropriate. The SmartCard is used only for 1 small operation on the _client_ for the user. (although you can also use them on the server too, for the services). And via PAM, you can route all sorts of authentication through it. I'll send you some links when I have time early next week (I'm on the road / in the air all weekend starting in a few minutes). There are a...

...widyono@seas.upenn.edu QAContact: rsync-qa@samba.org CC: widyono@seas.upenn.edu "list = no" correctly hides via rsync _server_::, however if one tries rsync _server_::_existing-module_/ and does not have permission, one gets @ERROR: access denied to _user_ from _client_, whereas an attempt for a non-existent module emits @ERROR: Unknown module '_non-existent-module_' If "list = no" is used for security purposes (can't think of another reason at the moment), this can be considered a security bug and thus I left severity at normal instead of l...

...ymlinks (../../foo), but absolute symlinks (/tmp/foo) produce the same behavior I will describe. I have two linux clients. - Client A runs samba 2.2.7a and follows the symlinks on the server to see the files there. All is well. - Client B runs samba 3.0.7 and tries to follow the symlinks on the _client_ machine's own filesystem! Needless to say, they don't exist on the client machine; they're on the server. Questions: 1) Is this a bug? (Is this bug 2008? https://bugzilla.samba.org/show_bug.cgi?id=2008 ) Or an intentional behavior change? 2) Short of downgrading my version of smbc...

..."context" - server-side links usually make no sense if interpreted on the client, and client-side links usually make no sense if interpreted on the server. It appears the "unix/linux extensions" are all or none. With them on, all symlinks are visible to and interpreted by the _client_. With them off, all symlinks are invisibly interpreted by the _server_ (and the client isn't even allowed to create any). How can I note which symlinks are server-side and which are client-side, and have Samba interpret the server-side ones internally yet at the same time make the client-side...

Hi, We would like to mount a Linux server running samba using a cifs mount from a linux client (linux->linux) and still be able to access the extended attributes. Acl's work on the native filesystem, however when we mount the samba server on the Linux client using mount -t cifs //localhost/test test -o username=xxx Then the extended attributes are no longer visible, only the default

Hi, I am running dovecot 1.2.11 on mac osx 1.5.8. Everything works perfectly with the application-level firewall off, but enabling the application firewall prevents dovecot connections. I have tried explicitly authorizing dovecot in the firewall, but it does not work. I have searched everywhere I can think of to look, and haven't found a solution, but have seen a couple other

...derclients). Clients </span><span class="lines">@@ -106,43 +102,55 @@ </span><span class="cx"> "ArtProvider#get_bitmap":artprovider.html#ArtProvider_getbitmap </span><span class="cx"> returns identical bitmap for different _client_ values! </span><span class="cx"> </span><del>-h4. See also - -See the "artprov":sampleartprovider.html sample for an example of ArtProvider usage. - </del><span class="cx"> h4. Derived from </span><span class="cx"...

...y strict "only the user may be able to read the private key file" check hurts us quite a bit here. It's also OpenSSH enforcing its own policy that doesn't match our threat model at all. sshd has a way to explicitly disable those checks (StrictModes no) for authorized_keys, but the _client_ (of all things) refuses to load private keys that are group-readable (but not world-readable) with no way to tell it that, yes, this is exactly what we want and need. We're currently using the work-around of running "ssh-add - < foo/id_rsa", but that's just that: a work-around...

...on the server, not trying adhoc, manual, kludge in things. And if you're old MS CIFS/PDC, get off of it. Get your network to NsDS (now Red Hat Directory Server) before it's too late -- even if just for your UNIX portion. Or at least introduce 23+ year-old NIS for things. Golden Rule: The _client_ is always right. Always present the _native_ interfaces of the client OS from a server when it comes to: 1) naming 2) directory/store 3) authentication 4) file services Whether you are a true UNIX, e.g., DNS/NIS, NIS, hash, NFS (NIS) DNS/NIS, NIS, Kerberos, NFS (NIS-Kerberos) NIS+, NIS+, RS...

Dear All: --- Summary, especially for openssh list (to test/reproduce): THANK YOU for all your help. Please extract into /home/username/nx on both host and client. cp ssh to a file named mxssh in that directory. Run (with an _n_ below) Start server on the remote host by typing ./server & Now do: ./nxssh hostname If you killall client on the remote end, it reconnects "seamlessly"

HI all, When CentOS 7 was created things like SSLv2 TLSv1 TLSv1.1 etc... were all OK, but now they have fallen out of favor for various reasons. Updating to CentOS 7.7 does not automatically disable these types of items from apache - is there a script that is available that can be ran to bring a box up to current "accepted" levels ? Or is that an edit by hand, do it yourself on all your

Hi, On Fri, Jan 9, 2015, at 10:48 AM, Tim Rice wrote: > My ssh_config has > Host * > HostbasedAuthentication yes > EnableSSHKeysign yes > NoHostAuthenticationForLocalhost yes > > NoHostAuthenticationForLocalhost is not necessary. > The one you are missing is EnableSSHKeysign. > > Additionally, you made no mention of your ssh_known_hosts files. Make > sure