Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1471275
| From | Theodore Ts'o <tytso@mit.edu> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] fscrypto: fix to null-terminate encrypted filename in fname_encrypt |
| Date | 2016-08-28 07:50 +0200 |
| Message-ID | <sb18J-64x-5@gated-at.bofh.it> (permalink) |
| References | <saWVr-3uU-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Sun, Aug 28, 2016 at 09:13:28AM +0800, Chao Yu wrote: > From: Chao Yu <yuchao0@huawei.com> > > This patch fixes to add null character at the end of encrypted filename > in fname_encrypt, in order to avoid incorrectly traversing random data > located after target filename. The call stack is as below: > > - f2fs_add_link > - __f2fs_add_link > - fscrypt_setup_filename > - fscrypt_fname_alloc_buffer allocate buffer for @fname > - fname_encrypt didn't set null character for @fname > - f2fs_add_regular_entry init qstr with @fname > - init_inode_metadata > - f2fs_init_security > - security_inode_init_security > - selinux_inode_init_security > - selinux_determine_inode_label > - security_transition_sid > - security_compute_sid > - filename_compute_type > - hashtab_search > - filenametr_hash traverse @fname as one which has null character The problem is not in fname_encrypt(), but rather that security_inode_init_security() should be given the _unencrypted_ filename. In ext4 security_inode_init_security() is called with the qstr from the dentry, not the encrypted qstr --- in fact we call security_inode_init_security before we call fname_encrypt. SELinux needs the unencrypted filename in order to decide which SELinux rules / labels should apply. - Ted
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH] fscrypto: fix to null-terminate encrypted filename in fname_encrypt Chao Yu <chao@kernel.org> - 2016-08-28 03:20 +0200
Re: [PATCH] fscrypto: fix to null-terminate encrypted filename in fname_encrypt Theodore Ts'o <tytso@mit.edu> - 2016-08-28 07:50 +0200
Re: [PATCH] fscrypto: fix to null-terminate encrypted filename in fname_encrypt Chao Yu <chao@kernel.org> - 2016-08-28 08:20 +0200
Re: [f2fs-dev] [PATCH] fscrypto: fix to null-terminate encrypted filename in fname_encrypt Chao Yu <chao@kernel.org> - 2016-08-29 17:00 +0200
Re: [f2fs-dev] [PATCH] fscrypto: fix to null-terminate encrypted filename in fname_encrypt Jaegeuk Kim <jaegeuk@kernel.org> - 2016-08-29 20:00 +0200
Re: [f2fs-dev] [PATCH] fscrypto: fix to null-terminate encrypted filename in fname_encrypt Theodore Ts'o <tytso@mit.edu> - 2016-08-29 21:10 +0200
Re: [f2fs-dev] [PATCH] fscrypto: fix to null-terminate encrypted filename in fname_encrypt Chao Yu <yuchao0@huawei.com> - 2016-08-30 18:20 +0200
csiph-web