#apppasswords

[somitsvk]

How to Generate Yahoo App Password? - (Step-by-Step Guide!)

[thesecuritysleuth]

Jump the Shark: 4 reasons why I rebranded my pride and joy

This is a quick post in which I’ll try to relay my reasoning as to why I rebranded my password manager app. 

Reason 1: The name wasn't obvious enough

Many of you who are regular readers of this blog would be aware that I have developed an anti - cloud privacy focused password manager, some of you may have even followed my journey from "how I stopped reusing my passwords and how you can too". After thinking on it for a long time the name I came up with for this password manager was Passta. The name Passta was supposed to be a clever anagram of “password storage assistant” but sadly this never caught on. That’s reason 1 why I went through with the rebranding - FYI the name is now “PassVult” and you can find it here on iOS, there’s also a lite version which you can get here.

Reason 2: The name was stolen

Reason number two for rebranding the app is between blogging about the app and actually releasing it a German language Passta password manager popped up on the App Store. It was extremely annoying regardless if it was a coincidence or deliberate act. It would be good to say this is the first time this has happened but it hasn't I have also seen numerous popular posts I put large amounts of effort and research into on here be blatantly plagiarised and copied word for word. 

Reason number 3: Logo design wasn't intuitive

Reason number 3 which helped with my rebranding efforts was that the logo didn’t really correlate to what the app did. Green P on dark grey background doesn’t really scream security app so now I have moved to a more trustworthy blue with white asterix and cursor line (like when you start typing in a password) that should be much better at leaving subtle queues.

Reason number 4: my message was lost on my potential customers

Reason number 4, the fact that this was a privacy focused password manager wasn’t really being conveyed effectively I have added a few call outs to this now - hopefully it’s a bit more obvious. When I built this app it’s specifically because I didn’t trust lastpass or 1password to be able to adequately protect my data. Numerous times since starting development and releasing the app this holds true. I’m proud at least that I have built something that lets you keep control of your password data forever even if nothing else comes out of this.

What’s next?

Whats next you might ask? Work has finally started on the android version, I’m confident the app is now in a solid place and that I can port it to android. Stay tuned for updates here. 

Also next is the continuous slog of marketing, marketing and more marketing. I didn't really have any experience in this space so I stared looking into app marketing and most importantly how to effectively market apps, there is so much I wasn't aware of its time to start learning and using some of these strategies to my advantage.

Improving the experience and adding more features. That last sentence should hopefully speak for itself, incase it doesn't it means the app will get better with every release. 

[buithucdong]

Đồng bộ danh bạ BlackBerry OS 10 - cập nhật 092019

Đồng bộ danh bạ BlackBerry OS 10 – cập nhật 092019

Xin chào,

Chắc hẳn rất nhiều anh chị em sử dụng BlackBerry OS đang gặp vấn đề không đồng bộ được danh bạ mà chỉ đồng bộ được email và lịch, nguyên nhân là do Google có cập nhật thay đổi API của danh bạ. Chỉ với 3 bước đơn giản sau bạn sẽ thiết lập được đồng bộ danh bạ BlackBerry OS 10

Truy cập Google/Gmail, bật mật khẩu 2 lớp

Truy cập https://myaccount.google.com/apppasswords tạo App Passwords,

M…

[clarenceomoore]

The Future of Business is a Digital Spokesperson — Let’s Build a Preview Using Microsoft’s Bot Framework

Everyone loves a great conversation.

And the conversational U.I. is coming on quickly.

Chatbots have been all the rage for the past couple of years — and the technology is quickly catching up to the hype.

As our trust in artificial intelligence grows, so too does our faith in letting it do more and more important work for us.

And what’s more important than interacting with your customers?

Well, A.I. is ideally suited for providing your customers with the personalized interactions they want — without you needing to hire a small army to man a call center.

Rise of the Conversational U.I.

The conversational user interface is about self-service — a major trend going back to ATMs. Self-service allows customers to solve problems on their own terms — while simultaneously reducing your costs.

The conversational U.I. is also a richer interaction — compared to websites. Providing your customers with a more natural and comfortable experience, while giving your business a deeper understanding of that customer’s emotions and urgency during the interaction.

