SMB1.
In terms of 'actively *IN*secure', it really depends what you mean by
that.
That is, like all big changes, the movement against SMB1 has had
multiple motivations:
- a desire no longer to expose really old code in Windows (recently
exploited)
- a desire to retire an old and compl
ely *IN*secure', it really depends what you mean by
that.
That is, like all big changes, the movement against SMB1 has had
multiple motivations:
- a desire no longer to expose really old code in Windows (recently
exploited)
- a desire to retire an old and complex protocol
- SMB3 having proper
On Mon, 2013-02-18 at 20:36 +0900, OGAWA Hirofumi wrote:
> Andrew Bartlett writes:
> > Or, if we cannot make any changes to the on-disk format, what about
> > keeping such a database in memory, allocating some of the existing free
> > list to files that have had fallo
On Mon, 2013-02-18 at 20:36 +0900, OGAWA Hirofumi wrote:
Andrew Bartlett abart...@samba.org writes:
Or, if we cannot make any changes to the on-disk format, what about
keeping such a database in memory, allocating some of the existing free
list to files that have had fallocate() called
ng you could not run out
of space expanding a file in another OS.
If a cluster was observed no longer to be in the real free list, it
would be ignored in the 'allocated free' list, to avoid corruption.
In short, I see the restriction on not breaking existing implementations
as a difficult, b
to be in the real free list, it
would be ignored in the 'allocated free' list, to avoid corruption.
In short, I see the restriction on not breaking existing implementations
as a difficult, but certainty not impossible problem.
Thanks,
Andrew Bartlett
--
Andrew Bartlett
On Thu, 2013-02-14 at 15:44 +0900, Namjae Jeon wrote:
> 2013/2/14, Andrew Bartlett :
> > (apologies for the duplicate mail, I typo-ed the maintainers address)
> >
> > G'day,
> >
> > I've been looking into the patch "[v2] fat: editions to support
> > fat
ctical way forward, and I look
forward to working with you on this.
Thanks,
Andrew Bartlett
--
Andrew Bartletthttp://samba.org/~abartlet/
Authentication Developer, Samba Team http://samba.org
--
To unsubscribe from this list: send the line "un
s.
Thanks,
Andrew Bartlett
--
Andrew Bartletthttp://samba.org/~abartlet/
Authentication Developer, Samba Team http://samba.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@
,
Andrew Bartlett
--
Andrew Bartletthttp://samba.org/~abartlet/
Authentication Developer, Samba Team http://samba.org
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo
forward, and I look
forward to working with you on this.
Thanks,
Andrew Bartlett
--
Andrew Bartletthttp://samba.org/~abartlet/
Authentication Developer, Samba Team http://samba.org
--
To unsubscribe from this list: send the line unsubscribe linux-kernel
On Thu, 2013-02-14 at 15:44 +0900, Namjae Jeon wrote:
2013/2/14, Andrew Bartlett abart...@samba.org:
(apologies for the duplicate mail, I typo-ed the maintainers address)
G'day,
I've been looking into the patch [v2] fat: editions to support
fat_fallocate() and I wonder
-technical really the right list for cifs-vfs patches? Aside from
being CC'ed on such patches, I've never seen discussion of them on the
Samba mailing lists.
Steve: Shouldn't that be linux-cifs-client?
Andrew Bartlett
--
Andrew Bartletthttp://samba.org/~a
from
being CC'ed on such patches, I've never seen discussion of them on the
Samba mailing lists.
Steve: Shouldn't that be linux-cifs-client?
Andrew Bartlett
--
Andrew Bartletthttp://samba.org/~abartlet/
Authentication Developer, Samba Team http
14 matches
Mail list logo
