search for: whitelisting

Dears all, I was testing my localusers facter by puppetmaster fileserver but i''d got in error Could not retrieve localusers: No such file or directory - /etc/ puppet/whitelist I was pretending the file was served by fileserver of puppetmaster doing in init.pp : file { "/etc/puppet/whitelist": ensure => present, Just before to call a facter. I

On 06/12/2015 12:18 PM, Jonathan Billings wrote: > On Sat, Jun 13, 2015 at 12:05:16PM -0600, jd1008 wrote: >> Mark, please be aware that noscript has also a whitelist >> that is not viewable by the user. >> The whitelist tab does NOT list the hidden white listed >> entries. > You mean the noscript.mandatory about:config entry? I looked at it on > my computer and

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,

On 06/12/2015 11:25 AM, m.roth at 5-cent.us wrote: > jd1008 wrote: >> On 06/12/2015 07:28 AM, g wrote: >>> On 06/10/2015 03:56 AM, Always Learning wrote: >>>> I displayed, as a web page, a list of search results created in PHP, >>>> from MySQL. >>> i am still using 24.8.0 and do not have to contend with all the >>> bugs introduced by moz

All other patches from the sequence remain unchanged. Repost of patch 6 based on comments from Joey to follow. Mike

Hi, I'm using virsh to instance a VM in my environment, but I'm running on some issues. I created the following domain file: <domain type='kvm'> <name>demovm</name> <uuid>4a9b3f53-fa2a-47f3-a757-dd87720d9d1d</uuid> <memory unit='KiB'>4194304</memory> <currentMemory

Hi, I am trying to use shorewall as a way for authenticated network access. I read about dynamic black lists, but is there a way to do dynamic white lists? I''ve looked through the doc, but couldn''t find it. Also, could someone please assist me on creating a rule so that all other failures (ie. the mac is not in the whitelist), requests get forwarded to a certain ip and port (so

On 06/12/2015 12:27 PM, Valeri Galtsev wrote: > On Sat, June 13, 2015 1:22 pm, jd1008 wrote: >> >> On 06/12/2015 12:18 PM, Jonathan Billings wrote: >>> On Sat, Jun 13, 2015 at 12:05:16PM -0600, jd1008 wrote: >>>> Mark, please be aware that noscript has also a whitelist >>>> that is not viewable by the user. >>>> The whitelist tab does NOT

On 04/19/2017 10:00 AM, Marco Aurelio L. Gomes wrote: > Hi, > > I'm using virsh to instance a VM in my environment, but I'm running on > some issues. > I got the following error: > > error: Failed to create domain from domain.xml > error: internal error: qemu unexpectedly closed the monitor: > 2017-04-17T17:00:37.012369Z qemu-kvm: -drive >

...all* of them?). A whitelist seems > much less prone to breakage or unexpected behavior. > > Hi Sean, Which blacklist are you referring to? In all places where we specifically allow or disallow certain constructs (such as specific instructions, intrinsics, linkage modes and so on) we use a whitelisting strategy. Eli -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130618/56c04fdd/attachment.html>

I have modified my delivery agent to deposit files in my Maildir already containing custom flags. For example, x is appended for files that are sent from local users, y is for e-mails from Contacts and z is for e-mails from Whitelisted sources. A file will thus be delivered in the Maildir and be called something like: filename:2,yz Also in the Maildir I created a file called

loop is sometimes a module, for example on RHEL 5. --- appliance/kmod.whitelist.in | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/appliance/kmod.whitelist.in b/appliance/kmod.whitelist.in index 814b9d0..96fc4c3 100644 --- a/appliance/kmod.whitelist.in +++ b/appliance/kmod.whitelist.in @@ -62,3 +62,5 @@ reiserfs.ko crc*.ko libcrc*.ko + +loop.ko -- 1.6.6.1

>>"Never use a browser for email." I don't agree. In fact, using a browser for email or atleast initial setup, is actually more secure. This because SMTP/IMAP clients normally don't support 2FA, so you would have to "hack" a solution to enable 2FA for email. This can be made in 2 ways: Either, you have a full fledged email setup. Whats important, is, to prevent

...t;> much less prone to breakage or unexpected behavior. >> >> > Hi Sean, > > Which blacklist are you referring to? In all places where we specifically > allow or disallow certain constructs (such as specific instructions, > intrinsics, linkage modes and so on) we use a whitelisting strategy. > > What I'm saying is that the approach to defining the format seems to be basically "the format is LLVM IR, except ...". The "except ..." is effectively a blacklist. You are starting with LLVM IR and then removing (i.e. blacklisting certain aspects) -- Sea...

Hello, On RHEL 6/amd64, the stock value for DEFAULT_PKCS11_WHITELIST is not very useful. On such systems, /usr/lib64/* would need to be added to the pattern list. Although users can specify the -P option every time they launch ssh-agent, it might be nice to provide a means to specify a default whitelist at build-time. It's tempting to suggest that configure should automatically supply a

Hello, I've installed the TDMA whitelist filter in front of majordomo on all mailing lists at Xiph.Org. I also repaired a few unrelated spam filter breaks. Posting from subscribed email addresses is unaffected. Any post to a mailing list from an unknown email list will require a confirmation message the first time posting from that mail address. A confirmation reply adds that address to

Hello, I've installed the TDMA whitelist filter in front of majordomo on all mailing lists at Xiph.Org. I also repaired a few unrelated spam filter breaks. Posting from subscribed email addresses is unaffected. Any post to a mailing list from an unknown email list will require a confirmation message the first time posting from that mail address. A confirmation reply adds that address to

Hello, I've installed the TDMA whitelist filter in front of majordomo on all mailing lists at Xiph.Org. I also repaired a few unrelated spam filter breaks. Posting from subscribed email addresses is unaffected. Any post to a mailing list from an unknown email list will require a confirmation message the first time posting from that mail address. A confirmation reply adds that address to

Hello, I've installed the TDMA whitelist filter in front of majordomo on all mailing lists at Xiph.Org. I also repaired a few unrelated spam filter breaks. Posting from subscribed email addresses is unaffected. Any post to a mailing list from an unknown email list will require a confirmation message the first time posting from that mail address. A confirmation reply adds that address to