Era of the Digital Spokesperson

If you project this trend out, it leads us to a point where A.I. could become the entire front end for your business. And in-fact, the consulting firm, Accenture, is already predicting exactly that.

Trend #1 for Accenture’s “Technology Vision 2017” is A.I. is the new U.I., anticipating…

“A.I. is making every interface both simple and smart…A.I. is poised to act as the face of a company’s digital brand and a key differentiator.”

So let’s explore what it takes to build out a chatbot capable of spanning the wide range of digital channels. And for the purposes of this guide, we’ll be using Microsoft’s Bot Framework to build it.

A.I.-Powered Conversational Interface

Without any further ado, let’s jump right into it…

What You’ll Need

Step 1: Create the Repository

Step 2: Create the Application

Step 3: Register the Bot

Step 4: Build the Bot

Step 5: Test It

Step 6: Push it to the Cloud

Step 7: Connect the Bot to Other Channels

Troubleshooting

That may look like a lot of steps, but it’s actually pretty easy to do.

The end result

This guide will provide you with the perfect starting point — a simple bot, running in the cloud, that responds to your interactions.

What you do with it from there is where the real magic begins — adding communication channels, enhancing functionality, and deepening conversation dialog.

How it works.

The architecture is pretty simple, but there are a few moving parts.

The bot itself is only a single file (written in Node.js), which we will store in a GitHub repository. And then we’ll use that GitHub repo as a deployment source for a Web App on Azure.

And from there, the Bot Framework Connector Service will allow you to wire up the bot to a wide range of different communication channels.

Ready to go? Let’s get to it…

What You’ll Need

Right off the bat, let’s get the initial requirements knocked out.

Install Node.js

To start, this application is written in Node.js, so you’ll need to install it. You’ll also need Node’s package manager — npm — which should be included with the Node.js installation.

Download the source repository.

Next, let’s pull down the source files. (You’ll need a git client installed on your computer for this step.)

Move to the directory you want to use for this guide and run the following commands in a terminal:

# Download source repository git clone https://github.com/10xNation/microsoft-bot-framework-nodejs.git cd microsoft-bot-framework-nodejs

The repository only includes a couple of files — so don’t blink.

Create an Azure account.

Go to the Azure home page (Azure is Microsoft’s cloud services platform).

If you don’t already have an Azure account, go ahead and create one by clicking on the “Free Account” button and completing the registration process.

Install the Bot Framework emulator.

You’ll also need to install the Bot Framework emulator.

The emulator is a desktop application that allows you to test and debug bots on your local machine (or via tunnel). It runs on Windows, Mac, and Linux. Just follow the provided directions to install — it’s super easy to use.

Step 1: Create the Repository

Next, go to the GitHub home page and register for a new account if you don’t already have one.

Once you’re signed in, click on the plus sign and “New repository.”

Enter a name for your new repo and hit “Create repository.”

Next, we’ll spin up the app…

Step 2: Create the Application

We need an Azure’s Web App instance to power the bot in the cloud, so go to your Azure Dashboard and sign in with your Azure account.

Click on the “+ New” button.

Then select the “Web + Mobile” and “Web App“ options.

On the Web App Create page, enter an “App name” — select a “Subscription,” — then create or select a “Resource group.” And the system should automatically create/choose an “App Service plan/Location“ for you.

Once everything is filled out, hit “Create.”

And after a few minutes, the new subscription will show up on your dashboard. Go ahead and click it (the App Service).

Configure the deployment options.

That should take you to the Overview tab for your new app.

Click on the “Deployment options” tab.

And then click on “GitHub.”

Go ahead and follow the prompts to authorize Azure to access your GitHub account / organization.

And hit “OK”

Hit “Choose project” and select the repo you created in step #1. If desired, select a branch — we’ll stick with master for this demo.

Once the GitHub repo is fully configured, click “OK.”

And that’s it for the web app, so let’s spin up the bot…

Step 3: Register the Bot

For your bot to be publicly accessible, you’ll need to register it with the Bot Framework platform, so go to the Developer Portal and sign in with your Microsoft account (same as Azure portal above).

