Sponsored Content
Full Discussion: Help me understand VPN
Top Forums UNIX for Beginners Questions & Answers Help me understand VPN Post 303045434 by Circuits on Friday 20th of March 2020 12:50:42 PM
Old 03-20-2020
Quote:
Originally Posted by stomp
There are lots of software packages and some different protocols that are used to operate VPNs.

I see, so then are both WireGuard and OpenConnect doing the same thing? I am just wondering because based on what I read on the OpenConnect homepage it seems like they have tailored their service to work with certain vendors like Cisco, which is the provider we use. I managed to get OpenConnect VPN working but I would rather use WireGuard if I can simply based on the article's description of it. So, as long as they are doing the same thing, why wouldn't I use WireGuard? Is it possible that a VPN can be tailored to work with certain vendors like Cisco? If they can, then perhaps I should be using OpenConnect.
 

9 More Discussions You Might Find Interesting

1. Cybersecurity

Trying to use MySql through a VPN

Hiya All, Problem after problem. I can't fire up MySql on my FC-3 Server at work I need to remote dial in past a VPN I get the following message Below. Is it something Obvious I need to do wrt to Config etc? I can't belive I cannot acces a STD DB past a VPN! other people in work do... (0 Replies)
Discussion started by: marty 600
0 Replies

2. UNIX for Dummies Questions & Answers

help with vpn

We have an older model DG Aviion Unix system and we're trying to switch to VPN but we can't talk to the Unix box... can't ping or telnet to it, but we can talk to all our other systems (PC/NT servers). Is there a network/tcpip setting we're missing? Something we have to change/set, either on... (0 Replies)
Discussion started by: markb
0 Replies

3. UNIX for Dummies Questions & Answers

One VPN question

Hi, My setup is as follows: 1) HeadOffice----->Private subnet: 192.168.0.0 2) Branch1-------->Private subnet: 192.168.200.0 I'm connecting from branch1 to headoffice thru VPN and I'm able to access all PC's except SCO UNIXWARE 7.1.1 box. I have made a search before posting this... (7 Replies)
Discussion started by: tayyabq8
7 Replies

4. IP Networking

Vpn

Hi, I have two unix networks connected via VPN via IPsec. I am using snapgear vpn devices at each location. The two devices can ping one another, as well as the unix network behind the respected devices. The unix machines can ping their local vpn devices. However, I am having issues pinging... (1 Reply)
Discussion started by: l8kerboi23
1 Replies

5. Linux

VPN Solutions

Hello Friends I want to know about VPN Solutions under Linux Please help me :confused: (6 Replies)
Discussion started by: jaibw
6 Replies

6. UNIX for Advanced & Expert Users

VPN and then

Hi, I want to work on a remote unix server, then on a windows XP station I have a Forticlient that makes a VPN to the network on which the server is situated. But then I do not know how to work with. In DOS box (cmd BOX) I issue: telnet myserver but It does not know IT. Any idea ? Many thanks. (2 Replies)
Discussion started by: big123456
2 Replies

7. Solaris

vpn not connecting

Hi, I have been using using internet explorer on windows for connecting with production server using vpn connection. i want to use same vpn to connect from solaris system to the production server.it is not connecting is there solution (0 Replies)
Discussion started by: malikshahid85
0 Replies

8. Cybersecurity

VPN Security

Hello Gurus : I had a question about VPN connection . Say for instance i have to connect from my point A to point B (Is the place where i initiate the VPN connection ) . From there i connect to point C (i.e Bank) . My question is this a secure connection . (from point A to C) Thanks... (3 Replies)
Discussion started by: tsbiju
3 Replies

9. Solaris

Vpn

Hi. Yesterday I installed Solaris 11.3 and I tried to setup a VPN but I didn't find how to make it. I saw the "network manager" where I found the ethernet connection but I didn't find where to add a VPN connection. When I used Debian Linux there was NetworkManagerVPN that with a GUI I... (0 Replies)
Discussion started by: Jena
0 Replies
GIT-SHORTLOG(1) 						    Git Manual							   GIT-SHORTLOG(1)

NAME
       git-shortlog - Summarize 'git log' output

SYNOPSIS
       git log --pretty=short | git shortlog [<options>]
       git shortlog [<options>] [<revision range>] [[--] <path>...]

DESCRIPTION
       Summarizes git log output in a format suitable for inclusion in release announcements. Each commit will be grouped by author and title.

       Additionally, "[PATCH]" will be stripped from the commit description.

       If no revisions are passed on the command line and either standard input is not a terminal or there is no current branch, git shortlog will
       output a summary of the log read from standard input, without reference to the current repository.

OPTIONS
       -n, --numbered
	   Sort output according to the number of commits per author instead of author alphabetic order.

       -s, --summary
	   Suppress commit description and provide a commit count summary only.

       -e, --email
	   Show the email address of each author.

       --format[=<format>]
	   Instead of the commit subject, use some other information to describe each commit.  <format> can be any string accepted by the --format
	   option of git log, such as * [%h] %s. (See the "PRETTY FORMATS" section of git-log(1).)

	       Each pretty-printed commit will be rewrapped before it is shown.

       -c, --committer
	   Collect and show committer identities instead of authors.

       -w[<width>[,<indent1>[,<indent2>]]]
	   Linewrap the output by wrapping each line at width. The first line of each entry is indented by indent1 spaces, and the second and
	   subsequent lines are indented by indent2 spaces.  width, indent1, and indent2 default to 76, 6 and 9 respectively.

	   If width is 0 (zero) then indent the lines of the output without wrapping them.

       <revision range>
	   Show only commits in the specified revision range. When no <revision range> is specified, it defaults to HEAD (i.e. the whole history
	   leading to the current commit).  origin..HEAD specifies all the commits reachable from the current commit (i.e.  HEAD), but not from
	   origin. For a complete list of ways to spell <revision range>, see the "Specifying Ranges" section of gitrevisions(7).

       [--] <path>...
	   Consider only commits that are enough to explain how the files that match the specified paths came to be.

	   Paths may need to be prefixed with "-- " to separate them from options or the revision range, when confusion arises.

MAPPING AUTHORS
       The .mailmap feature is used to coalesce together commits by the same person in the shortlog, where their name and/or email address was
       spelled differently.

       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-SHORTLOG(1)
All times are GMT -4. The time now is 07:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy