The activities of hackers are intensifying all over the world and not only large companies such as Sony or CD RED Project.
Unfortunately, we are witnessing one of the largest user password leaks in history. Cybernews warns that there is a huge text file in it There are up to 8.4 billion entries People around the world use it to sign in to a variety of sites and services. Cybernews editors confirmed the existence and content of the file, which takes up about 100 gigabytes.
“Taking into account the fact that online services are used by approximately 4.7 billion people, we can risk stating that The slogans of all the inhabitants of the world leakedNetwork connection. For this reason, we recommend our readers to immediately check if their passwords have been leaked and, if necessary, to change their passwords,” Cybernews wrote.
Password verification can be performed Location Prepared by Cybernews. Thanks to him, you can check whether a certain phrase, which we use as a password, is available in the tools used by hackers.
It’s worth remembering here not to use the same password for different websites and services you visit. This way, we avoid a big headache when someone can access our password.
function statusChangeCallback(response, forced) {
<
?
if (!$this - > user - > _is_logged()) {
?
>
if (response.status === 'connected') {
// Logged into your app and Facebook.
FB.api('/me', function(response) {
if (forced == 1) {
console.log('Próba logowania przez przycisk');
} else {
console.log('Próba autologowania');
}
console.log(JSON.stringify(response));
//fbAutoLogin(JSON.stringify(response), forced); });
//fbAutoLogin(fb_user_id);
} else if (response.status === 'not_authorized') {
// The person is logged into Facebook, but not your app.
console.log('Please log into this app.');
} else {
// The person is not logged into Facebook, so we're not sure if
// they are logged into this app or not.
console.log('Please log into Facebook.');
} < ?
} ? >
}
// This function is called when someone finishes with the Login
// Button. See the onlogin handler attached to it in the sample
// code below.
function checkLoginState() {
FB.getLoginStatus(function(response) {
statusChangeCallback(response, 1);
});
}
window.fbAsyncInit = function() {
FB.init({
appId: '113502828807977', // App ID
cookie: true, // enable cookies to allow the server to access the session
xfbml: true, // parse social plugins on this page
version: 'v2.2' // use version 2.2
});
FB.getLoginStatus(function(response) {
statusChangeCallback(response, 0);
});
}
// Here we run a very simple test of the Graph API after login is
// successful. See statusChangeCallback() for when this call is made.
function testAPI() {
}
// Load the SDK Asynchronously
(function(d) {
var js, id = 'facebook-jssdk',
ref = d.getElementsByTagName('script')[0];
if (d.getElementById(id)) {
return;
}
js = d.createElement('script');
js.id = id;
js.async = true;
js.src = "https://connect.facebook.net/pl_PL/all.js";
ref.parentNode.insertBefore(js, ref);
}(document));