Click on “My Bots.”

And “Register.”

Then jump back to your Azure App Service Overview tab from step #2 and copy the “URL.” Paste that URL into the “Messaging endpoint” field and add on /api/messages (see below).

Also enter a “Display name,” “Bot handle,” and “Long description.” Then click on “Create Microsoft App ID and password” to get your app ID.

Click on “Generate an app password to continue.”

And “Ok.”

Then “Finish and go back to Bot Framework.” And that will take you back to the Bot registration page with a pre-populated “app ID.”

All you have to do now is verify your email address in the “Owners” box, agree to the terms statement, and hit “Register.”

That should give you a simple success prompt. So hit “OK.”

And at this point you should see a dashboard for your shiny new bot.

So let’s put down some code for this new bot…

Step 4: Build the Bot

When it comes to software development, this is about as easy as it gets.

Configure Node.js.

Spin up the application settings using the command below:

Terminal

npm init

Enter responses to the screen prompts as desired — defaults are fine.

Install the Node.js modules.

Next, let’s install the Node.js requirements:

Terminal

npm install --save botbuilder npm install --save restify

That should only take a few seconds, so let’s move onto where the magic really happens…

Create the bot application.

The repo you cloned in What You’ll Need already includes this file, but below is the code if you’d like to see a preview:

app.js

var restify = require('restify'); var builder = require('botbuilder'); // Setup Restify Server var server = restify.createServer(); server.listen(process.env.port || process.env.PORT || 3978, function () { console.log('%s listening to %s', server.name, server.url); }); // Create chat connector for communicating with the Bot Framework Service var connector = new builder.ChatConnector({ appId: process.env.MICROSOFT_APP_ID, appPassword: process.env.MICROSOFT_APP_PASSWORD }); // Listen for messages from users server.post('/api/messages', connector.listen()); // Receive messages from the user and respond by echoing each message back (prefixed with 'You said:') var bot = new builder.UniversalBot(connector, function (session) { session.send("You said: %s", session.message.text); });

Ready to see the bot in action?

Step 5: Test It

Then let’s test your bot by using the emulator you installed in What You’ll Need.

Start the bot.

Move to the repo directory from What You’ll Need and run the following command in a terminal to start your bot:

Terminal

node app.js

This will run the application on the port we listed in app.js file — 3978.

All you’ll see is a simple listening notice.

Connect to the emulator.

Once your bot is running, fire up the bot emulator and enter the URL http://127.0.0.1:3978/api/messages, and your App ID and password.

Then hit “Connect.”

Have a chat.

Now that your bot is running locally and is connected to the emulator, try out your bot by typing a few messages in the emulator.

If all went as planned, you should see the bot respond to each of your messages with the original message prefixed with “You said:”.

Step 6: Push it to the Cloud

Now we’re ready to publish the bot to Azure.

Upload the repository

And the easiest way to do that is to delete the .git folder in the repo you cloned in What You’ll Need, then reinitialize it as a new repo.

So go ahead and delete .git and run the following commands in the repo’s directory:

git init git add . git commit -m "Initial commit" git remote add origin git@github.com:PROFILE/REPO_NAME.git git push -u origin master

Replace PROFILE and REPO_NAME with the respective profile/organization and repository name you created in step #1.

Note: if you chose a branch other than master while configuring the “Deployment options” in step 2, then replace master above with the appropriate branch.

Set the environment variables.

To keep things secure, you’ll need to add your App ID and password to the Web App settings, so they don’t have to be configured in the app.js file (and publicly available on github.com).

Jump back to your Azure Web App dashboard from step #2 and click on the “Application settings” tab, then scroll down to the “App settings” section.

We need to add two environment variables: For the first one, enter “MICROSOFT_APP_ID” for Key and your App ID from step #3 in the Value field. And for the second one, enter “MICROSOFT_APP_PASSWORD” for Key and your respective app password for Value.

Then hit the “Save” button.

Verify deployment.

Once Azure finishes reconfiguring itself, you should be able to see your bot on the My Bots Dashboard.

