similar to: [OFF-TOPIC] Reminder to tighten ALL types of security

Well them plus CIA, NSA, Barney the Dinosaur and Teletubbies. Brian Bernard On Apr 2, 2015 5:58 PM, "????????? ????????" <nevis2us at infoline.su> wrote: > One thing I forgot to mention: I also always recommend AGAINST using >> kasperski. Kasperski is KGB guy (*cough* *cough* retired. You know in that >> service retirement is only feet first dead, so you do your

http://bugzilla.mindrot.org/show_bug.cgi?id=1205 Summary: scp back-slash escaping of spaces ignored after username at hostname: tag Product: Portable OpenSSH Version: 4.3p2 Platform: ix86 OS/Version: Linux Status: NEW Keywords: low-hanging-fruit Severity: normal Priority: P3

Open Letter to Developers, Is there any way you can cut through the mob scene at Homeland Defense with a powerful new encryption/decryption formula? The government cryptography bunch are stuck in symmetry and asymmetry and are deaf/dumb/blind to supersymmetry. When it's so easy to line up a supersymmetrical hypercube fractal-to-fractal, pair-to-pair, quantum-to-quantum and slice through

I see the following paragraph in the Asterisk trunk LICENSE file: "In addition, Asterisk implements two management/control protocols: the Asterisk Manager Interface (AMI) and the Asterisk Gateway Interface (AGI). It is our belief that applications using these protocols to manage or control an Asterisk instance do not have to be licensed under the GPL or a compatible license, as we believe

Hi all, I'm sure this is simple but I don't get it. I have a table mytable<-c(rep("Disagree",37),rep("Agree",64)) table(mytable) this gives me Agree Disagree 64 37 but I didn't ask for it to be in alphabetic order. How can I get it in original order? Disagree Agree 37 64 Thanks, Jeff Jeffrey. M. Miller, PhD

Newsletter - October Issue, 2005 In October's issue we are going to profile a company involved in the Red Hot homeland security sector, also recently entering the Oil/Energy Industry! This company's st0ck is very much undervalued considering the potential of the industry and the position of the company. (The perfect time to get in) This small treasure is: VNBL (Vinoble, Inc.)

> Date: Wednesday, March 09, 2016 17:30:57 -0600 > From: g <geleem at bellsouth.net> > > On 03/09/16 14:28, Ned Slider wrote: >> On 09/03/16 19:11, g wrote: > <<<>>> > >> Does it affect the latest version of Firefox just released: >> >> firefox-38.7.0-1.el6_7 >> >> Is the bug in Firefox or the add-on. >>

I hope this message finds you well and thriving in your endeavors. As a fellow Vietnamese student currently pursuing education in the United States, I can't help but feel a sense of pride and excitement about the prospect of inviting you to experience the beauty and charm of my homeland, Vietnam. Vietnam is a land of captivating landscapes, rich history, and warm hospitality. From the

On Tue, 26 Jul 2016 13:40:59 -0500 Dale Schroeder <dale at BriannasSaladDressing.com> wrote: [snip] > > Sorry Rowland, but the break happened before the badlock patches when > Debian jumped from 4.1.x to 4.3.x, skipping 4.2.x altogether. [snip] > > Jim, currently at Debian 4.4.5. If you search this list, you will > find others who have had the same thing happen. To my

John R Pierce wrote: > On 5/31/2017 10:13 AM, m.roth at 5-cent.us wrote: >> If I had realized it would run this long, I would have used DBAN.... For >> single drives, I do, and choose DoD 5220.22-M (seven passes), which is >> *way* overkill these days... but I sign my name to a certificate that >> gets stuck on the outside of the server, meaning I, personally, am

On 7/27/2016 12:18 PM, Jim Seymour wrote: > On Tue, 26 Jul 2016 13:40:59 -0500 > Dale Schroeder <dale at BriannasSaladDressing.com> wrote: > > [snip] >> Sorry Rowland, but the break happened before the badlock patches when >> Debian jumped from 4.1.x to 4.3.x, skipping 4.2.x altogether. > [snip] >> Jim, currently at Debian 4.4.5. If you search this list, you

On 6 May 2016 at 23:31, Tanya Lattner <tanyalattner at llvm.org> wrote: > I am not going to argue with you anymore. I hope this isn't how we'll deal with CoC violations. > Please stop twisting my words. I'm certainly not twisting your words. I'm sorry you feel that way. I explicitly said I was confused, and I asked questions to understand what the point was. This

On Tue, Jun 25, 2019 at 09:09:58PM -0500, Eric Blake wrote: >I'm not sure whether we want to go with just the first patch (reject >nbd:unix:/path but still accept nbd:/path), or squash the two in order >to go with the second (reject both abbreviated forms, and require >scheme://...). Either way, though, nbdkit -U - --run '$nbd' will now >error out rather than

On 09/08/2018 03:15 AM, Richard W.M. Jones wrote: > Previously key=value on the command line allowed the key to be pretty > much anything that didn't contain an '=' character. Even empty > strings were permitted. > > This tightens up the permitted keys so they must contain only ASCII > alphanumeric, period, underscore or dash characters, and must not be > an

On Sun, Jul 16, 2023 at 04:39:18PM +0000, Tage Johansson wrote: > > @@ -194,7 +198,10 @@ calls. The cookie is unique (per libnbd handle) and E<ge> 1. > > > > You may register a function which is called when the command > > completes, see L</Completion callbacks> below. In this case we have > > -specified a null completion callback. > >

The following works fine but is there some way to make it more succinct? Thanks, Kent class obsd_etc_static { file { "/etc/mygate": owner => root, group => wheel, mode => 644, backup => main, source => "puppet://example.com/obsd_static/mygate" } file { "/etc/rc.conf": owner => root, group => wheel,

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Attached is a patch which attempts to enforce ''proper'' permissions of all files controlled directly by the puppet processes. All owners and groups are explicitly set as are all permissions. The idea is that the Puppet process configuration files should be relatively tamper resistant and at least throw a warning that the

Previously key=value on the command line allowed the key to be pretty much anything that didn't contain an '=' character. Even empty strings were permitted. This tightens up the permitted keys so they must contain only ASCII alphanumeric, period, underscore or dash characters, and must not be an empty string. --- docs/nbdkit-plugin.pod | 18 ++++++++++-------- src/main.c

Previously key=value on the command line allowed the key to be pretty much anything that didn't contain an '=' character. Even empty strings were permitted. This tightens up the permitted keys so they must contain only ASCII alphanumeric, period, underscore or dash characters; must not be an empty string; and must start with an ASCII alphabetic character. --- docs/nbdkit-plugin.pod

Package: logcheck Severity: wishlist I see no reason why /etc/logcheck should have any more permissions than 0750. Please consider removing access rights from 'other'. -- System Information: Debian Release: testing/unstable APT prefers stable APT policy: (700, 'stable'), (600, 'testing'), (98, 'unstable'), (1, 'experimental') Architecture: i386 (i686)