리눅스에서 Go를 스크립트 언어로 사용하기
This is a Korean translation of a prior post by Ignat Korchagin.
Cloudflare에서는 Go를 좋아합니다. Go는 많은 내부 소프트웨어 프로젝트와 거대한 파이프라인 시스템의 일부로도 사용되고 있습니다. 하지만 Go를 한단계 더 끌어 올려서 우리가 선호하는 운영체제인 리눅스의 스크립트 언어로 사용할 수 있을까요?
gopher image CC BY 3.0 Renee French | Tux image CC0 BY OpenClipart-Vectors
Go를 왜 스크립트 언어로 고려하는가
간단한 답은: 왜 안되나요? Go는 비교적 쉽게 배울 수 있고 아주 복잡하지도 않고, 코드를 처음부터 작성해야 하는 일을 피하기 위해 재사용 가능한 라이브러리의 거대한 에코시스템이 있습니다. 추가로 다음과 같은 잠재적인 장점이 있습니다:
- 여러분의 Go 프로젝트를 위한 Go 기반 빌드 시스템:
go build명령은 대부분의 소규모이며 독립적인 프로젝트에 적합합니다. 더 복잡한 프로젝트는 대부분 별도의 빌드 시스템/스크립트 세트를 채용하고 있습니다. 이런 스크립트도 Go로 작성 가능하지 않을까요? - 바로 이용 가능한 별도 권한 없는 패키지 관리: 여러분의 프로그램에서 서드 파티 라이브러리를 사용하고 싶다면 단순히
go get을 사용하면 됩니다. 그리고 이 코드가 여러분의GOPATH에 설치되므로, 서드파티 라이브러리를 받는 것은 시스템의 별도 운영 권한을 필요로 하지 않습니다(다른 일부 스크립트 언어와 달리). 이것은 대규모의 기업 환경에서 특히 유용합니다. - 초기 단계 프로젝트를 위한 빠른 코드 프로토타이핑: 최초로 돌아가는 코드를 작성할 때 컴파일 되기 위해서 많은 편집을 해야 하고 "편집->빌드->체크" 사이클을 위해 많은 키보드 입력을 Continue reading
New to the INE Video Course Library: Introduction to Azure Design and Implementation
Last week we added a new Azure course to our video library. This is the first course of it’s kind and can be found on the INE streaming site and also for sale on ine.com
Why Study Azure:
Azure is Microsoft’s version of web services management. Azure is a great option for DevOps professionals due to it’s diversity. Azure allows you to create intelligent apps using the language of your choice, including Node.js, Java and .NET, and works for both PC and Mac users. With 100+ services and tools to manage apps, Azure Design has become a favorite among many large companies and should be considered an essential study topic for DevOps professionals.
About the course:
Length- 1 hour 23 minutes
Instructor- Gary Bushey
In this Series we will take a look at what Azure is, including what IaaS, PaaS, and SaaS mean. We will thoroughly discuss Azure PaaS and some of the specific technologies used with PaaS, namely containers and artificial intelligence.
In the second section, we will discuss how to move your applications to Azure. The first video will provide an introduction to the Architectural decisions to make when moving your application, including which style Continue reading
Enterprise versus Provider?
Two ideas that are widespread, and need to be addressed—
First, there is no enterprise, there are no service providers. There are problems, and there are solutions.
When I was young (and even more foolish than I am now) I worked for a big vendor. When this big vendor split the enterprise and service provider teams, I thought this kindof made sense. After all, providers have completely different requirements, and should therefore run with completely different technologies, equipment, and software. When I thought of providers in those days, I thought of big transit network operators, like AT&T, and Verizon, and Orange, and Level3, and Worldcom, and… The world has changed since then, but our desire to split the world into two neat halves has not.
If you want to split the world into two halves, split it this way: There are companies who consider the network an asset, and companies that consider the network a Continue reading
The Challenges of Securing the Multi-Cloud Network
The digital transformation driving the adoption of multi-cloud networks requires an equivalent security transformation.
Automation Isn’t About Building a Button to Press
This is a guest blog post by Carl Buchmann, Managing Solution Consultant at TeraMach. Carl attended the Building Network Automation Solutions online course in 2017.
There is one thing I regret not doing sooner during my automation journey, and that is adopting Git and a proper IDE/text editor that has built-in source control management. I personally use Microsoft Visual Studio Code, as it has Git built in and has many great extensions to validate code syntax.
Read more ...Plenty of MEC Chatter Expected at Mobile World Congress 2018
HPE, Ericsson, Nokia, and Huawei are expected to show MEC-supported use cases.
Security Experts Shine a Spotlight on Automation, Managed Services at Mobile World Congress
The rise of 5G and IoT devices means the threat landscape is larger than ever.
Understanding IPv6: Link-Local ‘Magic’ (Part 2 of 7)
For those of you new to IPv6, what I am about to show you is going to look a lot like a magic trick. I’m going to bring up an IPv6 IGP neighbor relationship (OSPFv3) between two routers. This doesn’t sound like a magic trick, I know. But what if I told you I am going to do this without putting any IPv6 addresses into the configurations of either routers?
Like any true magician, I must start my magic act with letting you know I have nothing up my sleeves. So let’s review the facts:
- IPv6 unicast routing is globally enabled on both routers
- IPv6 OSPFv3 is enabled via the one global command, “ipv6 router ospf 6”
- Each router has an interface in an out-of-band management network (OOB mgt.) in the subnet 14.14.14.0/24.
- RouterA is 14.14.14.101 and RouterB is 14.14.14.102 in this OOB management network
- The IPv4 addresses for the OOB management interfaces are the only IP addresses in the configurations
- Gig1/0/1 on both routers only has only two IPv6 commands on it, as shown below
- Router A is monitoring the gig1/0/1 interface and sending the traffic to a Spirent Continue reading
Understanding IPv6: Link-Local ‘Magic’ (Part 2 of 7)
For those of you new to IPv6, what I am about to show you is going to look a lot like a magic trick. I’m going to bring up an IPv6 IGP neighbor relationship (OSPFv3) between two routers. This doesn’t sound like a magic trick, I know. But what if I told you I am going to do this without putting any IPv6 addresses into the configurations of either routers?
Like any true magician, I must start my magic act with letting you know I have nothing up my sleeves. So let’s review the facts:
- IPv6 unicast routing is globally enabled on both routers
- IPv6 OSPFv3 is enabled via the one global command, “ipv6 router ospf 6”
- Each router has an interface in an out-of-band management network (OOB mgt.) in the subnet 14.14.14.0/24.
- RouterA is 14.14.14.101 and RouterB is 14.14.14.102 in this OOB management network
- The IPv4 addresses for the OOB management interfaces are the only IP addresses in the configurations
- Gig1/0/1 on both routers only has only two IPv6 commands on it, as shown below
- Router A is monitoring the gig1/0/1 interface and sending the traffic to a Spirent Continue reading
Understanding IPv6: The Journey Begins (Part 1 of 7)
IPv6 and I met back in the early 2000s. I really didn’t see the big deal or know what all the RFCs were about. This stuff was easy. Of course, at the time, my thoughts were barely even scratching at the surface, and I still believed IPv6 was just IPv4 with 128 bits. I was in what I now refer to as the “Checklist IPv6” phase.
“Checklist IPv6” was actually a great place for me to start. I had to remember only a few things while I was configuring the routers. Then I could kick back and let the magic of routing protocols work. Voila, IPv6 addresses would show up in the routing table of some other router in the lab. Ping to confirm, and I was done.
IPv6 “I know nothing” phase
The quote “The more you know, the more you realize how much you don’t know. The less you know, the more you think you know,” is attributed to David T. Freeman. I discovered the truth of this as I began digging deeper. The trigger to this phase was when I realized that IPv6 was clearly not IPv4 with 128 bits. When did that happen? When Continue reading
Understanding IPv6: The Journey Begins (Part 1 of 7)
IPv6 and I met back in the early 2000s. I really didn’t see the big deal or know what all the RFCs were about. This stuff was easy. Of course, at the time, my thoughts were barely even scratching at the surface, and I still believed IPv6 was just IPv4 with 128 bits. I was in what I now refer to as the “Checklist IPv6” phase.
“Checklist IPv6” was actually a great place for me to start. I had to remember only a few things while I was configuring the routers. Then I could kick back and let the magic of routing protocols work. Voila, IPv6 addresses would show up in the routing table of some other router in the lab. Ping to confirm, and I was done.
IPv6 “I know nothing” phase
The quote “The more you know, the more you realize how much you don’t know. The less you know, the more you think you know,” is attributed to David T. Freeman. I discovered the truth of this as I began digging deeper. The trigger to this phase was when I realized that IPv6 was clearly not IPv4 with 128 bits. When did that happen? When Continue reading
Firepower FMC API – Initial Observations
As many of you know, I am not a developer but I do occasionally hack stuff together. This article is just some of the initial things I have learned working with the Firepower Management Console API.
A good place to start is the Firepower REST API Quick Start Guide. This can be found at the following URL.
Firepower REST API Quick Start Guide
One thing to note is that there is a recommendation to use a dedicated username for the API. I would go a step beyond that with a recommendation for testing and development. During development, I currently have a username for the FMC UI, a username for the API Explorer and a username for whatever tool I’m working with (Postman or a Python Scripts). The reason for the extra accounts is that logging in to any of the UI’s tends to generate a new token (and invalidate the old one). This causes a constant reauthentication to the Web Interfaces.
Here is a screenshot of Postman doing an initial authentication — Post to retrieve an access token.
Generate Token URL
https://<server-ip>/api/fmc_platform/v1/auth/generatetoken
Sending a post with basic authentication to the URL will produce an “x-auth-access-token”. This is good for 30 minutes Continue reading
Firepower FMC API – Initial Observations
As many of you know, I am not a developer but I do occasionally hack stuff together. This article is just some of the initial things I have learned working with the Firepower Management Console API.
A good place to start is the Firepower REST API Quick Start Guide. This can be found at the following URL.
Firepower REST API Quick Start Guide
One thing to note is that there is a recommendation to use a dedicated username for the API. I would go a step beyond that with a recommendation for testing and development. During development, I currently have a username for the FMC UI, a username for the API Explorer and a username for whatever tool I’m working with (Postman or a Python Scripts). The reason for the extra accounts is that logging in to any of the UI’s tends to generate a new token (and invalidate the old one). This causes a constant reauthentication to the Web Interfaces.
Here is a screenshot of Postman doing an initial authentication — Post to retrieve an access token.
Generate Token URL
https://<server-ip>/api/fmc_platform/v1/auth/generatetoken
Sending a post with basic authentication to the URL will produce an “x-auth-access-token”. This is good for 30 minutes Continue reading
Firepower FMC API – Initial Observations
As many of you know, I am not a developer but I do occasionally hack stuff together. This article is just some of the initial things I have learned working with the Firepower Management Console API.
A good place to start is the Firepower REST API Quick Start Guide. This can be found at the following URL.
Firepower REST API Quick Start Guide
One thing to note is that there is a recommendation to use a dedicated username for the API. I would go a step beyond that with a recommendation for testing and development. During development, I currently have a username for the FMC UI, a username for the API Explorer and a username for whatever tool I’m working with (Postman or a Python Scripts). The reason for the extra accounts is that logging in to any of the UI’s tends to generate a new token (and invalidate the old one). This causes a constant reauthentication to the Web Interfaces.
Here is a screenshot of Postman doing an initial authentication — Post to retrieve an access token.
Generate Token URL
https://<server-ip>/api/fmc_platform/v1/auth/generatetoken
Sending a post with basic authentication to the URL will produce an “x-auth-access-token”. This is good for 30 minutes Continue reading
Starting Today: NDSS Highlights the Best in Internet Security Research
You’ve undoubtedly heard about all sorts of Internet security vulnerabilities and incidents causing harm around the world, but the flip side of all that doom and gloom is all the promising efforts underway to create a more secure, private, and trusted Internet. Starting today and going through Wednesday (18-21 February), the Network and Distributed Systems Security (NDSS) Symposium takes place to present groundbreaking research in the world of Internet security.
This year marks the 25th anniversary of NDSS, and the Internet Society is proud to have been associated with it for over 20 years now. A key focus of the Internet Society has long been improving trust in the global open Internet. In order to promote this trust, we need new and innovative ideas and research on the security and privacy of our connected devices and the Internet that brings them together. NDSS is a top tier forum for highlighting this research.
NDSS 2018 is four full days featuring:
- Two exciting keynotes from Ari Juels and Parisa Tabriz
- Four workshops on Binary Analysis Research (BAR), Decentralized IoT Security and Standards (DISS), DNS Privacy (DNSPRIV), and Usable Security (USEC).
- A full program of 71 excellent peer-reviewed research papers organized into Continue reading