Click on it.

Then click on “Test” and enter something in the message box.

You should see a response similar to what you got in the emulator above.

Good stuff!

Step 7: Connect the Bot to Other Channels

One of the biggest advantages of using the Bot Framework is the ease at which you can make your bot available on nearly all of the major chat platforms — so take advantage!

Simply click on whichever channel you want to add and follow the prompts.

That’s it!

Troubleshooting

If you’re having any problems with the application, be sure to check out the logs.

Emulator logs.

The emulator makes it pretty easy to track what’s happening.

Take a look in the “Log” section of your emulator for specifics.

Azure logs.

Within Azure, jump back to your dashboard and click on the “Diagnose and solve problems” tab.

From this tab you have access to a number of different tools that can help track down any issues.

Take it to the Next Level

Congratulations! You’ve successfully created a bot that can communicate across a wide range of channels.

But this demo is just a starting point — the real fun begins when you start adding more and more channels and capabilities to your bot. Building it up to a Digital Spokesperson.

You can dig deeper into the Bot Framework in the Bot Framework Documentation or the Bot Builder SDK for Node.js.

Enjoy!

This post is part of our How to Apply A.I. in Your Business blog series. Be sure to check out our past issues:

Building Voice-Enabled Products With Amazon Alexa

Cognitive Customer Engagement Using IBM Watson

Harnessing Visual Data Using Google Cloud

Building a Recommendation Engine Using Microsoft Azure

Predicting Marketing Campaign Response Using Amazon Machine Learning

Unleashing A.I.-Powered Conversation With IBM Watson

Get into the Mind of Your Customer Using Google’s Sentiment Analysis Tools

Discover Your Customers’ Deepest Feelings Using Microsoft Facial Recognition

Give Your Products the Power of Speech Using Amazon Polly

Computers Are Opening Their Eyes — and They’re Already Better at Seeing Than We Are

How to Predict When You’re Going to Lose a Subscriber

And be on the lookout for future issues, they come out every other Monday.

[daengkhao]

Sysadmin diaries - Day 3

Another quiet day at work but back home I decided to tackle some of the odd messages I’d noticed at boot after I updated the kernel the other day.

First on list, I noticed that my ufw firewall was blocking some traffic from my Netgear NAS. For a while I’d had a problem with the NFS mount locking up after a while. This seemed to coincide with a firmware upgrade on the NAS. Naturally I was cursing Netgear. However, I noticed that on my laptop I didn’t get that issue. Must be some silly bleedin default in Linux Mint I concluded, So I started to dabble with the NFS mount options, without success so far. But here was the answer, the firewall was blocking some kind of keep alive messages from the NAS. A quick firewall update:

ufw allow from 192.168.11.9

and problem fixed. Apologies Netgear and Linux Mint, user error again, it broke when I set up the firewall.

Next were the following messages:

Jan  5 11:36:54 localhost postfix/smtp[29391]: 75858A424AC: SASL authentication failed; server smtp.gmail.com[64.233.184.109] said: 534-5.7.9 Appl ication-specific password required. Learn more at?534 5.7.9  https://support.google.com/mail/?p=InvalidSecondFactor f67sm99639626wmd.13 - gsmtp

The gmail SMTP server was rejecting my mail. Come to think of it, I hadn’t had any emails from the server in a while, in fact since I turned on Google 2 factor authentication. After a bit of research I found out that you need to create an app password. To do this you need to go to https://security.google.com/settings/security/apppasswords , select app > Mail , select device > Other (Custom Name) > create a name > Generate. My server runs postfix so i had to add the application specific password to sasl_passwd replacing the one already there and ran

/etc/postfix/sasl_passwd

A restart of postfix and another problem solved.

Next /boot as a bit full after the kernel update. So I deleted the files relating to the oldest kernel and ran

update-grub

This updates grub with kernels available and /boot was down to 50% utilised.

Finally, after updating to Linux Mint 18 a few months back I was expecting the boot time to drop dramatically due to the synchronous start up performed by systemd. However, it still seemed a bit slow but I found this really useful command:

systemd-analyze blame

