Displaying 20 results from an estimated 6000 matches similar to: "[Bug 934] Traverse-only directories (e.g. chmod 110) break the cd command in sftp"
2005 Jan 09
2
[Bug 934] Traverse-only directories (e.g. chmod 110) break the cd command in sftp
http://bugzilla.mindrot.org/show_bug.cgi?id=934
------- Additional Comments From opensshbugzilla at prikryl.cz 2005-01-10 03:38 -------
Hello,
I'm author of the metioned SFTP client (WinSCP).
I have been just experimenting with this issue.
For me realpath does succeed on OpenSSH server on Linux
(shell.sourceforge.net).
With OpenSSH client (sftp) I'm able to enter the
2004 Dec 06
2
[Bug 934] Traverse-only directories (e.g. chmod 110) break the cd command in sftp
http://bugzilla.mindrot.org/show_bug.cgi?id=934
djm at mindrot.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|sftp-server |sftp
Version|3.6.1p2 |-current
------- Additional Comments From djm at mindrot.org 2004-12-06 17:13
2014 Sep 09
0
[Bug 934] Traverse-only directories (e.g. chmod 110) break the cd command in sftp
https://bugzilla.mindrot.org/show_bug.cgi?id=934
Simon Deziel <simon at sdeziel.info> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |simon at sdeziel.info
--
You are receiving this mail because:
You are the assignee for the bug.
2004 Sep 21
1
[Bug 934] Traverse-only directories (e.g. chmod 110) break the cd command in sftp
http://bugzilla.mindrot.org/show_bug.cgi?id=934
Summary: Traverse-only directories (e.g. chmod 110) break the cd
command in sftp
Product: Portable OpenSSH
Version: 3.6.1p2
Platform: PPC
OS/Version: AIX
Status: NEW
Severity: minor
Priority: P2
Component: sftp-server
AssignedTo:
2013 Feb 03
3
Another "function does not return a value" problem
Here''s the function:
module Puppet::Parser::Functions
newfunction(:fact_to_array, :type => :rvalue) do |args|
args[0].split('','')
end
end
Here''s the class I''m trying to use it in:
class oms::all_config {
file { ''/var/lib/oms/config'':
source => ''puppet:///deployment/deployment'',
recurse =>
2012 May 03
2
How file store when using Btrfs on multi-devices? What happen when a device fail?
Hi, i have some questions when using Btrfs on multi-devices:
1. a large file will always be stored wholely on a device or it may
spread on some devices/partitions? Btrfs has option to specify it
explicitly?
2. suppose i have a directory tree like that:
Dir_1
|--> file_1A
|--> file_1B
|--> Dir_2
|--> file_2C
|--> file_2D
If Dir_2, file_2C on a failed device,
2013 Nov 05
1
samba-4.1.0 build failure -help with
Greetings,
I attrempted to compile samba-4.1.0 on a computer with these:-
--cpu amd64 2 cores
--os blfs linux-3.1.6, gcc-4.8.1, glibc-2.17
I ran configure like this:-
./configure
--prefix=/opt/samba4
( i.e I accepted all the defaults except the installation prefix)
then I ran make like this:-
make
BUT make ends like so:-
#---------------------------
[3807/3949] Linking
2020 Aug 03
3
Error compiling samba server in MacOS
Hi everyone,
I'm trying to compile samba from macOS Catalina from several days ago
without success, I'm a newbie on this kind of stuff over mac, so... It
will probably be a noob error, but I'm lost.
I tried to follow these couple of links, also without success:
https://medium.com/@mattmatic/compiling-samba-4-on-mac-os-x-high-sierra-24ca6a93a51c
and
2018 Mar 27
0
10 minutes between primary group change and effect on Fedora 27
On Tue, 27 Mar 2018 08:46:00 -0600
Jeff Sadowski via samba <samba at lists.samba.org> wrote:
> My smb.conf looks like so.
>
> [global]
> security = ads
> realm = MIND.UNM.EDU
> workgroup = MIND
> idmap config * : backend = tdb
> idmap config * : range = 2000-7999
> idmap config MIND:backend = ad
> idmap config MIND:schema_mode = rfc2307
2014 Aug 12
1
Samba4 and idmap_ad
Hello everyone,
I have a - maybe only cosmetical - problem. I am currently configuring two SLES servers running Samba4 as member servers in a Windows2008/2012-AD. (Yeah, poor us!) Everything went fine: installing the samba packages, getting Kerberos running, and joining the AD. But when I use id or wbinfo now to get user information I get lots of groups which cannot be mapped a GID and thus are
2015 Jan 13
2
Is there any problem that can arise from remapping gidNumber?
On 01/13/2015 10:41 AM, Rowland Penny wrote:
> On 13/01/15 15:11, John Lewis wrote:
>> On 01/13/2015 09:23 AM, Rowland Penny wrote:
>>> On 13/01/15 14:06, John Lewis wrote:
>>>> On 01/13/2015 06:35 AM, Rowland Penny wrote:
>>>>> On 13/01/15 11:33, John Lewis wrote:
>>>>>> This morning I remapped gidNumber from primaryGroupID to
2018 Mar 27
2
10 minutes between primary group change and effect on Fedora 27
On Tue, Mar 27, 2018 at 9:15 AM, Rowland Penny <rpenny at samba.org> wrote:
> On Tue, 27 Mar 2018 08:46:00 -0600
> Jeff Sadowski via samba <samba at lists.samba.org> wrote:
>
>> My smb.conf looks like so.
>>
>> [global]
>> security = ads
>> realm = MIND.UNM.EDU
>> workgroup = MIND
>> idmap config * : backend = tdb
>>
2015 Jan 13
0
Is there any problem that can arise from remapping gidNumber?
On 13/01/15 15:11, John Lewis wrote:
> On 01/13/2015 09:23 AM, Rowland Penny wrote:
>> On 13/01/15 14:06, John Lewis wrote:
>>> On 01/13/2015 06:35 AM, Rowland Penny wrote:
>>>> On 13/01/15 11:33, John Lewis wrote:
>>>>> This morning I remapped gidNumber from primaryGroupID to gidNumber. I
>>>>> did that because I could not change the
2015 Jan 13
0
Is there any problem that can arise from remapping gidNumber?
On 01/13/2015 11:10 AM, John Lewis wrote:
> On 01/13/2015 10:41 AM, Rowland Penny wrote:
>> On 13/01/15 15:11, John Lewis wrote:
>>> On 01/13/2015 09:23 AM, Rowland Penny wrote:
>>>> On 13/01/15 14:06, John Lewis wrote:
>>>>> On 01/13/2015 06:35 AM, Rowland Penny wrote:
>>>>>> On 13/01/15 11:33, John Lewis wrote:
2015 Jun 30
1
Several questions about winbind[d]
If there was no UNIX/Linux client, it would have been too easy, not fun
enough :)
File servers will be Linux clients using SSSD for users only, groups will
local to these file servers, to limit database usage (because of 4GB limit).
Some Linux workstation should be added at some point into this AD, they
will also use SSSD to retrieve users and groups. No idea yet about how much
of these they
2015 Jun 30
0
Several questions about winbind[d]
On 30/06/15 11:17, mathias dufresne wrote:
> @Andrew: I expect these lines came from RDP issue workaround which should
> be happening with previous Samba version. I removed all these lines as now,
> with 4.2.2 Samba version RDP and RSAT are working well without them.
>
> I removed also each and every idmap lines, commented most of winbind lines
> too and now my smb.conf is:
>
2008 Jun 12
1
[Bug 1310] chmod sftp command and setgid/setuid bit
https://bugzilla.mindrot.org/show_bug.cgi?id=1310
Damien Miller <djm at mindrot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |djm at mindrot.org
Blocks| |1452
--- Comment #3 from Damien Miller
2007 Apr 24
2
chmod sftp command and setgid/setuid bit
Hi OpenSSH developers,
I'm using OpenSSH on a daily basis and I'm very pleased
with the work you've done.
I am contributing to some Open Source software hosted at Savannah
https://savannah.nongnu.org/projects/tsp
and we recently hit some sftp unexpected behavior:
https://savannah.gnu.org/support/?105838
when using chmod sftp client command
it appears that setuid / setgid bits are
2015 Jun 30
2
Several questions about winbind[d]
@Andrew: I expect these lines came from RDP issue workaround which should
be happening with previous Samba version. I removed all these lines as now,
with 4.2.2 Samba version RDP and RSAT are working well without them.
I removed also each and every idmap lines, commented most of winbind lines
too and now my smb.conf is:
------------------------------------------------------------
[global]
2015 Jun 30
0
Several questions about winbind[d]
On 30/06/15 12:51, mathias dufresne wrote:
> 2015-06-30 12:42 GMT+02:00 Rowland Penny <rowlandpenny241155 at gmail.com>:
>
>> On 30/06/15 11:17, mathias dufresne wrote:
>>
>>> @Andrew: I expect these lines came from RDP issue workaround which should
>>> be happening with previous Samba version. I removed all these lines as
>>> now,
>>>