From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13381] New: Juniper Networks Certified Expert Security
Date: Wed, 16 Dec 2020 16:41:02 +0000 [thread overview]
Message-ID: <bug-13381-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=13381
Bug ID: 13381
Summary: Juniper Networks Certified Expert Security
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: harika.2019 at rediffmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
The Juniper Networks Certified Expert Security (JNCES) is aimed to authorize
the networking experts? ability to deploy, implement, manage and fix
JUNOS-based security platforms. The Juniper certified security professionals
have the capability to deploy manage, configure and troubleshoot the junos for
the businesses.
https://www.fieldengineer.com/skills/juniper-networks-certified-expert-security
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-12-16 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 16:41 bugzilla at busybox.net [this message]
2020-12-21 9:36 ` [Buildroot] [Bug 13381] Juniper Networks Certified Expert Security bugzilla at busybox.net
2021-01-13 5:45 ` bugzilla at busybox.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-13381-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.