Download the 5 files via links below (you may need to <ctrl> click, select Download Linked File As. on each link) Save to your downloads folder
Please know. IF You have any DoD certificates already located in your keychain access, you will need to delete them prior to running the AllCerts.p7b file below.
https://militarycac.com/maccerts/AllCerts.p7b,
https://militarycac.com/maccerts/RootCert2.cer,
https://militarycac.com/maccerts/RootCert3.cer,
https://militarycac.com/maccerts/RootCert4.cer, and
Double click each of the files to install certificates into the login section of keychain
Select the Kind column, verify the arrow is pointing up, scroll down to certificate, look for all of the following certificates:
DOD EMAIL CA-33 through DOD EMAIL CA-34,
DOD EMAIL CA-39 through DOD EMAIL CA-44,
DOD EMAIL CA-49 through DOD EMAIL CA-52,
DOD EMAIL CA-59,
DOD ID CA-33 through DOD ID CA-34,
DOD ID CA-39 through DOD ID CA-44,
DOD ID CA-49 through DOD ID CA-52,
DOD ID CA-59
DOD ID SW CA-35 through DOD ID SW CA-38,
Decrypt samsung tv recordings. DOD ID SW CA-45 through DOD ID SW CA-48,
DoD Root CA 2 through DoD Root CA 5,
DOD SW CA-53 through DOD SW CA-58, and
DOD SW CA-60 through DOD SW CA-61
NOTE: If you are missing any of the above certificates, you have 2 choices,
1. Delete all of them, and re-run the 5 files above, or
2. Download the allcerts.zip file and install each of the certificates you are missing individually.
Errors:
Error 100001 Solution
Error 100013 Solution
You may notice some of the certificates will have a red circle with a white X . This means your computer does not trust those certificates
You need to manually trust the DoD Root CA 2, 3, 4, & 5 certificates
Double click each of the DoD Root CA certificates, select the triangle next to Trust, in the When using this certificate: select Always Trust, repeat until all 4 do not have the red circle with a white X.
You may be prompted to enter computer password when you close the window
Once you select Always Trust, your icon will have a light blue circle with a white + on it.
The 'bad certs' that have caused problems for Windows users may show up in the keychain access section on some Macs. These need to be deleted / moved to trash.
The DoD Root CA 2 & 3 you are removing has a light blue frame, leave the yellow frame version. The icons may or may not have a red circle with the white x
| or | DoD Interoperability Root CA 1 or CA 2 | certificate | |
| DoD Root CA 2 or 3 (light blue frame ONLY) | certificate | ||
| or | Federal Bridge CA 2016 or 2013 | certificate | |
| or | Federal Common Policy CA | certificate | |
| or | or | SHA-1 Federal Root CA G2 | certificate |
| or | US DoD CCEB Interoperability Root CA 1 | certificate |
If you have tried accessing CAC enabled sites prior to following these instructions, please go through this page before proceeding
Clearing the keychain (opens a new page)
Please come back to this page to continue installation instructions.
Step 5a: DoD certificate installation instructions for Firefox users
NOTE: Firefox will not work on Catalina (10.15.x), or last 4 versions of Mac OS if using the native Apple smartcard ability
Download AllCerts.zip, [remember where you save it].
double click the allcerts.zip file (it'll automatically extract into a new folder)
Option 1 to install the certificates (semi automated):
Simple dns plus. From inside the AllCerts extracted folder, select all of the certificates
<control> click (or Right click) the selected certificates, select Open With, Other. Eye of the beholder aga for mac.
In the Enable (selection box), change to All Applications
Select Firefox, then Open
You will see several dozen browser tabs open up, let it open as many as it wants.
You will eventually start seeing either of the 2 messages shown next
If the certificate is not already in Firefox, a window will pop up stating 'You have been asked to trust a new Certificate Authority (CA).'
Gtags Github
Check all three boxes to allow the certificate to: identify websites, identify email users, and identify software developers
or
'Alert This certificate is already installed as a certificate authority.' Click OK
Once you've added all of the certificates.
• Click Firefox (word) (upper left of your screen)
• Preferences
• Advanced (tab)
• Press Network under the Advanced Tab
• In the Cached Web Content section, click Clear Now (button).
• Quit Firefox and restart it
• Click Firefox (word) (upper left of your screen)
• Preferences
• Advanced (tab)
• Press Network under the Advanced Tab
• In the Cached Web Content section, click Clear Now (button).
• Quit Firefox and restart it
Option 2 to install the certificates (very tedious manual):
Click Firefox (word) (upper left of your screen)
Preferences
Advanced (tab on left side of screen)
Certificates (tab)
View Certificates (button)
Authorities (tab)
Import (button)
Browse to the DoD certificates (AllCerts) extracted folder you downloaded and extracted above.
Note: You have to do this step for every single certificate
Note2: If the certificate is already in Firefox, a window will pop up stating: 'Alert This certificate is already installed as a certificate authority (CA).' Click OK
Ctags For Mac Os X
Note3: If the certificate is not already in Firefox, a window will pop up stating 'You have been asked to trust a new Certificate Authority (CA).'
Check all three boxes to allow the certificate to: identify websites, identify email users, and identify software developers
Once you've added all of the certificates.
• Click Firefox (word) (upper left of your screen)
• Preferences
• Advanced (tab)
• Press Network under the Advanced Tab
• In the Cached Web Content section, click Clear Now (button).
• Quit Firefox and restart it
• Click Firefox (word) (upper left of your screen)
• Preferences
• Advanced (tab)
• Press Network under the Advanced Tab
• In the Cached Web Content section, click Clear Now (button).
• Quit Firefox and restart it
Step 6: Decide which CAC enabler you can / want to use
Only for Mac El Capitan (10.11.x or older)
After installing the CAC enabler, restart the computer and go to a CAC enabled website
NOTE: Mac OS Sierra (10.12.x), High Sierra (10.13.x), Mojave (10.14.x) or Catalina (10.15.x) computers no longer need a CAC Enabler.
Try to access the CAC enabled site you need to access now
Mac support provided by: Michael Danberry
| Developer(s) | Ken Arnold |
|---|---|
| Repository | |
| Operating system | Unix and Unix-like |
| Type | Programming tool(Specifically: Code navigation tool) |
| License | BSD |
Ctags is a programming tool that generates an index (or tag) file of names found in source and header files of various programming languages to aid code comprehension. Depending on the language, functions, variables, class members, macros and so on may be indexed. These tags allow definitions to be quickly and easily located by a text editor, a code search engine, or other utility. Alternatively, there is also an output mode that generates a cross reference file, listing information about various names found in a set of language files in human-readable form.
The original Ctags was introduced in BSD Unix 3.0 and was written by Ken Arnold, with Fortran support by Jim Kleckner and Pascal support by Bill Joy. It is part of the initial release of Single Unix Specification and XPG4 of 1992.
Editors that support ctags[edit]
Tag index files are supported by many source code editors, including:
- CodeLite (as its tag indexer for code completion)
- Cloud9 IDE (uses it internally but does not expose it)
- Emacs and XEmacs
- Far Manager (via Ctags Source Navigator plugin)
- Gedit (via gedit-symbol-browser-plugin)
- jEdit (via plugins CodeBrowser, Tags, ClassBrowser, CtagsSideKick, or Jump)
- mcedit (Midnight Commander builtin editor)
- Notepad++ (via OpenCTags plug-in)
- TextMate (via CodeBrowser-PlugIn)
- vi (and derivatives such as Elvis, Nvi, Vim, vile, etc.)
Variants of ctags[edit]
There are a few other implementations of the ctags program:
Etags[edit]
GNU Emacs comes with two ctags utilities, etags and ctags, which are compiled from the same source code. Etags generates a tag table file for Emacs, while the ctags command is used to create a similar table in a format understood by vi. They have different sets of command line options: For those options which only make sense for vi style tag files produced by the ctags command, etags could not recognize them and would ignore them.[1]
Exuberant Ctags[edit]
Exuberant Ctags, written and maintained by Darren Hiebert until 2009,[2] was initially distributed with Vim, but became a separate project upon the release of Vim 6. It includes support for Emacs and
etags compatibility.[3][4]Exuberant Ctags includes support for over 40 programming languages with the ability to add support for even more using regular expressions.
Universal Ctags[edit]
Universal Ctags is a fork of Exuberant Ctags, with the objective of continuing its development. Upgrade office for mac 2008 to 2016. A few parsers are rewritten to better support the languages.[5]
Language-specific[edit]
Hasktags creates ctags compatible tag files for Haskell source files.[6] It includes support for creating Emacs etags files.[7]
jsctags is a ctags-compatible code indexing solution for JavaScript.[8] It is specialized for JavaScript and uses the CommonJS packaging system. It outperforms Exuberant Ctags for JavaScript code, finding more tags than the latter.[9]
Tags file formats[edit]
Ctags Gtags
There are multiple tag file formats. Some of them are described below. In the following, x## represents the byte with hexadecimal representation ##. Every line ends with a line feed (LF, n = x0A).
Ctags and descendants[edit]
The original ctags and the Exuberant/Universal descendants have similar file formats:[10]
Ctags[edit]
This is the format used by vi and various clones. The tags file is normally named 'tags'.
The tags file is a list of lines, each line in the format:
The fields are specified as follows:
- {tagname} – Any identifier, not containing white space
- t – Exactly one tab (x0b) character, although many versions of vi can handle any amount of white space.
- {tagfile} – The name of the file where {tagname} is defined, relative to the current directory
- {tagaddress} – An ex mode command that will take the editor to the location of the tag. For POSIX implementations of vi this may only be a search or a line number, providing added security against arbitrary command execution.
The tags file is sorted on the {tagname} field which allows for fast searching of the tags file.
Extended Ctags[edit]
This is the format used by Vim's Exuberant Ctags and Universal Ctags. These programs can generate an original ctags file format or an extended format that attempts to retain backward compatibility.
The extended tags file is a list of lines, each line in the format:
The fields up to and including {tagaddress} are the same as for ctags above.
Optional additional fields are indicated by square brackets ('[.]') and include:
- ;' – semicolon + double quote: Ends the {tagaddress} in a way that looks like the start of a comment to vi or ex.
- {tagfield} – extension fields: tab separated 'key:value' pairs for more information.
This format is compatible with non-POSIX vi as the additional data is interpreted as a comment. POSIX implementations of vi must be changed to support it, however.[10]
Etags[edit]
This is the format used by Emacs etags. The tags file is normally named 'TAGS'.
The etags files consists of multiple sections—one section per input source file. Sections are plain-text with several non-printable ascii characters used for special purposes. These characters are represented as bracketed hexadecimal codes below.
A section starts with a two line header (the first two bytes make up a magic number):
The header is followed by tag definitions, one definition per line, with the format:
{tagname}x01 can be omitted if the name of the tag can be deduced from the text at the tag definition.
Example[edit]
Given a single line test.c source code:
The TAGS (etags) file would look like this:
The tags (ctags) file may look like:
or more flexibly using a search:
See also[edit]
References[edit]
- ^
etags.emacs(1)– Linux General Commands Manual - ^'Exuberant Ctags'. ctags.sourceforge.net.
- ^'Vim documentation: version6: ctags-gone'. Retrieved 2007-04-28.
- ^
etags.ctags(1)– Linux General Commands Manual - ^'Universal Ctags Documentation'. Retrieved 2018-08-02.
- ^'GHC documentation: Other Haskell utility programs'. Retrieved 2010-03-05.
- ^'hasktags: Produces ctags 'tags' and etags 'TAGS' files for Haskell programs'. Retrieved 2010-03-05.
- ^'pcwalton github repository for jsctags'. Archived from the original on 2010-08-22. Retrieved 2016-09-10.
- ^Patrick Walton. 'Introducing jsctags'. Retrieved 2010-05-25.
- ^ ab'Proposal for extended Vi tags file format'. Retrieved 2007-06-30.
External links[edit]
| The Wikibook Guide to Unix has a page on the topic of: Commands |
ctags: create a tags file – Commands & Utilities Reference, The Single UNIX Specification, Issue 7 from The Open Group
Retrieved from 'https://en.wikipedia.org/w/index.php?title=Ctags&oldid=972397004'