If you run systemd, try it. It lists the time it takes to start each service with the slowest at the top. For example, I found puppetserver was taking over 3 minutes to start. As I installed it just as a learning exercise, I decided to disable it. I also disabled a couple of other unnecessary slow starters.

That’s it for today, bye!

[marceljansen2015]

Hoe configureerd u Yahoo! In Outlook?

Hoe configureerd u Yahoo! In Outlook?

Het merendeel van gebruikers zijn gewent Yahoo! Te gebruiken op browsers. Desondanks zijn er gelegenheden waar integratie van Yahoo! Accounts in Outlook user-interface handiger is. Dan hoeven we niet steeds te switchen tussen Outlook en browser terwijl we aan e-mails aan het werken zijn onder Outlook.

Meeste gebruikers kunnen zich misschien afvragen waarom Yahoo! niet geconfigureerd kan worden onder Outlook de laatste tijd. Recent hebben of zullen Gmail,iCloud en Yahoo! Een extra beveiligings kenmerk invoeren die de gebruiker vereist een tweede wachtwoord in te vullen voor een app van een derde partij. Inclusief Outlook die toegang probeerd te krijgen naar de e-mail, kalenders,contacten en taken informatie.

Het heet 2-stap Verificatie. U moet het aanzetten om Yahoo! onder Outlook te kunnen gebruiken. Desondanks bied Yahoo! App passwords in deze situatie. Leest u verder voor meer details:

Log in op uw Yahoo! en ga naar Account Info. Klik op Setup your second sign-in verification onder Sign-In And Security.

Klik op Generate app password.

Vul de naam van de software in die toegang nodig heeft onder Name the app that requires a password en klik op Generate password. Vul de code in onder Enter the app password. Klik op Done en sluit.

Hoe doe ik de setup van Yahoo! e-mail in Outlook?

Hoe doe ik de setup van Outlook voor Yahoo? Ga naar Outlook, klik op File links boven en selecteer Account settings.

Creër handmatig een mail profiel zoals gebruikelijk. Bij Account Type,kies POP of IMAP volgens uw voorkeur. Vul wachtwoord in wat u zojuist verstrekt heeft gekregen van Generate password.

Klik op More Settings aan de rechterzijde. Klik op het Outgoing Server tabje en vink het vakje My outgoing server (SMTP) requires authentication aan.

Ga naar de volgende tab van Advanced,vink het vakje van This server requires an encrypted connection (SSL) aan en het port number zal veranderen naar 995 voor POP en 993 voor IMAP.

Vervolgens verander Outgoing server (SMTP): naar 587 als de waarde van Use following type of encryption connection TLS is.

Verander Outgoing server (SMTP): naar 465 als de waarde van Use the following type of encryption connection SSL is.

Klik op OK en sluit. En de rest op OK.

Nu kunnen we Gmail’s mail functie in Outlook gebruiken. Maar de contacten en kalenders dan? Er is een Outlook add-in genaamt EVO Collaborator voor Outlook. En het is in staat dit sort 2-stap verificatie process in Gmail,iCloud en Yahoo! aan te kunnen. U kunt het downloaden via de officiele website om het uit te proberen

EVO Collaborator voor Outlook is compatibel met :

Publiek contact,kalender, taak services zoals Gmail,iCloud,Yahoo! En fruux.

CardDAV/CalDAV servers ter plekken zoals EVO Mail Server, Mac OS X Server, OwnCloud en Zimbra.

Na ECO installatie , zal elk contact , agenda en taken items gemaakt door een andere manier van mobiele apparaten of het web gebaseerde interface worden gesynchroniseerd met Outlook en vice versa.

Voor alle items voor ECO installatie kunt u handmatig items selecteren en deze uploaden in uw CardDAV/CalDAV account.

Ik denk dat het elke cent waard is.

Zie AUB de volgende links hoe u populaire CardDAC/CalDAV services synchroniseerd met Outlook.

Synchronisatie van uw Gmail contacten en agenda in Outlook

Synchroniseer iCloud´s Contacten en Kalenders met Outlook

Sync Mac OS X, Zimbra of OwnCloud met Outlook.