search for: wide

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 i...

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 incompatible. Wide links will be disabled for this sh...

...pters. Michael Stefaniuc (80): dswave: Simplify the stub WAVE IPersistStream_Load(). gdiplus: Remove superfluous cast to self. shell32: Remove superfluous cast to self. shlwapi: Remove superfluous cast to self. oleaut32: Remove superfluous casts. atl80/tests:Use wide-char string literals. browseui: Use wide-char string literals. d2d1/tests:Use wide-char string literals. comcat/tests: Use wide-char string literals. comsvcs/tests: Use wide-char string literals. d3dx10/tests: Use wide-char string literals. d3dx11/tests: Use wide...

...3: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 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 incompatible. Wide links wi...

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 p...

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 th...

...(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 obviously aren't correct. Many thanks, Paul twin.wide$a<-twin.wide$RCCT<600 & twin.wide$RCCT>480 twin.wide$b<-twin.wide$LCCT<600 & twin.wide$LCCT>480 selVarsCCT <- with(twin.wide,c('a','b')) MZCCT <- subset(twin.wide,Zygosity=='MZ',selVarsCCT) DZCCT <- subset(twin.wide,Zygosity=='DZ'...

...sp), %rcx movq %rcx, 16(%rdi) adcq 120(%rsp), %r8 movq %r8, 24(%rdi) adcq 128(%rsp), %r9 movq %r9, 32(%rdi) movq 8(%rsp), %rcx adcq 136(%rsp), %rcx movq %rcx, 40(%rdi) movq 16(%rsp), %rcx : : : What is the best strategy for lowering wide integer types/operations on x86_64 without causing code blow up? Should we the code run through a custom pass that replaces wide operations with a library function call (or alternatively a loop) before code generation? Is there any existing code that can be reused? Is there any documentation that...

...>> map untrusted to domain = yes >> >> username map script = /usr/local/samba-4.2.5/etc/samba/mapcomputers.sh >> >> shadow:snapdir = .zfs/snapshot >> shadow:sort = desc >> shadow:localtime = yes >> shadow:format = %Y%m%d%H%M >> wide links = yes >> >> vfs objects = full_audit >> full_audit:prefix = %u|%I|%m|%S >> full_audit:success = mkdir rename rmdir pwrite >> full_audit:failure = none >> full_audit:facility = LOCAL7 >> full_audit:priority = NOTICE >> >> ai...

...; preds = %vector.body, %overflow.checked %index = phi i64 [ 0, %overflow.checked ], [ %index.next.1, %vector.body ], !dbg !18 %0 = getelementptr inbounds double, double* %a, i64 %index, !dbg !19 %1 = bitcast double* %0 to <2 x double>*, !dbg !20 %wide.load = load <2 x double>, <2 x double>* %1, align 8, !dbg !20 %2 = getelementptr double, double* %0, i64 2, !dbg !20 %3 = bitcast double* %2 to <2 x double>*, !dbg !20 %wide.load8 = load <2 x double>, <2 x double>* %3, align 8, !dbg !20 %4 = fmul <2 x double...

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 modifying symlinks > on the share, so in wffect...

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 disabled when u...

...or 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 interim. Our users need to follow wide links. So being aware of the security implications we defined "allow insecure wide links = yes" so we could still follow wide links when "unix extensions = yes". Now this works great when we mount from a Linux client or PC client. But we cannot follow a wide link from the Mac...

...t; 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$' has wide links and unix extensions enabled. These > > parameters are incompatible. Wide links will be disabled for this > > share. > > > > I assume that Share 'IPC$' is some sort of automatically created share > &g...

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

...>>>> >>>>> 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$' has wide links and unix extensions enabled. These >>>>> parameters are incompatible. Wide links will be disabled for >>>>> this share. >>>>> >>>>> I assume that Share 'IPC$...

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 c...

...isiting: 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! Initial Comment: http://wxruby.rubyforge.org/doc/frame.html Display is too wide for even a wide lcd! I can almost display the functions, but it is much too wide unlike other pages. Thanks. ---------------------------------------------------------------------- You can re...

...use "natural" accessors, so we don't do byte-at-a-time. > > Cheers, > Rusty. You are right, the endina-ness is not an issue, so the commit log I wrote is wrong, but I still think the patch is required, because MMIO spec says the same as PCI. The driver MUST only use 32 bit wide and aligned reads and writes to access the control registers described in table 4.1. For the device-specific configuration space, the driver MUST use 8 bit wide accesses for 8 bit wide fields, 16 bit wide and aligned accesses for 16 bit wide fields and 32 bit wide and aligned accesses for 32...

...use "natural" accessors, so we don't do byte-at-a-time. > > Cheers, > Rusty. You are right, the endina-ness is not an issue, so the commit log I wrote is wrong, but I still think the patch is required, because MMIO spec says the same as PCI. The driver MUST only use 32 bit wide and aligned reads and writes to access the control registers described in table 4.1. For the device-specific configuration space, the driver MUST use 8 bit wide accesses for 8 bit wide fields, 16 bit wide and aligned accesses for 16 bit wide fields and 32 bit wide and aligned accesses for 32...