search for: widely

Thanks - that much I (pretty much) got. Its really the "wide links" option that isn't well distinguished/clarified. *insecure* wide links is much more clear, although the detail you've given helps a lot. What exactly is the "ordinary" "wide links = yes" option going to do (with or without Unix extensions), and how does it compare/how much exposure to

Hi all Since we changed our installation from Samba 3.x to 4.x (currently 4.2.5 on Solaris 11.1), we repeatedly encounter the following 'widelinks_warning', originating from Windows Server 2012 R2 RDS clients: [2015/10/29 15:50:38.837702, 0] ../source3/param/loadparm.c:4306(widelinks_warning) Share 'data' has wide links and unix extensions enabled. These parameters are

The Wine development release 5.19 is now available. What's new in this release (see below for details): - Wine Mono engine updated to 5.1.1, with WPF text formatting support. - KERNEL32 library converted to PE. - DSS cryptographic provider. - Windowing support in the new console host. - A number of exception handling fixes. - Various bug fixes. The source is available from the

> On 29 Oct 2015, at 23:22, Jeremy Allison <jra at samba.org> wrote: > > On Thu, Oct 29, 2015 at 05:27:49PM +0100, Thomas Werschlein wrote: >> Hi all >> >> Since we changed our installation from Samba 3.x to 4.x (currently 4.2.5 on Solaris 11.1), we repeatedly encounter the following 'widelinks_warning', originating from Windows Server 2012 R2 RDS

Thank you. So, If I understand correctly, "ordinary" "wide links = yes", means Samba *will* traverse an existing symlink that points outside the root of the share, if permissions allow. However because it *also* disables SMB1 Unix extensions, it *also* prevents the user from creating or modifying symlinks on the share, so in wffect it inherently prevents this being

I'd like to understand reasonably fully,, the difference between the two options "wide links" and "allow insecure wide links" in smb.conf. The docs make them sound very similar but as there are obvious security implications for anything to do with symlink scope, it's important to know what each of them allows/blocks and where they differ. Interestingly, only the

Hi, I'm wanting to exclude data more than 2 sd's from the mean before proceeding with further analyses. I've created new logical variables (a and b) and written them to the existing dataframe. I want to be able to subset the TRUE observations based on another 2 factor variable. I'm assuming this is possible, but I don't know what I'm doing wrong, as I get results that

Is there an existing option in X86_64 target code generator to emit a loop for the following code: define i4096 @add(i4096 %a, i4096 %b) alwaysinline { %c = add i4096 %a, %b ret i4096 %c } instead of: movq %rdi, %rax addq 96(%rsp), %rsi adcq 104(%rsp), %rdx movq %rdx, 8(%rdi) movq %rsi, (%rdi) adcq 112(%rsp), %rcx movq %rcx, 16(%rdi) adcq

> On 02.11.2015, at 20:25, Rowland Penny <rowlandpenny241155 at gmail.com> wrote: > > On 02/11/15 17:08, Thomas Werschlein wrote: >>> On 02.11.2015, at 16:25, Rowland Penny <rowlandpenny241155 at gmail.com> wrote: >>> >>> Well he didn't write what I asked for, can you please post your entire smb.conf, please do not use testparm, please post as

The following function compiles with -O3 into the following IR. http://llvm.org/docs/Passes.html#simplifycfg-simplify-the-cfg says - Eliminates a basic block that only contains an unconditional branch. but the first and third blocks in the compiled function only contain an unconditional branch; I would have expected them to be eliminated. What am I missing? double f(double *a) { for (int i

On Wed, Feb 28, 2018 at 08:36:14PM +0000, Stilez wrote: > Thank you. > > So, If I understand correctly, "ordinary" "wide links = yes", means Samba > *will* traverse an existing symlink that points outside the root of the > share, if permissions allow. However because it *also* disables SMB1 Unix > extensions, it *also* prevents the user from creating or

Sure, but did you even try my advice.. ?? So again.. from smb.conf unix extensions (G) allow insecure wide links (G) wide links (S) follow symlinks (S) G = Global S = Share So here you are lazy ... ( fill the dots..) ;-) Read below .... from : man smb.conf In normal operation the option wide links which allows the server to follow symlinks outside of a share path is automatically

Please educate me! First to explain: when we upgraded our Macs to 10.9 we started to get errors reading and writing files in matlab. For reasons we don't understand changing "unix extensions" to 'yes' fixed this. I have been contacted by the developers about this and they have requested I send in dumps for debugging. However I would like to get back into production in the

> On Fri, 30 Sep 2016 10:14:32 -0400 (EDT) > Thomas Schulz via samba <samba at lists.samba.org> wrote: > > > We are running Samba 4.4.6 as a file server. > > In the logs for a few client machines I see entries such as: > > > > [2016/09/29 22:36:58.862575, 0] > > ../source3/param/loadparm.c:4402(widelinks_warning) > > Share 'IPC$'

Hi there, I'm trying to use wide links with Samba 3.5.2 but setting wide links = yes in [globals] section of smb.conf or for the share in registry does not show any effect. Anybody using wide links without problems or is this a bug in Samba 3.5.2 ? Greetings, Thorsten Habich

>> On Fri, 30 Sep 2016 12:14:44 -0400 (EDT) >> schulz at adi.com (Thomas Schulz) wrote: >> >>>> On Fri, 30 Sep 2016 10:14:32 -0400 (EDT) >>>> Thomas Schulz via samba &lt;samba at lists.samba.org> wrote: >>>> >>>>> We are running Samba 4.4.6 as a file server. >>>>> In the logs for a few client machines I

Hello R users and developers, I have a general question about reshaping a wide data frame using the "reshape" command. I have a data frame consisting of 108 columns that I would like to convert to a long table and remove the metadata (embedded in the column names of the wide table) to new metadata columns in the long format. #example data frame. NOTE column names contain metadata::

Bugs item #17714, was opened at 2008-02-02 06:58 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=17714&group_id=35 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: Dale E. Edmons (linuxfan) Assigned to: Nobody (None) Summary: http://wxruby.rubyforge.org/doc/frame.html Display is too wide for even a wide lcd!

On Thu, Mar 12, 2015 at 12:33:36PM +1030, Rusty Russell wrote: > "Michael S. Tsirkin" <mst at redhat.com> writes: > > Going over the virtio mmio code, I noticed that it doesn't correctly > > return device config values in LE format when using virtio 1.0. > > Borrow code from virtio_pci_modern to do this correctly. > > AFAICT, it doesn't need to.

On Thu, Mar 12, 2015 at 12:33:36PM +1030, Rusty Russell wrote: > "Michael S. Tsirkin" <mst at redhat.com> writes: > > Going over the virtio mmio code, I noticed that it doesn't correctly > > return device config values in LE format when using virtio 1.0. > > Borrow code from virtio_pci_modern to do this correctly. > > AFAICT, it doesn't need to.