Sponsored Content
Full Discussion: Cyber wall? just for me?
The Lounge What is on Your Mind? Cyber wall? just for me? Post 302994651 by jim mcnamara on Sunday 26th of March 2017 11:48:59 AM
Old 03-26-2017
I don't get what all you are asking. But part of the answer is:
Big companies geoblock all the time.
Countries where the government does not like unreviewed content, the same occurs.
To my knowledge, Britain does not geoblock every IP from Brazil. Try this to test: Google

The other possibility is that the podcast company's version of antimalware is blocking a part of the IP range you are in.

Brazil is not blacklisted on the datasets we have. Your ISP may be. And you may be dealing in the UK with a company or its subsidiary that just got a new blacklist. And, your ISP is on it.

'Underground' has a negative side:
FWIW: A lot of security people are trying to learn how to deal with 'underground' or dark net services like tor.
Unless you are really security savvy, messing around in a lot of dark net sites may get your system irreversibly trashed. So say the security guys at my company.

Instead of doing something counterproductive, see if you can find a way to email the podcast site owner, in order to see if s/he can help some way.

Last edited by jim mcnamara; 03-26-2017 at 12:56 PM..
This User Gave Thanks to jim mcnamara For This Post:
 

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

wall commands

I would like to know when using the wall command can I send a message to a specific user that is logged in. Thank you (1 Reply)
Discussion started by: nascar.fan
1 Replies

2. UNIX for Dummies Questions & Answers

wall

is there a command to send all terminals a message. i tired wall, but it only sends the message to who ever is logged in at a terminal. i need a command to send to every terminal no matter if someone is logged in or not. Thanks! -The DJ (11 Replies)
Discussion started by: djatwork
11 Replies

3. What is on Your Mind?

(Preprint) Human Cyber Consciousness - The Next Frontier

Preprint available at Amazon (Publication date: May 31, 2018): Preprint Cancelled. See this update. (0 Replies)
Discussion started by: Neo
0 Replies

4. What is on Your Mind?

Human Cyber Consciousness: The Next Frontier in Cybersecurity

FYI, I am planning to release the first book in a new mini-series the end of May: Pre-Order Cancelled. See this update. (Cyberspace Situational Awareness Book 1) https://www.unix.com/members/1-albums215-picture844.jpg If anyone want to write a short book for this mini-series, or... (3 Replies)
Discussion started by: Neo
3 Replies

5. What is on Your Mind?

Cyber Dystopia Teaser (720 HD)

Working on a new cybersecurity, dystopian world series and made a short 2 min teaser today. Cyber Dystopia (720 HD) https://www.youtube.com/watch?v=g9Ca07J_YC8 If anyone has any ideas for the story, please write out some story lines in the comments and join the production team! (1 Reply)
Discussion started by: Neo
1 Replies
GIT-CHECK-MAILMAP(1)						    Git Manual						      GIT-CHECK-MAILMAP(1)

NAME
git-check-mailmap - Show canonical names and email addresses of contacts SYNOPSIS
git check-mailmap [options] <contact>... DESCRIPTION
For each "Name <user@host>" or "<user@host>" from the command-line or standard input (when using --stdin), look up the person's canonical name and email address (see "Mapping Authors" below). If found, print them; otherwise print the input as-is. OPTIONS
--stdin Read contacts, one per line, from the standard input after exhausting contacts provided on the command-line. OUTPUT
For each contact, a single line is output, terminated by a newline. If the name is provided or known to the mailmap, "Name <user@host>" is printed; otherwise only "<user@host>" is printed. MAPPING AUTHORS
If the file .mailmap exists at the toplevel of the repository, or at the location pointed to by the mailmap.file or mailmap.blob configuration options, it is used to map author and committer names and email addresses to canonical real names and email addresses. In the simple form, each line in the file consists of the canonical real name of an author, whitespace, and an email address used in the commit (enclosed by < and >) to map to the name. For example: Proper Name <commit@email.xx> The more complex forms are: <proper@email.xx> <commit@email.xx> which allows mailmap to replace only the email part of a commit, and: Proper Name <proper@email.xx> <commit@email.xx> which allows mailmap to replace both the name and the email of a commit matching the specified commit email address, and: Proper Name <proper@email.xx> Commit Name <commit@email.xx> which allows mailmap to replace both the name and the email of a commit matching both the specified commit name and email address. Example 1: Your history contains commits by two authors, Jane and Joe, whose names appear in the repository under several forms: Joe Developer <joe@example.com> Joe R. Developer <joe@example.com> Jane Doe <jane@example.com> Jane Doe <jane@laptop.(none)> Jane D. <jane@desktop.(none)> Now suppose that Joe wants his middle name initial used, and Jane prefers her family name fully spelled out. A proper .mailmap file would look like: Jane Doe <jane@desktop.(none)> Joe R. Developer <joe@example.com> Note how there is no need for an entry for <jane@laptop.(none)>, because the real name of that author is already correct. Example 2: Your repository contains commits from the following authors: nick1 <bugs@company.xx> nick2 <bugs@company.xx> nick2 <nick2@company.xx> santa <me@company.xx> claus <me@company.xx> CTO <cto@coompany.xx> Then you might want a .mailmap file that looks like: <cto@company.xx> <cto@coompany.xx> Some Dude <some@dude.xx> nick1 <bugs@company.xx> Other Author <other@author.xx> nick2 <bugs@company.xx> Other Author <other@author.xx> <nick2@company.xx> Santa Claus <santa.claus@northpole.xx> <me@company.xx> Use hash # for comments that are either on their own line, or after the email address. GIT
Part of the git(1) suite Git 2.17.1 10/05/2018 GIT-CHECK-MAILMAP(1)
All times are GMT -4. The time now is 05:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy