__  __    __   __  _____      _            _          _____ _          _ _ 
 |  \/  |   \ \ / / |  __ \    (_)          | |        / ____| |        | | |
 | \  / |_ __\ V /  | |__) | __ ___   ____ _| |_ ___  | (___ | |__   ___| | |
 | |\/| | '__|> <   |  ___/ '__| \ \ / / _` | __/ _ \  \___ \| '_ \ / _ \ | |
 | |  | | |_ / . \  | |   | |  | |\ V / (_| | ||  __/  ____) | | | |  __/ | |
 |_|  |_|_(_)_/ \_\ |_|   |_|  |_| \_/ \__,_|\__\___| |_____/|_| |_|\___V 2.1
 if you need WebShell for Seo everyday contact me on Telegram
 Telegram Address : @jackleet
        
        
For_More_Tools: Telegram: @jackleet | Bulk Smtp support mail sender | Business Mail Collector | Mail Bouncer All Mail | Bulk Office Mail Validator | Html Letter private



Upload:

Command:

[email protected]: ~ $
GCR
===
GCR is a library for displaying certificates and crypto UI, accessing
key stores. It also provides the viewer for crypto files on the GNOME
desktop.

GCK is a library for accessing PKCS#11 modules like smart cards, in a
(G)object oriented way.

Building
--------

You can build GCR using [Meson] with the following build commands (replace
`$BUILDDIR` with your chosed build directory).

```
$ meson setup $BUILDDIR
$ meson compile -C $BUILDDIR
$ meson install -C $BUILDDIR
```

Versions
--------
Starting version 4.0.0, gcr and gck use semantic versioning.

To denote unstable versions, the micro version number will correspond to 90 or
higher, e.g. `4.$MINOR.90`.

Contributing
------------
The code and issue tracker of GCR can be found at the GNOME GitLab instance at
https://gitlab.gnome.org/GNOME/gcr.

If you would like to get involved with GNOME projects, please also visit our
[Newcomers page] on the Wiki.

Documentation
-------------
The documentation for GCR and GCK is built using [gi-docgen].

You can find the nightly documentation at:

* Gck: https://gnome.pages.gitlab.gnome.org/gcr/gck-2/
* Gcr: https://gnome.pages.gitlab.gnome.org/gcr/gcr-4/

You can find the older GCR documentation at:

* Gck: https://gnome.pages.gitlab.gnome.org/gcr/gck-1/
* Gcr: https://gnome.pages.gitlab.gnome.org/gcr/gcr-3/
* GcrUI: https://gnome.pages.gitlab.gnome.org/gcr/gcr-ui-3/

Debug tracing
-------------
The Gcr and Gck libraries contain statements which help debug flow
and logic. In many cases these help you track down problems.

Use the environment variable `G_MESSAGES_DEBUG='all'` or
`G_MESSAGES_DEBUG='xxx'` to display either all messages or a specific categories
of debug messages. You can separate categories in this list with spaces, commas
or semicolons. Gcr library uses category 'Gcr', while Gck library uses category
'Gck'.

```
# Example to display all debug messages:
$ G_MESSAGES_DEBUG=all gcr-viewer /path/to/certificate.crt

# Example to display debug messages for a specific category:
$ G_MESSAGES_DEBUG="Gcr" gcr-viewer /path/to/certificate.crt
```

For the Gck debug messages simply replace 'Gcr' with 'Gck' in the above
examples.

More information
----------------
To discuss issues with developers and other users, you can post to the
[GNOME Discourse instance](https://discourse.gnome.org).



[gi-docgen]: https://gnome.pages.gitlab.gnome.org/gi-docgen/
[Meson]: https://mesonbuild.com
[Newcomers page]: https://wiki.gnome.org/TranslationProject/JoiningTranslation

Filemanager

Name Type Size Permission Actions
NEWS.gz File 5.76 KB 0644
README.md File 2.44 KB 0644
changelog.Debian.gz File 3.28 KB 0644
copyright File 2.74 KB 0644
Filemanager