If you configure your Google account for extra security to use the 2-step verification, then some applications which work outside the browser might not be compatible with 2-step verification and cannot ask for verification codes.
Postfix which was installed and configured to send out emails won’t work anymore, and you might notice error messages in the /var/log/mail.log file.
SASL authentication failed; server smtp.gmail.com said: Application-specific password required.
For some reason I found this rule to be difficult but finally got it to work thanks to the internets. This is the only rule that worked within the NGINX configuration to get only the root URL to redirect to (in my case) a non-SSL location. Here’s the section:
For a number of reasons, it recommends disabling SSLv3 (as a result of its insecurity), settings AES256 as the standard cipher to utilize and a couple of other things that can prevent attacks. Good stuff to tighten up security on an NGINX SSL implementation.
After events that occurred with AT&T on the technical and customer service sides back when I first moved into my new house, I wasn’t quite sure what to expect with changing over, once again, to new service. However, after all of the frustration and mind-boggling breakdowns in order processing and account bungling from a few months ago, this has been worth the wait.
I had a failure recently when trying to compile ModSecurity as a standalone module for use within NGINX that seemed to be pretty consistent with what others were experiencing, from the limited number of sites that seemed to have information on this particular problem. I knew it was possible to set this up, but I also knew I was missing something.
After scanning the internet for a solution and getting some pointers from Ryan Barnett at Trustwave’s SpiderLabs, I finally found what I was looking for to get this to work.
Though I haven’t proven this theory out yet I’ve been wondering since it seems to me to be a difference in stability. So my neighbors all around me have U-verse and have had all kinds of issues in which a U-verse tech has had to come out to resolve their issues. I’ve had basically none, with a couple of exceptions (area-wide drops). One neighbor had to have the line at the curb completely dug up and reset, but that was a different issue. When they setup my connection, I asked up front to run twisted pair from the outside to my router/gateway instead of using coax. As I understand it, unless I’m mistaken, the default is to use coax which, sure enough, all my neighbors have. As it pertains to VDSL2+ (the protocol U-verse uses), is twisted pair more stable than coax as a medium for delivery? I’m just curious, because that would be an easy thing to ask for at the beginning. I don’t know that this is the case, but I would be interested to see stats on that. Here are my numbers using twisted pair after 113 days of data/error collection:
My, how easily we forget history. Even recent history. 2006 wasn’t that long ago, when an AT&T technician outed the National Security Agency’s program to install Narus data siphoning devices in the AT&T central offices. At the time Bush was president. Conservatives ignored all the noise about warrantless wiretaps from their political opponents and explained it away as necessary for the war on terror (oddly enough as our own president did today). I even held that view until these revelations. Then I became concerned. Little did the conservatives realize the civil libertarians (and concerned liberals) were right all along: this will be used, not for outsiders, but for us (much like DHS, but that’s another story, though eerily related).
Now Obama is president and the tables are turned. If we go back and read the articles in which the media was (rightly) concerned about President Bush’s warrantless wiretapping as it relates to the Constitution, we see it takes on a whole new meaning now that Obama is President and conservatives are being targeted. Whether it’s Bush or Obama though (who, on this point at least, are one in the same), we are coming to find out that we’re all civil libertarians now. The government has way too much power for the good of us all. And it will never lessen its grip without a fight.
That it has been revealed Verizon has tracked (eh hem, is tracking, eh hem) millions of calls only reveals the tip of the iceberg. It goes much, much deeper and broader than that.
Below is a list of some of the stories, videos and testimony from the early to mid-2000’s forward in which all of this was brought up over and over again: NSA is siphoning and storing our data. All they can get their hands on. They siphon it, mine it, store it, create data cubes off of it, make it searchable, sort it, analyze it, report off of it. What I know from the IT world of data storage, searching and analysis, applied to private data in this context, is frightening. And now NSA is fixing to launch their Bluffdale data center in which yottabytes of data will be stored. It’s a Brave New World. Big Data isn’t just a concept in the corporate IT world, but rather very much a part of data acquisition, storage, reporting, and sorting theory by the government.
What more can be said to show this government is out of control? Not sure what else can be done, short of a serious crisis to get us to wake up. The cultural rot, the malaise, the lack of incentive, the entitlement, the willful ignorance, and most of all, the loss of gospel-truth taking hold in people’s hearts. Saddening situation.
Lord help us, seriously, if there is ever a serious crisis causing dislocation. Emergency legislation waits in the wings. You know I never have understood over the years when I talk to people about these things how they can just flippantly say, “Yeah, I’m sure they’re listening to everything,” almost in disbelief. And I reply, “No seriously, they’re siphoning our data,” so as to emphasize the fact that it is happening, I’m not talking in hypotheticals. Unfortunately it will take a series of crises to get people to wake up to the seriousness of what we’re facing politically, economically, socially, spiritually.
I’ve been looking at a solution for this for quite some time. Until recently, the only way to make this work was to jailbreak your phone and use GuizmOVPN or some other type of app, which of course voids your warranty. But then along came OpenVPN Connect, an app for the iPhone and the iPad that is extremely simplistic to use (well, relatively speaking for OpenVPN). It works just like any other client side setup for OpenVPN, only you move the certs and config files over through iTunes File Sharing (which is probably the more secure way to do this transaction). This is an absolutely amazing way to secure your traffic to and from an OpenVPN server, from wherever you are, using 3g/4g or Wi-Fi.
Download the OpenVPN Connect app from iTunes on to your iPhone or iPad.
Take a sample client.ovpn file and modify it with your particular settings to connect to your OpenVPN server. Make sure and set the cert and key names to exactly what you’ll be copying over, otherwise it won’t reference the proper files from within the config.
Get your client.crt, client.key, ca.crt, ta.key, and client.ovpn files ready for moving over to your phone. (these file names are just examples)
Open iTunes with your phone or device connected.
Select the device on the left-hand side.
Click the Apps tab at the top.
Scroll down to the File Sharing section, select OpenVPN and drag n’ drop your five files (should be five at least) into the OpenVPN Documents window. Once they are moved over, go ahead and do a sync just to make sure everything is good.
As long as everything was setup correctly in the client.ovpn file and your certs are all good, you should be able to open your app and add it as a new profile. Once the the new profile is added in the app, you should be able to connect.
Note: As an aside, if you want to secure all your traffic to and from the OpenVPN server, make sure and set this parameter before you upload the client.ovpn file: redirect-gateway def1
The downside? It eats battery life like crazy. That all may depend on your encryption level and key size though. In addition, each time you want to edit the client.ovpn, you have to edit it locally on your computer and re-upload it. But considering the alternative (no VPN, PPTP, or jailbreaking your phone), this is an excellent app.
This problem has been perplexing me for several months now, ever since I upgraded my server to 12.10 Quantal. Finally found a solution (Can’t remember the site where I found it though)! These are the instructions for a profile that’s already been configured that no longer works.
Open the NX Client for Windows (in my case).
In the Session section, select the session profile you originally created, that no longer works.
Under the General tab, and the Desktop section, ensure that Unix and GNOME is selected.
Now, in the same tab, in the Display section, check the box next to Use custom settings, and click Settings.
Under the Performance section, check the box next to Disable the render extension.
Click Ok, then on the next screen, click Save and Ok.