similar to: [PATCH] Whitelist the loop kernel module

The driver was renamed from ibmvscsic to ibmvscsi on kernel 3.7. See https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9965c2f19be470c452357ae4f6304467cdeada55 The old name is kept so supermin works with recent kernels as well as kernel version older than 3.7. --- src/format_ext2_initrd.ml | 1 + 1 file changed, 1 insertion(+) diff --git a/src/format_ext2_initrd.ml

-- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones New in Fedora 11: Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 70 libraries supprt'd http://fedoraproject.org/wiki/MinGW http://www.annexia.org/fedora_mingw -------------- next part -------------- >From dba9b0377d29cb937fcef3861eae4f722aced323 Mon Sep 17

Also drop the sr_mod module used by the deprecated guestfs_add_cdrom interface. --- src/ext2_initrd.ml | 5 ----- 1 file changed, 5 deletions(-) diff --git a/src/ext2_initrd.ml b/src/ext2_initrd.ml index 730f806..5e841ea 100644 --- a/src/ext2_initrd.ml +++ b/src/ext2_initrd.ml @@ -40,12 +40,7 @@ let kmods = [ "virtio*.ko*"; "libata*.ko*"; "piix*.ko*"; -

On Tue, Mar 31, 2020 at 11:11:44PM -0300, Gustavo Luiz Duarte wrote: > The driver was renamed from ibmvscsic to ibmvscsi on kernel 3.7. > See https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9965c2f19be470c452357ae4f6304467cdeada55 > > The old name is kept so supermin works with recent kernels as well as kernel > version older than 3.7. > --- >

The appliance was being completely rebuilt every time guestfsd was updated. This was because make.sh depended on guestfsd, which it had to do because it called update.sh to install guestfsd. This fix removes the call to update.sh in make.sh, and therefore the dependency on guestfsd. The Makefile already includes a rule to run update.sh when guestfsd is updated, so this was unnecessary. ---

Dear Friend, I done configuration using RBLSMTPD with WHITELIST, but I don't know it is correct. Please check files below are corrects. Thanks Adriano === FILE WHITELIST.DOMINIO.RBL. ==== $ttl 900 whitelist.dominio.rbl. IN SOA host1.xxxxxx.com. root.xxxxx.com. ( 2006112002 ; serial; 3600 ; refresh period (1 hora); 900 ; retry time (15 minutos); 1800 ; expire tiem (30 minutos); 900 ;

I looked at the 1.3 whitelist documentation and realized that the ops example, while interesting in and of itself, did not do what I think a whitelist does. Back to symmetry, if a blacklist is a list of sites not allowed to connect in through the fire wall, maybe to a web server, for example, then a whitelist should be a list of machines that are allowed to access a service or services, again,

It would seem kmod-hfsplus does not have a module for my kernel uname -r 3.10.0-327.28.2.el7.x86_64 yum provides "*/hfsplus.ko" Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile * base: mirror.tzulo.com * elrepo: repos.ord.lax-noc.com * extras: mirrors.usinternet.com * updates: mirror.nexcess.net kmod-hfsplus-0.0-1.el7.elrepo.x86_64 : hfsplus

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 15 Jan 2015, Cliff Hayes wrote: > When new users are added we start them with a spam rule that routes spam to > their junk folder. I don't see a way to assign priority ... so how does a > user whitelist a spam-flagged email? Are the rules applied in some order? > Alphabetically perhaps? If so I can name the spam rule

echo_daemon is a simple echo which can be used to test connectivity between the client and daemon. --- daemon/Makefile.am | 1 + daemon/echo_daemon.c | 66 +++++++++++++++++++++++++++++++++++++++++++++++++ daemon/m4/stddef_h.m4 | 45 +++++++++++++++++++++++++++++++++ po/POTFILES.in | 1 + src/MAX_PROC_NR | 2 +- src/generator.ml | 7 +++++ 6 files changed,

https://bugzilla.mindrot.org/show_bug.cgi?id=2682 Bug ID: 2682 Summary: ssh-agent is unable to remove smartcard after introducing whitelist Product: Portable OpenSSH Version: 7.4p1 Hardware: Other OS: Linux Status: NEW Keywords: patch Severity: enhancement Priority:

RHEL 3 doesn't have a dynamic /dev. kmod-virtio creates devices nodes for vdX block devices based on what the major number of virtblk was at the time it was installed. This is, in turn, based on the order the modules were loaded in initrd. To try to preserve this precarious state of affairs, when adding virtio drivers to a new initrd we always load the same drivers as kmod-virtio in the same

This patch is FYI as it needs more testing, although feel free to take a look at it if you want. Background: We'd like to change libguestfs so that the appliance can support optional features. This would mean you could have (for example) a 'libguestfs' base package and a 'libguestfs-xfs' package providing optional support for XFS filesystem tools. This would only apply to

We used to have a per device feature whitelist to filter out the unsupported virtio features. But this seems unnecessary since: - the main idea behind feature whitelist is to block control vq feature until we finalize the control virtqueue API. But the current vhost-vDPA uAPI is sufficient to support control virtqueue. For device that has hardware control virtqueue, the vDPA device driver

Hi Nick, Just in case you aren't already aware of it, there is a tool that limits rsync to particular directories: rrsync - Restricts rsync to subdirectory declared in .ssh/authorized_keys https://www.samba.org/ftp/unpacked/rsync/support/rrsync There is also a generic tool (I wrote this one) for limiting incoming ssh commands to a fixed list of specific actual commands (with

This adds support for whitelisting the acceptable options in the "refuse options" setting in rsyncd.conf. It introduces "!" as a special option string that refuses most options and interprets any following strings as patterns of options to allow. For example, to allow only verbose and archive: refuse options = ! verbose archive The "!" does't refuse no-iconv,

Thanks. That's exactly what I needed. However I have a permission problem. I added the parameter to 90-sieve.conf and created the directory but now I get the following permissions errors in maillog even though I have the file and directory wide open with 777 permissions: Error: yY/0JHtauVQfPgAAU+Cu/Q: sieve: failed to open sieve dir: stat(/var/lib/dovecot/sieve/after.d/) failed: Permission

Hi, The dovecot version is 2.2.33.2 and we are using LDAP to do the authentication for SMTP service. We have the following configuration in auth-ldap.conf.ext to deny some users for LDAP auth. passdb { args = /etc/dovecot/deny.smtp driver = passwd-file deny = yes } passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } And now we want to change the mechanism and only users

Am 13.07.2018 um 10:30 schrieb whpang: > Hi, > > The dovecot version is 2.2.33.2 and we are using LDAP to do the authentication for SMTP service. [ ... ] > Anyone can help to advice how to configure dovecot to have a whitelist for user LDAP authentication? Thank you very much. > > Best regards, > William Pang > > Academic Computing and Technology Services Section

Hello, When new users are added we start them with a spam rule that routes spam to their junk folder. I don't see a way to assign priority ... so how does a user whitelist a spam-flagged email? Are the rules applied in some order? Alphabetically perhaps? If so I can name the spam rule z-spam. Thanks in advance.