Best match

Most recent

Fiserv

Transfer

Fiserv is transferring the listing of its common stock to the New York Stock Exchange (NYSE) from the NASDAQ Global Select Market (NASDAQ).

Fiserv to Transfer Listing to New York Stock Exchange

https://www.bing.com/th?id=ODF.fJDJ4f2BFbmOkQx_rnDw3Q&pid=news

YAHOO!Finance

Seth Klarman

Investor

Stock

In this article, we discuss the 10 stocks that legendary value investor Seth Klarman is selling in 2023. If you want to see more stocks in this selection, check out Legendary Value Investor Seth Klarman is Selling These 5 Stocks in 2023.

https://www.bing.com/th?id=OVFT.xOEvbbKZOso4Eh9iED_-bC&pid=News

Legendary Value Investor Seth Klarman is Selling These 10 Stocks in 2023

Yahoo Finanzas

Get Free Exclusive PDF Sample Copy of This Research @  Some of the key players profiled in the study are: IBM Corporation (United States), Capgemini SE (France), Oracle Corporation (United States), Fiserv,

Financial Crime and Fraud Management Solutions Market to Huge Growth : Capgemini, Fiserv, IBM

https://www.bing.com/th?id=ODF.WbwBhyLf0mt3sgNOM6CYtQ&pid=news

The Buffalo News

Information technology

In this article, we will take a look at the 12 best information technology services stocks to buy. To see more such companies, go directly to 5 Best Information Technology Services Stocks to Buy.

12 Best Information Technology Services Stocks to Buy

Yahoo Finance

Global

Players

Bank

This report provides strategists, marketers and senior management with the critical information they need to assess the market.The global digital banking platform market grew from $6.09 billion in 2022 to $6.

https://www.bing.com/th?id=OVFT.Dmm1sDXsfiKNjYGpLsSAEC&pid=News

Global Digital Banking Platform Market Report 2023: Major Players Include Appway, Crealogix Holding, EdgeVerve Systems and Fiserv

https://www.bing.com/th?id=ODF.LBn5t3rqxzpf5jMTBU81BA&pid=news

Robe

Centre Region, France

The Robe Visitor Information Centre is situated in the main street of Robe, opposite Robe Town Beach and Foreshore area. It is part of the building that houses the Robe Public Library, the Local History Collection, the Robe Institute and the Lapwing Art ...

Robe Visitor Information Centre

South Australia

Its solutions help companies manage their digital workflows. It ranks 2nd in our list of the best information technology services stocks to buy. ServiceNow Inc. (NYSE:NOW) posted strong Q1 results.

5 Best Information Technology Services Stocks to Buy

Insider Monkey

Get the most recent info and news about Fiserv on HackerNoon, where 10k+ technologists publish stories for 4M+ monthly readers.

Fiserv, Inc., together with its subsidiaries, provides payment and financial services technology worldwide. The company operates through Acceptance, Fintech, and Payments segments. The Acceptance segment provides point-of-sale merchant acquiring and digital commerce services; mobile payment services; security and fraud protection products; Carat, an omnichannel commerce solution; Clover, a cloud-based point-of-sale and business management platform; and Clover Connect, an independent software vendors platform. This segment distributes through various channels, including direct sales teams, strategic partnerships with agent sales forces, independent software vendors, financial institutions, and other strategic partners. The Fintech segment offers customer deposit and loan accounts, as well as manages an institution's general ledger and central information files. This segment also provides digital banking, financial and risk management, professional services and consulting, item processing and source capture, and other products and services. The Payments segment offers card transactions, such as debit, credit, and prepaid card processing and services; security and fraud protection products; card production; print services; and various network services, as well as non-card digital payment software and services, including bill payment, account-to-account transfers, person-to-person payments, electronic billing, and security and fraud protection products. It serves business, banks, credit unions, other financial institutions, merchants, and corporate clients. The company was incorporated in 1984 and is headquartered in Milwaukee, Wisconsin.

The growing popularity of online banking as well as modern payment systems such as Revolut, N26, and Monzo suggests that traditional banking may be moving towards its demise. On the one hand, more than 50% of consumers still performed monthly visits to physical bank offices with 80% of them making at least one such visit within the 6 months preceding the . Fiserv survey However, this trend may be partially supported by older baby boomer audiences who do not feel at ease with smartphone applications and other remote banking instruments. On the other hand, major practitioners including Citibank are reducing their physical presence at an alarming rate moving away from brick-and-mortar branches. This article considers a number of trends in the financial industry to identify if we are getting close to the death of traditional banking. Perceived Trustworthiness The most widespread sphere of criticism for modern fintech companies is their lack of ‘tangibility’ making them appear than brick-and-mortar banks and more prone to ‘disappear into thin air’. Several stories on Reddit and other resources describe this problem citing the inability to reach the outsourced customer support, quickly react to the emerging issue to stop the fraudulent transfer of money, and the slow response of these organizations to both customer and police requests. less reliable Considering the fact that a smartphone app may be the only contact you have with the bank, this further exposes you to the risk of losing access to all your money in the case of any technical problems, the loss or theft of your smartphone, or the inability to log into your account. This is a highly concerning sign considering the fact that many mobile payment providers do not have internal call centers and may not be available via voice calls on a 24/7 basis. Technological Aptitude The above-mentioned problems may seem insignificant considering the rates of operational and shown by major physical banks. Large brick-and-mortar organizations including the Bank of Scotland, Lloyds, and Barclays have all reported 30+ significant breaches across their internal systems per month. security issues While born-digital mobile systems were originally created in the age of blockchain technologies, full anonymity, and cashless transactions, their traditional counterparts had to teach themselves these skills to survive the competition. In many cases, their old systems fail to learn new tricks and may be seen as clumsy and outdated by younger digital-native audiences. Many of them also lack the transparency of their modern counterparts that update you about any issues via multiple social media profiles and make it a rule to respond to your questions on Instagram or Twitter within one hour. Costs of Use Most proponents of modern technologies cite lower costs of use as one of the main benefits of modern solutions for mobile payments. N26, TransferWise, and Revolut charge you £0 for issuing and using their cards and 2% on the average for transferring money to anywhere in the world. All transfers occur instantly and you do not have to pay any fees when you are not using their services. On the contrary, most physical banks charge substantially higher payment processing fees for inter-bank transactions while processing periods may amount to 2-3 days in some cases. This also disrupts the retail industry since many organizations in it do not want to pay the ever-increasing charges for all check-out operations performed with banking cards. Lifestyle Integration An avid iPhone user is generally more willing to buy the ‘Created by Apple, not a bank’ Apple Card rather than the actual Goldman Sachs product being sold under this name. The Web 3.0 environment we all live in implies that our social media profiles may be more trustworthy and traceable than the documents provided by us to a bank branch. This is well understood by major brands including Facebook that add the capability to send and receive money directly to their instant messaging chats. When a friend in need is asking you for a $100 pre-salary loan, it is more logical to make this transfer from the same app rather than switch to a third-party interface or make a live visit to your bank. Even in the case of fraudulent scam attempts, digital payment methods such as PayPal generally offer better customer protection than traditional banks that may spend months considering your chargeback request. Ease of Use Most people agree that opening a digital app or a website live chat has become substantially more convenient than driving to your bank office during its working hours on a rainy day. However, this obvious factor is trickier than it looks. On the one hand, small mobile payments are easier to perform via the online systems created by . Moreover, you only need your phone to use them and they do not prohibit transactions if you forgot your passport or your driving license at home earlier this morning. modern fintech companies On the other hand, traditional thinking still suggests that brick-and-mortar storefronts may be more suitable for making ‘more serious’ transactions. Complex life choices such as opening a long-term deposit or making a mortgage payment of several thousand dollars to your real estate developer are usually associated with the need for physical contact and confirmation from the bank. Modern financial institutions are well aware of these preconceptions, which explains the transformation of their brick-and-mortar storefront facilities into open-space zones with coffee shops, coworking spaces aimed at small businesses, and regularly organized entrepreneurial fairs. The interesting part of the competition between modern services and traditional banks is its almost Hegelian dialectic. The new competitors highlight the disadvantages of their predecessors that criticize their own flaws and develop synthetic solutions combining the strong points of physical and online-based banking. At the moment, the death of traditional services may not be in sight since most people prefer to experiment with new technologies as a ‘second card’ for convenient mobile payments and international money transfers rather than a ‘core’ all-purpose solution. However, the advancement of fintech start-ups and their acquisition of specialized bank licenses will inevitably allow them to offer a wider range of offerings including deposits and consumer credits. This extra step may give them the leverage to fully disrupt the financial industry and bring an end to physical banking services.

Mobile Payments Systems: How Close Is the Death of Physical Banking?  

Python for Data Science: How to Scrape Website Data via the Internet's Top 300 APIs

Real-Life Software Security Vulnerabilities And What You Can Do To Stay Safe

Fintech represents the collision of two worlds — Financial services and technology, and with this union comes, both disruption and synergies. Fintech came of age in the aftermath of the 2008 financial crisis. New regulations and changing consumer demands began to emerge as the world tried to pick up the pieces of the “great recession”. 2008–18 constituted the formative decade for FinTech ‘Wave-1’, which irreversibly set the foundation for Wave-2 (2019 >onwards). . More innovation will happen in the next 10 years than the previous 100 years Asia is the epicenter of all fintech innovation, and within Asia, Singapore, and India, in particular, have taken big and bold moves towards the development of its FinTech landscape. There are three key takeaways from FinTech Wave-1 and what it means for India and Southeast Asia. China is the real fintech story, and that success story is divided between WeChat and Alipay. China has shown the world what is , and the world can’t go back. 1. possible There are also some hiccups in this journey, during 2018, the in China’s $192 B peer-to-peer (P2P) lending industry accelerated at a rapid clip. In many ways, this is a step in the right direction towards industry standardization/clean-up. shakeout regulatory crackdown Chinese fintech ecosystems have scaled and innovated faster and are structurally different from their counterparts in the US and Europe. Outside China, the most successful fin-techs are typically attackers that have focused on one vertical, such as payments, lending, or wealth management, deepening their core offering and then expanding geographically. The payment-wallets in Asia (*ex-china) continue to face ‘the moment of truth. The opportunity is HUGE. In India & Indonesia, 90%+ microtransactions are still ‘CASH’ based. is an extraordinary success in India. 2. The challenge remains. UPI ASEAN countries are a very and heterogeneous ecosystem. Situational awareness is critical to “win the game.” unique Lending is/was a ‘hot favorite’ for India and SE-Asia. The opportunity is MASSIVE, but some apparent mistakes are being made. The size/scale of alt-lenders is minuscule (%TAM) right now. 3. Startups trying to copy the China model will be disappointed. The marketplace/aggregators in the lending business face an uphill task. Debt Collections will get a big focus in the coming months. Alt-lenders should “read the tea leaves” and understand some unique factors, For e.g. the in India. [ ] banking crisis 1 A CLOSER LOOK AT THE SIX SECTORS IN WAVE-1 Fintechs have seized the initiative — defining the direction, shape, and pace of innovation across almost every subsector of financial services — and have succeeded as both stand‐alone businesses and crucial parts of financial value chains. They have reshaped customer expectations, setting new and higher bars for user experience. Let’s take a closer look: 1) Alt-lending The transactional and commodity nature of lending is making it hard, therefore, the investment community re-rated some startups from technology companies to lending companies. Moving forward, only the companies that can build profitable and scalable business-ecosystem models, and can withstand the test of a will lead the new wave. credit-cycle 2) Payments The original disruptors have gotten to scale and their playbook is changing. Rapid e-commerce growth, the digitization of payments, enabling regulations, are causing rapid growth of payment companies in Asia. that has seen Asia-Pacific accounting for nearly more than half of global payments revenue growth in the world at more than $900 billion. A growth Also, the market is in a consolidation phase, signaled by Fiserv Inc.’s planned $22 billion of First Data Corp and Fidelity National’s $43 billion of WorldPay Inc. purchase acquisition 3) Insurance Insurance startups are really at a pivot right now. Fast growth is leading to full-stack solutions. Historically, insurance startups were simply brokers or managing general agents. There’s a compelling case that insurance-tech startups need to become carriers. However, the ROE for carriers tends to be low(~9%). Insurance-tech players will need to figure this out. 4) P2P Lending Many peer-to-peer (P2P) lending companies — among the earliest to list in the US — saw valuations drop drastically in the public market. A number of Chinese lending fintechs, listed on the NYSE and Nasdaq in 2017, are trading much lower than their IPO prices, driven by . reports of bad loans and stringent regulations in China Accountability and better governance are critical for P2P lending to potential. truly hit its Understated risks, maturity mismatches, and illegal practices have to be addressed to restore faith and prove the viability of the business. 5) Wealth Tech One of the more interesting trends right now is that all the Wealth and investment companies that have achieved scale are adding a checking account and trying to become banks. Not necessarily licensed banks, but rather, a consumer’s primary financial partner. Chinese wealth-tech companies have proven that the — is winning operating model “a platform for your whole financial life”. Asia-Pacific is the world’s largest wealth management market, with >US$61 trillion in assets — bigger than the US or Europe — and growing at 3x the rate of the rest of the world. However, for markets like India and Indonesia, The key challenge (opportunity) is to transition existing users- “from part-time savers to longer-term investors.” 6) Decentralisation We are still in the very early days. In 2017, blockchain tech was a revolution In 2018, it was a disappointment. In 2019, it is becoming mundane. But with a greater focus on the “fairness” of Bitcoin and other Cryptocurrencies, it’s inevitable that we will see new distribution-focused . The previous two years were about the infrastructure needed to build these products, the next two will be about and attracting users. experiments scaling “Find a market that thrives on its lack of transparency and make it transparent.” NEAR-TERM: 2019–2020 The global fintech ecosystem will continue to mature at an accelerated pace. With big developments ranging from Fintech enabled marketplaces, increasing regulatory clarity, and maturation of AI and blockchain phase, Wave-2 promises to be big for fintech. Challenger banks will continue to grow their service offerings and expand across international borders. Supportive governments and regulators will become the foundation and bridge that enables a collaborative model between fintechs and banks. Collaboration between fintechs and banks in Asia is expected to continue to grow, particularly in areas like KYC, AML, and digital identity management — including facial recognition and voice recognition. Companies that work in isolation will lose relevance and fade away. A shortage of digital and tech talent will be the biggest trigger to facilitate this joining. Traditional banks and corporates will increasingly expand into digital banking, introducing nimble, standalone digital banks that operate independently and do not rely on their existing legacy systems. Collaboration is key to the next wave of fintech. As the fintech ecosystem matures, it’ll become increasingly clear that the best path forward for the industry lies in collaboration among all stakeholders. WAVE-2: NEW HORIZONS- WHAT’S NEXT? (2019- ) In Wave-2, the financial services sector will look beyond the current open banking ‘phase’ and towards a future of and , where traditional banking model is turned on its head and requires a dramatic rethink, emphasizing: fintech enabled marketplaces complete financial automation 1) over Products; Experience 2) over Assets; Data 3) over the build or buy; Partnering 4) over ownership. Shared access FinTechs are now increasingly global, and threatening traditional banks by ushering in product-stack changes- from ‘ , from . Incumbent Banks will recognize the value of the financial-cloud and speed up their digital transformation efforts to meet customer expectations derived from un-bundling to re-bundling’ ‘mono-line to multi-line’ fintechs with new operating and business models. In the medium term, (i.e. manufacture white-label versions of specific products and services) will gain traction. Distributed Ledger, API banking, and AI (Artificial Intelligence) will for both banks and financial services providers — — . However, consumer-ready AI remains much more limited. We will witness the emergence of “ ”; They will dominate a segment by offering a small number of world-class products that are hyper-focused on the segment’s needs. transactional banking become critical building blocks triggering ‘ the age of Invisible Banking’ and unleash a new paradigm where fintechs are the infrastructure providers vertical banks The onset of makes it possible to synergize financial services, where the line between deposits and lending will be blurred, and will be a reality. Collaborative AI Cash-flow-as-a-service In the next few years, some large will scale. Automation will increase and data security will become paramount. Big tech companies will continue to slowly move into finance, and some large Fintech firms will be acquired. fintech enabled marketplaces- curated with thousands of apps and APIs- The “move fast and break things” approach that disrupted the ad-tech industry is unlikely to work in financial services. , and a high level of regional variation in fintech disruption shall continue. More challengers and incumbents will partner . It is customers who are driving the disruption. New Fintech startups will enter markets not by stealing customers from incumbents, but by desidesign solusoluti around a select few customer activities. The focus will shift back to sound business and operating model innovation. As market landscapes get increasingly complex, choosing the right abstraction layers the company sits at becomes more important. Disruption starts with unhappy customers, not technology. In Wave-2, Human+Technology is the underlying theme Good execution and solid business models will trump exotic technology. Extraordinary transformations are happening in the finance world. We’ve only scratched the surface of this revolution. FinTech in ASEAN is only 1% done. It’s a very long game, but ultimately worth it. The coming “second wave” will be the one that drives lasting change. FinTech Wave-2 isn’t Digital. It’s Hybrid. and currently building a “ for India and South-East Asia. Gaurav Sharma is a FinTech entrepreneur, product and business builder with operating experience across Asia in Online-Credit, Payments, Internet, Consumer Banking , Bank of the Future” Other posts by Gaurav: Autonomous Finance Credit is older than Money (and Fintech) “Blood and Sand”: The Moment of -Truth for Mobile Wallets in Asia ChatB ots, API, Voice, Zero UI, and the future of Mobile Apps. Artificial Intelligence (AI) and FinTech — Part 1 Wal-Mart Moment for the banks Of Suits, Hoodies, and Ripped Jeans- Transcending the “Expectation Chasm” in Banking

"FinTech Wave-2 isn't Digital, It’s Hybrid." Lessons from Wave-1 and What’s Next?

Brian Rankin’s background is not unlike others. Successful business man moves into blockchain and leaves to explore the traditional business world yet again. Unlike his peers, Brian saw something interesting during a time when most retail investors are exiting. Brian saw opportunity and massive growth coming. Inspired and motivated to re-enter the blockchain space, Brian found an unlikely suitor. A project that seemingly is unknown to many, yet poised to disrupt the payment industry. And with Brian’ s experience, this is exactly what he contends will happen. PLEASE TELL US ABOUT YOUR BACKGROUND AND A LITTLE BIT ABOUT YOUR EXPERIENCE AT RIPPLE? I’ve been working in the Fintech world since 2008, back when mobile banking was new to the world. At ClairMail (acquired by Monitise, then by Fiserv) I managed mobile banking deployments into 50+ banks and credit unions. At Ripple I led the team that deployed RCL (Ripple Consensus Ledger) and cross-border payments solutions into international banks throughout Europe and APAC. In both companies I was privileged to lead teams of absolutely outstanding engineers and managers, truly some of the best people I’ve ever worked with [ teams, hats off to you! ] And I’m a leadership coach. I believe that everybody is naturally creative, resourceful and whole (unless they prove otherwise) and the best part of my day is when I’m coaching & mentoring my team. WHAT MADE YOU DECIDE TO JOIN MODERN FINANCE CHAIN AFTER LEAVING THE BLOCKCHAIN SPACE? Quite simply I’ve a big believer in the potential of the blockchain and digital currencies. And the big vision of Modern Finance Chain: to expand cryptocurrency utility to the point of ubiquity. With Modern Finance Chain’s multi-blockchain solution based on flexible and powerful smart contacts, I find it personally compelling because it hearkens back to the root of what digital currencies are all about: truly decentralized, instantaneous, transparent, that’s in the best interest of both merchants and consumers. There are so many ICOs out there that are based purely on fluff and “make money fast” — in fact, if you want to see the U.S. Securities and Exchange Commission’s take on ICOs then google HoweyCoins, which is the complete opposite of Modern Finance Chain. ELEVATOR PITCH. HOW WOULD YOU DESCRIBE WHAT MODERN FINANCE CHAIN IS AND WHAT IT’S TRYING TO DO IN A FEW SENTENCES? is a smart contract platform providing the ability for multiple digital currencies to be transacted across multiple blockchains — which is huge and very compelling because MFChain can embrace almost any use case that will enhance consumer and merchant’s experience. With multi-blockchain integration, it’s truly a decentralized network with no single dominant coin. And both merchants and consumers are rewarded for using the platform. Modern Finance Chain CAN YOU EXPLAIN YOUR EXACT ROLE WITH MODERN FINANCE CHAIN? I’m advising Modern Finance Chain on enterprise integrations. Many small technology startups, especially those that are consumer-facing, find it challenging to integrate with financial institutions and payments gateways. Banks — financial institutions in general — are large enterprises with a serious responsibility: they are custodians of financial asset used by millions of people (checking, savings, investments). This places huge regulatory, legal, compliance, and infoSec burdens on everything they do, highlighting the absolutely critical importance of quality product delivered to exacting specifications. I’m here to help MFChain navigate those waters — they can take advantage of my scars and deliver enterprise quality right out of the gate. REGULATIONS AND CRYPTOCURRENCY IS A HOT TOPIC. WHAT DO YOU THINK MODERN FINANCE CHAIN NEEDS TO DO TO ENSURE LONG TERM SUCCESS DURING THESE UNCERTAIN TIMES? So beyond ICOs and talk of digital currencies as securities: the big driver of regulation is that the institutional investors want in. Digital currency investments have a total AUM of about 5% of traditional venture capital. That’s a lot of room for investing in coin. What’s stopping things is lack of institutional-grade investor protection, which won’t change until the regulatory landscape around digital currencies matures. And Modern Finance Chain’s part? Keep abreast of what’s going on around regulations, but don’t let uncertainty and rumors drive the ship — stay the course and keep executing against the vision. At the same time work with the regulators, not against the regulators, as what they really want is to do what’s best for the security and well-being of the people and institutions who will use digital currencies (yes I’m giving regulators the benefit of the doubt). Finally, listen to the MFChain team members, often they already have the answer to — or at least an informed opinion about — the problem of the day. WHAT DO YOU THINK MAKES MODERN FINANCE CHAIN UNIQUE VERSUS ITS COMPETITORS? Several things. Let’s break it down. MFChain has their own Mainnet which enables multi-blockchain integration and a multi-currency digital payments system. And (I like this) it uses the BFT/POS consensus model, which scales horizontally very well. Merchants have choices: accept multiple digital currencies; convert some or all to fiat currencies as desired; control the surcharges on their systems so they can do what’s right for their individual businesses. Consumers can use whatever wallet they have today to transact on Mainnet — no need to go through an exchange. Privacy is king — and consumers control their own privacy settings. And consumers are rewarded — 1% of every purchase using MFX tokens. About those rewards — what I didn’t mention is that 16% of the entire token allocation will be set aside as a rewards pool. And the rewards merchants receive can be passed on — in part or whole — to their customers as they see fit. It’s an awesome innovation platform and incubator. The Mainnet gives the ability for other ICO projects to accept other digital currencies when generating tokens — today most ICOs accept only BTC and ETH. With MFChain we also accept NEO, LTC, XRP, etc — just about any of Altcoin on any blockchain. PLEASE EXPLAIN WHAT THE MF2X PROTOCOL IS? IS THIS FULLY COMPLIANT OR ARE LICENCES AND REGISTRATION STILL REQUIRED? The MF2X protocol enables direct crypto-to-fiat and crypto-to-crypto swaps without the need for dealing with a centralized crypto exchange. This allows any digital currency to participate & transact on the MFChain mainnnet, and opens up the MfChain products and services to millions of users. It’s exciting! Still lots of work to do, however we’re already collaborating with Credits to accept their tokens on our Mainnt. And yes, with our AML/KYC capabilities we will be fully compliant and will register as required within any applicable jurisdiction. Our legal team is managing those important details. PLEASE EXPLAIN THE MFX REWARDS POOL. HOW DOES THAT WORK FOR BOTH CONSUMERS AND MERCHANTS? The MFX reward pool comprises 16% of the entire initial MFX token allocation; additional allocations to the pool will happen as new blockchain partnerships join the Mainnet. The pool is used to incent both consumers and merchants to transact: consumers are rewarded for every transaction (a percentage of their purchase similar to a cash-back credit card program); for merchants the pool covers fees typically bundled by traditional payments systems: chargebacks, interchanges, assessments, payment gateways — these all go away with the MFX Rewards Pool. I like that it’s totally transparent to both the consumers and the merchants, and the merchants can choose to pass their savings onto their customers. It’s an important component of an entire merchant/consumer ecosystem, which is what MFChain is all about. ARE THERE ANY PARTNERSHIPS FORMED OR ANY POTENTIAL PARTNERSHIPS COMING UP? Absolutely! We’re partnered with Ingot Coin and Loopring, which provides us transparent access to their liquidity pools and cryptocurrency partners, and with DDEX as our first exchange listing partner. We’ve also joined the Komorebi Alliance, which I find especially interesting as it’a cross-blockchain group of partners that hedges risk by providing redundancy in the event there’s a performance issue with a partner’s platform, and, converges the industry-specific functions of each partner’s utility token — Token Augmenting Partnerships, to quote Hirander Misra. And we’re announcing two new partners: Zagg, a leader in Gift Cards, Benefits, Rewards and Loyalty industry, who will use the MF2X protocol for payments through MFChain’s payments gateway and will integrate their awards program with the MFX rewards pool. We’ve just partnered with Credits, a Singapore-based blockchain platform for developing dApps, who will use the M2FX protocol to enable the Credits token in the MFChain mainnet. What’s fascinating to see is that we are reaching out to potential partners — not just any blockchain company but the best and the brightest — and they get the vision, they see the value. They understand that by moving beyond the power of one to the power of team, all of us can be immeasurably more successful & impactful. And at the end of the day that’s what it’s all about: having positive impact in the world.

Meet Brian Rankin, Former VP of Ripple

Top 10 Reputable Blockchain Development Companies

Enterprises are discovering new avenues for growth and opportunity because of digital transformation. More industries are adopting digital workplaces and hybrid models to create a more flexible and self-sufficient workforce. Especially during the COVID-19 pandemic, digital workplaces have transformed the way people collaborate and experience work. More companies are heavily reliant on technology for remote collaboration and operational efficiency. According to a study by Deloitte, implementing digital technologies augments the progress towards company goals by . In a rapidly evolving technology-driven ecosystem, digital initiatives are also responsible for creating more sustainable workplaces in and beyond. 22% 2021 However, the debate is still going on about whether remote work is better than on-site work, or whether a hybrid workplace model is the best fit for modern enterprises. What does the future of work look like? In a survey conducted by Accenture, it was identified that of high-revenue companies embrace the concept of hybrid workforce models. This states that most enterprises are keen on streamlining processes using technology that enables more efficient on-site work as well as remote work. 63% Ultimately digital transformation is driving industries to adopt new ways of working and upskilling their current workforce to meet future demands. Yet many businesses still rely on on-site workforces which is gradually changing with the introduction of new equipment, artificial intelligence, and machine learning. So, what is the difference between on-site work, remote work, and hybrid work? What are the pros and cons? Which workplace solution will determine the future of work? To answer these questions, let us understand the pros and cons of each workplace ecosystem. 1. On-site work Working at a location, a worksite or an office can provide a unified experience for the entire workforce. This can foster a physical sense of awareness, discipline, and unity. Most of us are familiar with this type of work as the set standard. While some people exclusively prefer on-site work, there are others who find remote work more advantageous. Each type of work has its own pros and cons. Pros of on-site work: Less distractions from family affairs More communication and interaction with colleagues Cohesive organizational culture which fosters a sense of purpose Access to company assets, facilities, and equipment Common, structured routine that enables discipline and productivity Cons of on-site work: Stressful, costly and lengthy commute times Increased overheads for the organization Higher energy costs for the organization and individual Frequent distractions from colleagues and coworkers An exclusive business ecosystem that some may find unfavorable While on-site work is slowly phasing out in various industries, there is still a large proportion of workers who are required to be on-site to perform certain tasks and functions of the business. Digital disruption will benefit the companies investing in developing technologies to automate strenuous processes. 2. Remote work Digital innovation has introduced digital workplaces, which highlights a lot of drawbacks of on-site workplace models. With the rise of technology, it became easier for people to work and collaborate remotely. Research by Owl Labs revealed that of the companies globally are already remote. Another study by CoSo Cloud recorded that of remote workers report being more productive when they work from home. 16% 100% 77% A parallel survey by Intuition also revealed that of employers surveyed will permit employees to work remotely post-pandemic. 47% Remote work is gaining prominence in numerous industries across various business verticals. Pros of remote work: Higher levels of productivity Freedom to work anywhere and at any time Save time and costs on commute More family time and personal time Less distractions from coworkers Virtual collaboration Cons of remote work: Social isolation and related problems Lack of interaction with the outside world Often results in communication gaps between teams Remote work trends picked up during the global pandemic of COVID-19, where many companies introduced remote work practices and policies. 3. Hybrid work Notably, key players in the IT and FinServ industries are determined to continue remote work post the pandemic. However, operations reliant on on-site workers will have to find a new and inventive workplace solution. That’s why hybrid workplaces can revolutionize the future of work. In a survey by Stanford, of workers prefer to spend some time at office and some time at home during work. preferred working from home permanently, while only said they want to work on-site full-time. 55% 25% 20% Hybrid work models vary from company to company. In many cases, employees are offered flexible work hours and remote work opportunities while a percentage of the workforce works on-site. This system is alternated depending on the business requirements. Pros of hybrid working: Employees have the freedom of remote work During on-site workdays, employees can get to know their coworkers better Companies can curb overhead costs by deploying hybrid workplace solutions Cons of hybrid working: Division between on-site and remote workers in the same organization Collaboration between two teams may be negatively impacted Managers and leaders may prefer teams they work with often, rather than a cohesive work culture The hybrid work model includes the many advantages of both on-site and remote workplace solutions. Yet every enterprise has its own goals. A hybrid model works best when the solution is designed for business-specific outcomes. Are Hybrid Workplaces the Future of Work? To materialize the hype around what the modern workplace will be like, experts at Technovert conducted an independent study on LinkedIn. The poll asked respondents to pick their preferred type of work. of voters opted for Hybrid work while chose Remote work and preferred Working from office. 47% 36% 17% LinkedIn Poll results Realizing that hybrid workplaces are a top preference by most voters, reflects changing employee expectations and their recent experiences. Majority of the voters who prefer a hybrid workplace understand the benefits of on-site work and vouch for the flexibility of remote work. Combining the two workplaces is the logical solution. The impact of hybrid workplaces will speed up innovation at every level of enterprise in the coming years. This will change the way we work and thus our perception of work as a whole. Digital transformation is reinventing the way we work Digital transformation has made way for technology that enables seamless workplace experiences that are flexible, adaptable and highly scalable. According to Gartner, of senior executives believe that digitalization is an organizational priority. Digital initiatives will determine the progressive nature of technology adoption in every office across the world. 87% For businesses to make better decisions, it is important to understand how various types of workplace solutions can impact their operational efficiency, and organization’s culture. Digital workplace solutions that are tailored to the unique demands of enterprises can map the growth and opportunity for companies of all sizes. The future of work is tech-driven workflow and flexible workplace policies, widely sought after by conglomerates and SMBs alike.

The Future of Work: On-site Work vs Remote Work vs Hybrid Work

Mobile phones have come a long way from being devices that only allowed you to communicate via voice or text. The slow progression to multimedia communication was brought about by better telecommunication services and the gradual advancements from 2G networks to 3G and then 4G. Today, are the customers first choice and it is due to their 3G and 4G network capabilities that we enjoy the benefits that we do. However, with 5G on the horizon, smartphones will undergo yet another set of changes, and these will greatly enhance and change the way we interact with smartphones. Android smartphones under Rs. 15000 To understand this better, take a look at a few ways in which 5G phones can affect change in the world around you. Take advantage of the 5G network’s connectivity and speed capabilities 5G mobile phones can tap into 5G networks that have very noticeable differences. 5G networks are faster as they support data rates up to 10Gbps, are capable of low latency, under 1ms, and offer enhanced coverage thanks to the small cell concept. So, with a 5G-compatible phone, you can get access to media of the highest quality within seconds, enjoy wireless transmission with minimal delay and enjoy seamless integration with cloud technology. Grant access to more immersive and interactive content When it comes to newer technology, like Augmented Reality or Virtual Reality, the main obstacle to accessing it is the fact that it requires you to be on a network that is capable of handling large streams of data quickly. This is why most of these systems are typically run on broadband networks because they’re much faster and have lower latencies, all of which are limitations you’d face on a wireless 4G network. However, with 5G phones, AR and VR can be migrated seamlessly and you can enjoy this content whenever you’re connected to a 5G network. Both these new formats are highly immersive and deliver a truly unique experience, and 5G smartphones take advantage of the faster spectrum to bring the formats to you. Play a fundamental role in the Internet of Things (IoT) The Internet of Things concept relies on the interconnectivity of appliances and smart devices with the internet. However, for these applications to run as intended with real-time analysis and control, there needs to exist a network that can collect and process huge amounts of data quickly. 5G networks can do just that and 5G phones can take advantage of this to facilitate ecosystems like a smart home. Here, all your devices are linked to your smartphone and with the help of an AI-assistant, you can set commands and control them remotely. The practical applications of 5G mobiles are many, ranging from VR and smart homes to remote surgeries and virtual healthcare, and new mobile phones will definitely play a vital role in the way you interact with technology and the world around you. 5G phones are simply the next step in telecommunication and the sooner you get your hands on compatible devices, the faster you can enjoy premium features. However, considering the fact that these devices will be the most advanced in the market, they won’t come cheap. You can expect the latest 5G Samsung, Apple, Xiaomi, Oppo or to bear a hefty premium and so, it is best to learn how you can shop for a device of your choice affordably. Thankfully, with the Bajaj Finserv EMI Network, you can get a 5G mobile on EMI without a credit card by simply opting for No Cost EMIs. Vivo smartphone Here, the cost of the device is split over a flexible tenor of up to 24 months to match your repayment capabilities. What’s more, after paying the first installment, you can foreclose the loan entirely at no additional costs. To shop hassle-free, simply use your EMI Network Card or go for in-store financing at a partner store. Similarly, for a customized EMI plan, check your pre-approved offer online by sharing basic details and get instant approval.

5G phones: The next-gen technology that can change the world

Based on your previous coverage of similar topics, we thought you may be interested in this recently discovered voice activation device hack, and a new technique we call Voice-Command SQL Injection. Here are the highlights: 1) Hacker uses a voice-command SQL injection methodology to extract unauthorized data from the application database- including the admin account 2) This is done on an Alexa device but could be performed on any voice-activated digital assistant 3) This could mean that users of virtual assistant skills/applications could be exposed to new attacks The outcome: The tried and true SQL injection attack has is now voice-enabled Write-up: Picture this, your bank account was hacked. While not new news, what if it was hacked using simply voice and Alexa? Pretty scary, right? We all know that not all web applications are created equal, as each one has different levels of security measures in place to protect the information or data, as well as application access. Unfortunately, the average user of the application has very little knowledge as to the security of each application, whether it be their financial, retail, utility, fitness applications, etc. Luckily, there are regulatory requirements surrounding security measures for applications in certain industries like FinServe (FINRA), Healthcare (HIPAA), and Retail (PCI-DSS), but what about other industries not impacted by regulatory compliance? Or even within those, how have security protocols evolved to protect the applications and skills when applied to new channels, like Alexa, Google Assist, Cortana, Siri, etc. In fact, now it is easier than ever for hackers to perform such hacks into a variety of applications, just using their voice. Leveraging voice-command SQL injection techniques, hackers can give simple commands utilizing voice text translations to gain access to applications and breach sensitive account information. To illustrate the vulnerability and create greater awareness, Head of Security and Ethical Hacker, Tal Melamed illustrates how a can be executed through a verbal command in order to gain unauthorized access to sensitive account data. This demo will show how, in this instance, Alexa, can be exploited in an unprotected application or skill, by translating words and numbers. Protego’s simple SQL Injection Tal will illustrate how easy it is to gain unauthorized access through Alexa to unsecured applications, by verbally providing simple account numbers and text. Since Tal is an ethical hacker, he will be using an application and SQL database he built himself, but in reality, it could be any application that requires an account number or text as a unique identifier. The the following: demo highlights 1) Tal will try to access an admin account that he is unauthorized to access according to name identification and account ID. 2) Alexa will at first deny his request 3) Tal will then bypass this denial by calling a random number with syntax that would trigger the SQL. 4) When asked for an account ID he simply says a random number and adds “or/true” which grants him access to any line in the database 5) Alexa then provides Tal with the balance information of the unauthorized Admin account It is important to note that this demo is , using Alexa. not highlighting a vulnerability with Alexa rather, the actual applications In fact, any application that was potentially susceptible to an attack by text input (think a hacker and a keyboard) would be susceptible to a voice-based attack as depicted here. All that is needed are these three conditions: 1) the virtual assistant function/skill is using SQL as a database 2) the function/skill is vulnerable to SQL injection 3) one of the (vulnerable) SQL queries includes an integer value as part of the query Of course, there are other similar attacks, not based on SQL (e.g. command injection) that might also be relevant as these rapidly deployed skills/applications don't necessarily lend themselves to putting a WAF in front of them. In environments where there is no true perimeter around the applications themselves, security teams need to work with developers on building security around the code itself. It is the only way to ensure applications are protected from all fronts against malicious attacks, including virtual assistants. If additional application security measures were in place, whether hosted in serverless or other cloud-infrastructure, Alexa wouldn’t be able to access any secure data, even when attempting an SQL injection such as this. It is a new game of cat and mouse with hackers as there are hundreds of skills being developed by organizations each day, and attackers have now found a new way to try and access these applications. Now we have to make sure we are prepared.

How to Hack Your Alexa using a Voice Command-SQL Injection

Hello, in today’s article, I will show you how you can build your own OAuth2 server just like google, facebook, github etc. This will be very helpful if you want to build a production ready public or private API. So let’s get started. What is OAuth2? Open Authorization Version 2.0 is known as OAuth2. It’s one kind of protocol or framework to secure RESTful Web Services. OAuth2 is very powerful. Now a days, majority of the REST API are protected with OAuth2 due to it’s rock solid security. OAuth2 has two parts 01. Client 02. Server OAuth2 Client If you’re familiar with this screen, you know what I’m talking about. Anyway, Let me explain the story behind the image: You’re building a user facing application that works with user’s github repositories. For example: CI tools like TravisCI, CircleCI, Drone etc. But user’s github account is secured and no one can access it if the owner doesn’t want. So how do these CI tools access user’s github account and repositories? Easy. Your application will ask the user “In order to work with us, you need to give read access to your github repos. Do you agree?” Then the user will say “Yes I do. And do whatever needs to do”. Then your application will contact github’s authority to grant access to that particular user’s github account. Github will check if it’s true and ask that user to authorize. Then github will issue an ephemeral token to the client. Now, when your application needs to access it after the authentication and authorization, it needs to send the access token with the request so that github will think: “Oh, the access token looks familiar, may be we have given that to you. Ok, you can access” That’s the long story. Days have changed, now you don’t need to go to github authority physically each time (we never had to do that). Everything can be done automatically. But how? This is a UML sequence diagram of what I have talked couple of minutes ago. Just graphical representation. From the above picture, we found some important things. OAuth2 has 4 roles: 01. User — The end user who will use your application 02. Client — The application you’re building that will use github account and the user will use 03. Auth Server — The server that deals with the main OAuth things 04. Resource Server — The server that has the protected resources. For example github Client sends OAuth2 request to the auth server on behalf of the user. Building an OAuth2 client is neither easy nor hard. Sounds funny, right? We’ll do that in the next part. But in this part, we’ll go to the other side of the world. We’ll build our own OAuth2 Server. Which is not easy but juicy. Ready? Let’s go OAuth2 Server You may ask me “Wait a minute Cyan, why building an OAuth2 server?” Did you forget man? I have said this earlier. Ok, let me tell you again. Imagine, you’re building a very useful application that gives accurate weather information (there are plenty of this kind of api out there). Now you want to make it open so that public can use it or you want to make money with it. Whatever the case is, you need to protect your resources from un-authorized access or malicious attacks. In order to do that you need to secure your API resources. Here comes the OAuth2 thingy. Bingo! From the picture above, we can see that we need place an Auth Server in front of our REST API Resource Server. That’s what we’re talking about. The Auth Server will be built using OAuth2 specification. Then we’ll become the github of the first picture, hahahaha just kidding. The primary goal of the OAuth2 server is to provide access token to the client. That’s why OAuth2 Server is also known as OAuth2 Provider, because they provide token. Enough talking. There are four types of OAuth2 server based of the Grant Flow type: 01. Authorization Code Grant 02. Implicit Grant 03. Client Credentials Grant 04. Password Grant If you want to know more about OAuth2, check out awesome article. this For this article, we’ll use . So let’s dig in Client Credentials Grant Type Client Credentials Grant Flow Based Server When implementing Client Credentials Grant Flow based OAuth2 Server, we need to know couple of things. In this grant type, there’s no user interaction (i.e. signup, sign-in). Two things needed, and they are the and the . With this two things, we can obtain . Client is the 3rd party application. When you need to access resource server without the user or only by the client application, then this grant type is simple and best suited. client_id client_secret access_token Here’s a UML Sequence Diagram of it. Coding To build this, we need to rely on an awesome Go package First of all, let’s build a simple API server as Resource Server package main ( )

func main() {
	http.HandleFunc( , func(w http.ResponseWriter, r *http.Request) {
		w.Write([]byte( ))
	})

	log.Fatal(http.ListenAndServe( , nil)) import "log" "net/http" "/protected" "Hello, I'm protected" ":9096" Run the server and send a Get Request to http://localhost:9096/protected You’ll get response. What kind of protected server it is? Though the endpoint name is protected, but anyone can access it. So we need to protect it with OAuth2. Now we’ll write our authorization server Routes 01. for issuing client credentials (client_id and client_secret) /credentials 03. to issue token with client credentials /token We need to implement these two routes. Here’s the preliminary setup package main ( )

func main() { := manage.NewDefaultManager()
   manager.SetAuthorizeCodeTokenCfg(manage.DefaultAuthorizeCodeTokenCfg)

   manager.MustTokenStorage(store.NewMemoryTokenStore())

   clientStore := store.NewClientStore()
   manager.MapClientStorage(clientStore)

   srv := server.NewDefaultServer(manager)
   srv.SetAllowGetAccessRequest( )
   srv.SetClientInfoHandler(server.ClientFormHandler)
   manager.SetRefreshTokenCfg(manage.DefaultRefreshTokenCfg)

   srv.SetInternalErrorHandler(func(err error) (re *errors.Response) {
      log.Println( , err.Error()) })

   srv.SetResponseErrorHandler(func(re *errors.Response) {
      log.Println( , re.Error.Error())
   })
	
   http.HandleFunc( , func(w http.ResponseWriter, r *http.Request) {
		w.Write([]byte( ))
   })

   log.Fatal(http.ListenAndServe( , nil))
} import "encoding/json" "fmt" "github.com/google/uuid" "gopkg.in/oauth2.v3/models" "log" "net/http" "time" "gopkg.in/oauth2.v3/errors" "gopkg.in/oauth2.v3/manage" "gopkg.in/oauth2.v3/server" "gopkg.in/oauth2.v3/store" manager true "Internal Error:" return "Response Error:" "/protected" "Hello, I'm protected" ":9096" Here we created one manager, client store and the auth server itself. Here’s the route /credentials http.HandleFunc( , func(w http.ResponseWriter, r *http.Request) { := uuid.New().String()[: ]
   clientSecret := uuid.New().String()[: ]
   err := clientStore.Set(clientId, &models.Client{ :     clientId, : clientSecret, : ,
   }) err != nil {
      fmt.Println(err.Error())
   }

   w.Header().Set( , )
   json.NewEncoder(w).Encode(map[string]string{ : clientId, : clientSecret})
}) "/credentials" clientId 8 8 ID Secret Domain "http://localhost:9094" if "Content-Type" "application/json" "CLIENT_ID" "CLIENT_SECRET" It creates two random string, one for client_id and another for client_secret. Then saves them to the client store. And return them as response. That’s it. We used in memory store, but we can store them in redis, mongodb, postgres etc. Here’s the route: /token http.HandleFunc( , func(w http.ResponseWriter, r *http.Request) {
   srv.HandleTokenRequest(w, r)
}) "/token" It’s very simple. It passes the request and response to the appropriate handler so that the server can decode all the necessary data from the request payload. So here’s our overall code: package main ( )

func main() { := manage.NewDefaultManager()
   manager.SetAuthorizeCodeTokenCfg(manage.DefaultAuthorizeCodeTokenCfg)

   manager.MustTokenStorage(store.NewMemoryTokenStore())

   clientStore := store.NewClientStore()
   manager.MapClientStorage(clientStore)

   srv := server.NewDefaultServer(manager)
   srv.SetAllowGetAccessRequest( )
   srv.SetClientInfoHandler(server.ClientFormHandler)
   manager.SetRefreshTokenCfg(manage.DefaultRefreshTokenCfg)

   srv.SetInternalErrorHandler(func(err error) (re *errors.Response) {
      log.Println( , err.Error()) })

   srv.SetResponseErrorHandler(func(re *errors.Response) {
      log.Println( , re.Error.Error())
   })

   http.HandleFunc( , func(w http.ResponseWriter, r *http.Request) {
      srv.HandleTokenRequest(w, r)
   })

   http.HandleFunc( , func(w http.ResponseWriter, r *http.Request) { := uuid.New().String()[: ]
      clientSecret := uuid.New().String()[: ]
      err := clientStore.Set(clientId, &models.Client{ :     clientId, : clientSecret, : ,
      }) err != nil {
         fmt.Println(err.Error())
      }

      w.Header().Set( , )
      json.NewEncoder(w).Encode(map[string]string{ : clientId, : clientSecret})
   })
   
   http.HandleFunc( , func(w http.ResponseWriter, r *http.Request) {
		w.Write([]byte( ))
   })
   log.Fatal(http.ListenAndServe( , nil))
} import "encoding/json" "fmt" "github.com/google/uuid" "gopkg.in/oauth2.v3/models" "log" "net/http" "time" "gopkg.in/oauth2.v3/errors" "gopkg.in/oauth2.v3/manage" "gopkg.in/oauth2.v3/server" "gopkg.in/oauth2.v3/store" manager true "Internal Error:" return "Response Error:" "/token" "/credentials" clientId 8 8 ID Secret Domain "http://localhost:9094" if "Content-Type" "application/json" "CLIENT_ID" "CLIENT_SECRET" "/protected" "Hello, I'm protected" ":9096" Run the code and go to route to register and get client_id and client_secret http://localhost:9096/credentials Now go to this URL http://localhost:9096/token?grant_type=client_credentials&client_id=YOUR_CLIENT_ID&client_secret=YOUR_CLIENT_SECRET&scope=all You”ll get the access_token with expiry time and some other information. Now we got our access_token. But our /protected route is still un-protected. We need to setup a way that will check if a valid token exists with each client request. If yes, then we give the client access. Otherwise not. We can do this with a middleware. Writing middleware in go is ao much fun if you know what you are doing. Here’s the middleware: func validateToken(f http.HandlerFunc, srv *server.Server) http.HandlerFunc { http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
      _, := srv.ValidationBearerToken(r) err != nil {
         http.Error(w, err.Error(), http.StatusBadRequest) }

      f.ServeHTTP(w, r)
   })
} return err if return This will check if a valid token is given with the request and take action based on that. Now we need to put this middleware in front of our /protected route using adapter/decorator pattern http.HandleFunc( , validateToken(func(w http.ResponseWriter, r *http.Request) {
   w.Write([]byte( ))
}, srv)) "/protected" "Hello, I'm protected" Now the whole code looks like this: package main ( )

func main() { := manage.NewDefaultManager()
   manager.SetAuthorizeCodeTokenCfg(manage.DefaultAuthorizeCodeTokenCfg) manager.MustTokenStorage(store.NewMemoryTokenStore()) clientStore := store.NewClientStore()
   
   manager.MapClientStorage(clientStore)

   srv := server.NewDefaultServer(manager)
   srv.SetAllowGetAccessRequest( )
   srv.SetClientInfoHandler(server.ClientFormHandler)
   manager.SetRefreshTokenCfg(manage.DefaultRefreshTokenCfg)

   srv.SetInternalErrorHandler(func(err error) (re *errors.Response) {
      log.Println( , err.Error()) })

   srv.SetResponseErrorHandler(func(re *errors.Response) {
      log.Println( , re.Error.Error())
   })

   http.HandleFunc( , func(w http.ResponseWriter, r *http.Request) {
      srv.HandleTokenRequest(w, r)
   })

   http.HandleFunc( , func(w http.ResponseWriter, r *http.Request) { := uuid.New().String()[: ]
      clientSecret := uuid.New().String()[: ]
      err := clientStore.Set(clientId, &models.Client{ :     clientId, : clientSecret, : ,
      }) err != nil {
         fmt.Println(err.Error())
      }

      w.Header().Set( , )
      json.NewEncoder(w).Encode(map[string]string{ : clientId, : clientSecret})
   })

   http.HandleFunc( , validateToken(func(w http.ResponseWriter, r *http.Request) {
      w.Write([]byte( ))
   }, srv))

   log.Fatal(http.ListenAndServe( , nil))
}

func validateToken(f http.HandlerFunc, srv *server.Server) http.HandlerFunc { http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
      _, := srv.ValidationBearerToken(r) err != nil {
         http.Error(w, err.Error(), http.StatusBadRequest) }

      f.ServeHTTP(w, r)
   })
} import "encoding/json" "fmt" "github.com/google/uuid" "gopkg.in/oauth2.v3/models" "log" "net/http" "time" "gopkg.in/oauth2.v3/errors" "gopkg.in/oauth2.v3/manage" "gopkg.in/oauth2.v3/server" "gopkg.in/oauth2.v3/store" manager // token memory store // client memory store true "Internal Error:" return "Response Error:" "/token" "/credentials" clientId 8 8 ID Secret Domain "http://localhost:9094" if "Content-Type" "application/json" "CLIENT_ID" "CLIENT_SECRET" "/protected" "Hello, I'm protected" ":9096" return err if return Now run the server and try to access endpoint without the as URL Query. Then try to give wrong . Either way, the auth server will stop you. /protected access_token access_token Now get the and again from the server and send request to the protected endpoint : credentials access_token http://localhost:9096/test?access_token=YOUR_ACCESS_TOKEN Bingo! You’ll get access to it. So we’ve learned how to setup our own OAuth2 Server using Go. In the next part, we’ll build our OAuth2 client in Go. And in the last part, we’ll build the with user login and authorization. Authorization Code Grant Type Based Server

Build your own OAuth2 Server in Go

Cree su propio servidor OAuth2 en Go

Lets talk about some old security here. Kerberos! This is a couple years old but sadly still works. Kerberos is the authentication system for windows and ad networks. There is an exploit that allows us to get back a poorly encrypted hash of valuable logins all directly from the domain controller, this is done once you have an authenticated user, so it isn’t the main way in but once you have a foothold you can pivot to a more useful account. Lets have a brief breakdown of how kerberos works, borrowed from https://adsecurity.org/?p=3458 User logs on with username & password. 1a. Password converted to NTLM hash, a timestamp is encrypted with the hash and sent to the KDC as an authenticator in the authentication ticket (TGT) request (AS-REQ).1b. The Domain Controller (KDC) checks user information (logon restrictions, group membership, etc) & creates Ticket-Granting Ticket (TGT). 2. The TGT is encrypted, signed, & delivered to the user (AS-REP). Only the Kerberos service (KRBTGT) in the domain can open and read TGT data. 3. The User presents the TGT to the DC when requesting a Ticket Granting Service (TGS) ticket (TGS-REQ). The DC opens the TGT & validates PAC checksum — If the DC can open the ticket & the checksum check out, TGT = valid. The data in the TGT is effectively copied to create the TGS ticket. 4. The TGS is encrypted using the target service accounts’ NTLM password hash and sent to the user (TGS-REP). 5.The user connects to the server hosting the service on the appropriate port & presents the TGS (AP-REQ). The service opens the TGS ticket using its NTLM password hash. 6. If mutual authentication is required by the client (think MS15–011: the Group Policy patch from February that added UNC hardening). Unless PAC validation is required (rare), the service accepts all data in the TGS ticket with no communication to the DC. Alright so lets just dive right in to the nitty gritty here. We are going to do this on a windows box with powershell and the active directory module.The return will look something like “MSSQLSvc/adsmsDB01.adsecurity.org:1433”, then “MSSQLSvc” is the SPN type. The SPN is really the important part of the initial scan because we will want to find specific types of SPNs. Such as:AGPMServer: Often has full control rights to all GPOs.MSSQL/MSSQLSvc: Admin rights to SQL server(s) which often has interesting data.FIMService: Often has admin rights to multiple AD forests.STS: VMWare SSO service which could provide backdoor VMWare access.To do the actual querying we can use the Get-ADUser cmdlet: get-aduser -filter {AdminCount -eq 1} -prop * | select name,created,passwordlastset,lastlogondate We can also use PowerView’s Get-NetUser cmdlet: Get-NetUser -AdminCount | Select name,whencreated,pwdlastset,lastlogon Once we have an SPN then lets get the querying for the vulnerable hash type $SPNName = ‘MSSQLSvc/adsmsDB01.adsecurity.org:1433’Add-Type -AssemblyNAme System.IdentityModelNew-Object System.IdentityModel.Tokens.KerberosRequestorSecurityToken -ArgumentList $SPNName We can then use “$ klist “in order to get the listing of the hash and from there we can use mimikatz in order to export. $ mimikatz $ kerberos::list /export Then we just drop that hash into hashcat with a word list and we are good to go.Sadly this vulnerability is over 4 years old, it is still out there. In order to mitigate it the recommendation is ensuring service account passwords are longer than 25 characters (and aren’t easily guessable). Also enabling logging and then dropping that log information into a SIEM where you can look for specific “4769 events” and and Ticket_Encryption_Type=0x17. Good luck! links:https://adsecurity.org/?p=2293 : “Cracking Kerberos TGS Tickets Using Kerberoast — Exploiting Kerberos to Compromise the Active Directory Domain”https://adsecurity.org/?p=3466 : “Sneaky Persistence Active Directory Trick #18: Dropping SPNs on Admin Accounts for Later Kerberoasting.”

Kerberoasting!

Photo by on Aziz Acharki Unsplash Table of Contents Part I: Getting started with the Fn project Part II: Fn Load Balancer (this post) If you’re looking to get up and running with the , check out the first post in this series. In this post I am going to talk about Fn load balancer — what is it, how to run it locally and how to deploy it to a Kubernetes cluster. Fn project The purpose of the is to intelligently route traffic to clusters of Fn servers. This is not a simple round robin routing as it has some logic that determines to which nodes to route the traffic based on the requests that are coming in. For example, if your function is “hot” on node2, the load balancer will ensure it gets routed to that node, instead of another node where the function is not loaded. That way you get much better performance. Fn load balancer Check the simple diagram below to see how load balancer falls into place with the Fn server(s) and the Fn database. Fn Load Balancer diagram Load balancer also gathers information about the entire cluster and exposes the list of nodes and their states, so you can use that information to scale out your cluster by adding more Fn servers or scale in — decrease the number of servers in your cluster. Running locally The quickest way to get multiple Fn servers up and running behind the load balancers and to try things out is to run it locally on your machine using Docker. The image you want to pull and run is called . At the time of writing this, the latest version/tag is . fnproject/fnlb 0.0.268 Let’s try running a couple of Fn servers and a load balancer. We will run both the Fn server(s) and the load balancer in containers — we will link the load balancer to the Fn server instance, so it can discover it. If you don’t want to manually copy/paste the commands in this section, you can get the script below — the script will automatically start N Fn server containers and a single Fn load balancer. : Make sure to run in the same folder you’re planning to run the above script in. The reason for that is, so Fn can create the database file for us. If you don’t do this, you’ll get errors starting the Fn server containers. Note fn start Start by running a couple of Fn server containers. We don’t need to expose any ports to the host, as we are going to be accessing the Fn server through the load balancer: docker run -it --rm --name fnserver1 -v $PWD/data/fn.db:/app/data/fn.db  -v /var/run/docker.sock:/var/run/docker.sock fnproject/fnserver:latest Similarly, run the second Fn server from a new terminal window. : Make sure you run the second server from the same folder as they need to share the same database docker run -it --rm --name fnserver2 -v $PWD/data/fn.db:/app/data/fn.db  -v /var/run/docker.sock:/var/run/docker.sock fnproject/fnserver:latest : if you don’t feel like opening multiple new terminal windows, you can add to each Docker command to run the containers in detached mode. I prefer seeing logs from all containers when trying things out. Note _-d_ Finally, let’s run the load balancer and link to the Fn servers we have running: docker run -it --rm --name fnlb --link fnserver1 --link fnserver2 -p 8080:8081 fnproject/fnlb:latest --nodes fnserver1:8080, fnserver2:8080 We are using to link the containers together — this makes the Fn server containers accessible from the Fn load balancer container using their names ( and ). We are also exposing port 8080 to the host and linking it to the port 8081 inside of the container (that’s the port LB is accessible from inside of the container). --link fnserver1 fnserver2 If all is good, you should see the following output from the load balancer container telling you that both Fn servers are running, healthy and accessible from the load balancer: Fn load balancer with 2 Fn servers Let’s try this out! Since load balancer is exposed on port 8080, we can simply run the CLI commands to deploy the apps (we could have used a different port for the load balancer and then set the environment variable to point to the actual host and port). fn FN_API_URL At this point you can create and deploy a couple of new functions: fn init --runtime go testapp1fn init --runtime go testapp2fn init --runtime go testapp3 cd testapp1fn deploy --local --app testapp1cd .. cd testapp2fn deploy --local --app testapp2cd .. cd testapp3fn deploy --local --app testapp3cd .. And then try calling them to see that the calls are being routed to both Fn server instances. I used this command to continuously call the endpoints from multiple terminal windows: while true; do sleep 1; curl ; echo $(date);done http://localhost:8080/r/testapp3/testapp3 Make sure you replace the app and func name (testappX) and eventually you should see logs being outputted from both Fn server instances. Management endpoints Fn load balancer also exposes a management endpoint that’s accessible on path and supports , and methods. With you could dynamically add a node to the list of nodes load balancer maintains, the method will remove a specified node and with you can get a list of nodes and their states. You can imagine implementing some sort of a watcher that uses certain events to add/delete nodes from the load balancer. /1/lb/nodes PUT DELETE GET PUT DELETE GET Running on Kubernetes How would we replicate a similar set up, but instead of running it locally, we would run it on Kubernetes? Fn load balancer supports a Kubernetes mode of operation that can be activated by passing in the flag — in this mode the flag will be ignored and you will be able to use labels and label-selectors to pick out the pods that are running Fn servers. You could manually go and create the files necessary to deploy all this on Kubernetes, but the good news is that the Fn team already did this for you! -db=k8s --nodes There’s an and you can use that to install Fn on your Kubernetes cluster. Fn Helm chart available Helm chart on the link above will also install an instance of MySQL and Redis on your cluster as well as the UI and Fn Flow — so you get the full deal with one Helm command. Instructions on how to install it are , but in short once you have installed you run the following commands to initialize Helm, clone the repo, install the chart dependencies and finally install the Fn chart: here Helm helm initgit clone git@github.com:fnproject/fn-helm.git && cd fn-helmhelm dep build fnhelm install --name myfn fn Once installed, you will also see the instructions on how to set the environment variable that points to the load balancer. If you’re using Docker for Mac you can access the load balancer on . FN_API_URL http://localhost:80 If you’re watching the logs from the Fn load balancer (pod that’s created as part of the deployment ), you should see a bunch of activity that indicates new pod was detected and there should be a line that look like this: fn-fnlb-depl time="2018-05-21T22:31:49Z" level=info msg="is healthy" node="10.1.0.23:80" and indicates that Fn load balancer was able to connect to the Fn server. The great thing if you’re using Kubernetes that’s part of Docker for Mac is that the Fn load balancer service is accessible via : [http://localhost:80](http://localhost:80,) $ curl localhost:80/version{"version":"0.3.455"} Note: if you’re deploying this to a “real” cluster, you can look up the external IP of the service by running and checking the column. fn-fn-api kubectl get svc EXTERNAL-IP Hooking up the Fn CLI Assuming you don’t have any Fn servers running locally anymore, you will get an error if you try to run an Fn CLI command. For example: # Try to get the list of apps$ fn list appsERROR: Get : dial tcp [::1]:8080: connect: connection refused http://localhost:8080/v1/apps Since we have Fn load balancer exposed on localhost port 80, we can hook it up with the CLI by setting the environment variable or running the CLI with the variable pre-pended: FN_API_URL FN_API_URL= fn list apps http://localhost:80 Because we haven’t deployed anything yet, the above command will return “no apps found”. Set the to your Docker hub repository and then deploy the testapp1 from before: FN_REGISTRY FN_API_URL=http://localhost:80 fn deploy --app testapp1 : we had to set the FN_REGISTRY, because we won’t be deploying the apps to a “local” Fn server like we did before. We will actually build and push the image to the Docker hub, so Fn server running in the Kubernetes cluster can pull it and run it. Note Last thing to do is to try and run the deployed function. You can either list the routes of the app we deployed to get the full endpoint (e.g. ) or use the Fn CLI to invoke the function like this: http://localhost:80/r/testapp1/testapp1 $ FN_API_URL= fn call testapp1 testapp1{"message1":"Hello World"} http://localhost:80 Conclusion In this article I talked about Fn load balancer and how to set it up either locally for development and just to try things out as well as how to deploy it using a Helm chart on a Kubernetes cluster. With the knowledge from the previous post you could create your custom Fn server image (including your custom extensions) then deploy and run it inside the Kubernetes cluster and perhaps expose the functionality to the end users and allow them to use your platform to deploy their services. Thanks for Reading! Any feedback on this article is more than welcome! You can also follow me on and . If you liked this and want to get notified when I write more stuff, you should subscribe to ! Twitter GitHub my newsletter

Part II: Fn Load Balancer

“A massive white cloud over a snow-capped mountain ridge” by on Benjamin Child Unsplash Table of Contents Part I: Getting started with the Fn project (this post) Part II: Fn Load Balancer (this post) I am not one of those lucky ones who can simply read a whitepaper/code/docs and can quickly figure out how things work without trying things out in practice. I need to install things, run things and play with them to get a feeling for how stuff works. If I get stuck, that’s when I am going to read the docs and code to see what I am missing. In this edition I decided to figure out how works, how to run it, use it and even extend it. The is the container native, cloud agnostic serverless platform. Fn project Fn project As part of this article, I’ve created three different example extensions for the Fn server — you can get them on . GitHub The Basics — install and run This section goes through installing the Fn server, starting it and then creating a simple function and invoking it. You will need Docker on your machine in order to run Fn and once you have that, you can install the Fn with : brew brew install fn Apparently I’ve installed Fn before and the Docker image I had on my machine was stale causing Fn fail when starting — running will ensure you have the latest Fn server image on your machine. fn update server Finally, with Fn installed and images updated, you can run the Fn server with the following command: fn start The above command runs Fn in a single server mode with embedded database and queue. Behind the scenes, command runs a Docker image called in a privileged mode. It also mounts the Docker socket into the container as well as the folder in the current working directory (this is where database and queue information is stored). Finally, it exposes port to the host, so you can invoke it on that port. fn start fnproject/fnserver /data 8080 fnserver image running locally Now that you have the Fn server running, you can create a new function. First function The Fn CLI comes with a command that is used for creating new functions. init At the time of writing, these were the upported function runtimes: dotnet, go, java8, java9, java, lambda-nodejs4.3, lambda-node-4, node, php, python, python3.6, ruby, rust, kotlin Before we start, here’s a simple explanation of different concepts Fn uses: Apps are a way to logically group your functions under the same name (e.g. ) Apps greeter-app Each function has a trigger that has a source (e.g. or ) and a target that’s the endpoint where the function lives (e.g. ) Triggers /greeter-app/hello /greeter-app/goodbye http://localhost:8080/greeter-app/hello **Functions**This is the actual piece of code you are writing and gets executed Docker image that packages your function; the image used depends on the language of the function (e.g. , , , …), the goal here is that the image is as small as possible to be more performant Images fnproject/go fnproject/ruby fnproject/node Call holds information about a call that was made to the function. It includes information about the app, route and time call was created, started and completed include the status of the call. Calls With this out of the way, let’s create a new function by providing a runtime (e.g. Go, Node or other supported language) and the name of the function: fn init --runtime go --trigger http hello Above command creates a Go function in the sub folder. The function structure looks like this: hello hello├── Gopkg.toml├── func.go├── func.yaml└── test.json The source of your function lives inside the file and has a function handler that responds with a “Hello World” message. The file has information such as version runtime, name and entry point for your function. func.go func.yaml Another interesting file is — this file holds an array of tests (input values and expected output values) and you can use it to test out your function, by running . test.json fn test To run this function, you can use the command. Before you run the command, make sure you set the environment variable to your Docker repository. fn run FN_REGISTRY Then when you run the command, Fn will build the Docker image with the function and runs the function like this: $ fn runBuilding image hello:0.0.1 ...........{"message":"Hello World"} This is all great, but we have the Fn server running locally, so let’s deploy our function to the server, instead of just running it. To deploy the function, you can use the command, specify the app name and add the since the Fn server is running locally: fn deploy --local fn deploy --app myapp --local Command deploys the app (called ) to the local Fn server and it creates a path called (our function name). myapp /hello Deploying the app to local Fn server This means that on the Fn server, the function will be accessible under path. The app name is used to logically group functions together. To see the full list of triggers defined on the Fn server, run this command: /myapp/hello # List all triggers for 'myapp'$ fn list triggers myappFUNCTION        NAME            TYPE    SOURCE          ENDPOINThello           hello-trigger   http    /hello-trigger http://localhost:8080/t/myapp/hello-trigger Finally, if you access the endpoint, you will get back the “Hello World” message like this: $ curl {"message":"Hello World"} http://localhost:8080/t/myapp/hello-trigger Grouping functions To group the functions together, you can use the app name construct — this allows you to logically group different routes together (e.g. could have routes called and ). greeter-app /hello /goodbye In this case the could also be the folder name where your functions live and subfolders and would contain the actual functions. You can also define the file in the app root folder, to be able to deploy all functions with one command. greeter-app /hello /goodbye app.yaml Follow the steps below to create a greeter-app with hello and goodbye functions: # Create the greeter-app foldermkdir greeter-app && cd greeter-app # Create app.yaml that defines the app nameecho "name: greeter-app" > app.yaml # Create a hello function in /hello subfolderfn init --runtime go --trigger http hello # Create a goodbye function in /goodbye subfolderfn init --runtime go --trigger http goodbye With all this set up and in the root folder, you can use this command to deploy all functions to local Fn server: app.yaml fn deploy --all --local Above command creates the following app and endpoints: $ fn list routes greeter-apppath     image         endpoint/goodbye goodbye:0.0.2 localhost:8080/r/greeter-app/goodbye/hello   hello:0.0.2   localhost:8080/r/greeter-app/hello You can also create a function that lives in the root of your app by running command from the apps’ root folder: fn init fn init --runtime node --trigger http Then deploy it again: fn deploy --all --local Now we have three functions under the /greeter-app logically group: $ fn list routes greeter-apppath     image             endpoint/        greeter-app:0.0.2 localhost:8080/r/greeter-app/goodbye goodbye:0.0.3     localhost:8080/r/greeter-app/goodbye/hello   hello:0.0.3       localhost:8080/r/greeter-app/hello Enabling the UI If you prefer UI to interact with the Fn — there’s that for you as well. Assuming you have the Fn server running locally, you can start the UI like this: docker run --rm -it --link fnserver:api -p 4000:4000 -e "FN_API_URL= " fnproject/ui http://api:8080 When image gets downloaded and container executes, you’ll be able to access the UI on . [http://localhost:4000](http://localhost:4000) Fn server UI Extending Fn There are a couple of different options for you to extend the Fn server. All options require you to rebuild the Fn server as you will have to import your extension — you can either use the CLI command and file to build a new image of the Fn server with your extension(s) OR you can fork & clone the Fn repo and reference your extension in file, then re-build the code and run it. build-server ext.yaml cmd/fnserver/main.go For development, the fastest way is to clone the Fn repo and create & register your extension there. If you are using command it might take a bit longer as that command will re-build the Fn server image each time it’s invoked. Note that you will have to build the Fn server each time in both cases, but the straight-up Go build is much faster than rebuilding a Docker image. build-server There are three extension points on the Fn server: listeners, middleware, custom API endpoints. Read on for a more detailed description of each extension point and look at some examples later in the article. Listeners You can listen to various API events and respond to them. There are 2 types of listeners at this moment: App and Call. I think Route listeners should come soon as well… In an App listener, you can respond to the following events: BeforeAppCreate AfterAppCreate BeforeAppUpdate AfterAppUpdate BeforeAppDelete AfterAppDelete These events are available in a Call listener: BeforeCall AfterCall Middleware With middleware you can add desired functionality for every API request that comes to the server. Within that middleware you can then decide if you want to cancel the request or if you want to call the next middleware in the chain. A simple example of a middleware would be an authentication middleware that checks headers for a token or a middleware that logs certain things for each request. Custom API endpoints Custom API endpoints allow you to add new endpoints to the Fn server. For example, you could add a custom API endpoint that handles requests to a custom route such or define an endpoint with route or . /mycustomroute /v1/apps/:app_name/mycustomhandler /v1/apps/:app_name/routes/:route_name/mycustomhandler For example, one could implement a custom endpoint on apps and routes called (so, and ) and when those endpoints are invoked you could return some basic stats for the app or a route. stats /v1/apps/:app_name/stats /v1/app:app_name/routes/:route_name/stats Example: Call counter extension using Call listener I wrote a simple extension that counts the number of times an app has been called and it outputs that number to the stdout. You can get the source code for the extension . here The extension implementation is separated into two files: and . callcount.go calllistener.go In the first file ( ) I register the extension and set up the call listener like this: callcount.go In the function, I am creating a map called that I’ll use to increment the calls to specific app and then I am registering the extension by calling function and passing in my extension struct that implements and functions. In the name function I am simply returning just the import name where the extension is located at and in the Setup function I am actually adding the Call listener, telling the Fn that I’ll be listening to Call events (these events are implemented in the file): init callCountMap RegisterExtension Name Setup calllistener.go In the function we check if there’s an entry with the in the map, and if it isn’t, we set the number of calls to 0. Similarly, in the function we increment the number of calls for the and print out that number. BeforeCall AppID AfterCall AppID With the extension ready we can modify the Fn server to include our extension. There are two things we need to do in the cmd/fnserver/main.go file: Import the extension like this (line in bold): import ("context""github.com/fnproject/fn/api/server"**  _ "github.com/peterj/fn-extensions/callcount"**) 2. Call in the function: AddExtensionByName main func main() {ctx := context.Background()funcServer := server.NewFromEnv(ctx) funcServer.Start(ctx)} funcServer.AddExtensionByName("github.com/peterj/fn-    extensions/callcount") Finally, we can build the fnserver and run it to try out the extension. Try out the extension Let’s run the command below to rebuild the : fnserver go build -o fnserver ./cmd/fnserver Finally, run the and when it starts, try calling a function you’ve deployed earlier. You should see the “Call number: X” in the Fn server output: ./fnserver Extension in action! Just like we implemented the Call listener, we could similarly add the App listener, middleware or custom API endpoints. Adding the App listener is similar to adding the Call listener — we’d need to create methods on our extension struct to satisfy the App listener interface, and then call function. AddAppListener Example: Cancel call middleware Let’s show how would one implement a middleware function that checks if a certain header is present ( ) and cancels the chain of calls — that is, it doesn’t execute the function. fn-cancel-call There are two different ways to inject custom middleware. One is using the — this function injects the middleware to all API endpoints such as: AddAPIMiddleware /v1/apps /v1/apps/:app /v1/apps/:app/routes … The other function — — injects the middleware to both API and your app calls as well. AddRootMiddleware To create a custom middleware we need implement a function on our extension struct. Just like before, the source code for the extension is available . Handle(next http.Handler) http.Handler here The extension registration and setup part is the same as previously, the only difference is the implementation of the middleware and the fact that we call function, instead of a function: AddRootMiddleware AddCallListener The logic for the middleware is in lines 30–40. We get the header named and if the value of that header is set to 1, we output a message and return from the function, canceling the remaining chain of middlewares. If cancel header is not set, we call the next handler in line for execution ( ) and continue the execution. fn-cancel-call next.ServeHTTP Example: Call logs using custom API endpoint In this last example, we are going to implement a custom API app endpoint that connect to the Fn server database an returns a list of calls that were made to the app. We are going to return a couple of fields from that array to the user. /v1/apps/:app/logs If you went through other examples, then the above code should look familiar. There are only a couple of differences — on line 23 where we are setting up the extension, we add the reference to our extension struct, so we can use it later in the func and get the information about the calls. We also call the to set up our custom API endpoint on the /logs path and specify the HTTP method. Datastore ServeHTTP AddAppEndpoint GET The functionality of the extension is in the func on line 35. Here, we set up a first, then pass it to the func on the datastore to retrieve the calls made to the app. ServerHTTP CallFilter GetCalls On line 43 we are using a func that’s coming from the Fn server package to send the error response, in case we can’t retrieve the calls. Once we get the calls, we go through each one of them and write the call ID, status, path and time call started to the response writer. Rebuild and run the Fn server then make the call to e.g. — you will get an output similar to the one in the figure below (assuming you made some calls to that app). localhost:8080/v1/apps/myapp/logs Sample output from the call to the /logs custom API endpoint Conclusion This article should serve you as a good introduction and getting started document for the Fn. It gives you the basics you need to start playing the serverless on your local machine and gets you thinking about different ways you can extend it. I will probably write a follow up article where I’ll talk about , and how to get Fn running on Kubernetes. Fn Flow Server Fn Loadbalancer Thanks for Reading! Any feedback on this article is more than welcome! You can also follow me on and . If you liked this and want to get notified when I write more stuff, you should subscribe to ! Twitter GitHub my newsletter

Playing with the Fn project

I have been on a long journey with for over 15 years. And for the last two years, I’ve been teaching people C# in a local IT school. There are topics that cause a lot of confusion in C#. Reflection is one of those. C# According to , reflection in C# provides objects (of type ) that describe assemblies, modules, and types. It allows you to perform various dynamic operations, such as creating instances of types, binding types to existing objects, invoking methods, and accessing fields and properties. Reflection leverages metadata present in assemblies to enable these dynamic capabilities. Microsoft Type In real-life scenarios, reflection can be applied in the following cases: Create custom attributes and access them in your program's metadata. Serialization/deserialization. Dependency Injection. While there are dedicated libraries available for serialization, deserialization, and dependency injection in C# and the platform, understanding how these libraries utilize reflection can provide valuable insights into the inner workings of the language and platform. Additionally, leveraging custom attributes through reflection can offer new possibilities for designing flexible and extensible applications. .NET I hope this overview provides a good starting point to dive into the world of reflection and its applications. If you have any specific questions or if there's anything else I can assist you with, please let me know! Create custom attributes When it comes to creating custom attributes, it's important to understand their purpose and why you might choose to use them instead of alternative approaches. Custom attributes are metadata extensions that provide additional information to the compiler about elements in the program code at runtime. By marking types, methods, properties, or other code elements with custom attributes, you can convey specific information or instructions to other code that interacts with them. Let's consider a simple example where we want to create a custom attribute to represent a minimum value for a property. To create a custom attribute, you need to create a new class that inherits from the class. It is the convention to suffix the attribute class name with "Attribute." System.Attribute public class MinValueAttribute : Attribute
{
    public int Value { get;}
    public MinValueAttribute(int value) => Value = value;
} It is possible to apply the newly created attribute to a certain property of the class. Let’s create a class with property which is marked with . User Age MinValueAttribute public class User
{
    public string Name { get; set; }

    [MinValue(18)]
    public int Age { get; set; }
} Remember that attributes are useless until somebody uses them. It means that some piece of code has to verify if a specific attribute is applied to a particular entity and build some logic based on that. Let’s create a validator class that verifies if is applied and if the current state of the object satisfies minimum value logic. MinValueAttribute public static class MinValueValidator
{
    public static bool Validate(User person)
    {
        var type = typeof(User);
        var properties = type.GetProperties();

        foreach (var property in properties)
        {
            var attributes = property.GetCustomAttributes(false);

            foreach (var attr in attributes)
            {
                if (attr is MinValueAttribute minValueAttribute)
                {
                    var propValue = property.GetValue(person, null);
                    if (propValue == null || 
                        int.Parse(propValue.ToString()) < minValueAttribute.Value)
                    {
                        return false;
                    }
                }
            }
        }
    
        return true;
    }
} To get object of the particular class we can use 3 different approaches: with the help of operator, using method of the class, or using the static method .  After that, we need to get all the properties of the type under inspection by calling the method. For each property, we need to call method and for each attribute check if it is a required one by using operator. If it is we can call method for the property object to get actually value of the property. Then it is possible to compare the actual property value and the for the . Type typeof GetType() Object Type.GetType() GetProperties() GetCustomAttributes() is GetValue() Value MinValueAttribute To run the validator we can use the following code: var user = new User() { Age = 45, Name = "John" };
Console.WriteLine("User is under 18: " + MinValueValidator.Validate(user)); It has to return string. User is under 18: True Serialization/deserialization Serialization converts object state into a transportable or persistent format. Deserialization reverses this process. Popular serialization formats include XML, JSON, and binary.. How can we utilize reflection for this purpose? Remember that reflection provides object that contains all the information of class members and their states. That is what we need to make serialization work. Let’s create a simple class and the method inside. Type XmlConvertor Serialize() public static class XmlConverter
{
    public static string Serialize(object obj)
    {
        var sb = new StringBuilder();
        var type = obj.GetType();

        sb.AppendLine("<" + type.Name + ">");

        var props = new List<PropertyInfo>(type.GetProperties());
        foreach (var prop in props)
        {
            var propValue = prop.GetValue(obj, null);
            sb.AppendLine("\t<" + prop.Name + ">" + propValue + "</" + prop.Name + ">");
        }

        sb.AppendLine("</" + type.Name + ">");

        return sb.ToString();
    }
} All we need to do is to call method for the object and iterate through existing collection to retrieve their values using method. What is left is just to create a proper XML string. Let’s serialize the object we described earlier. GetProperties() Type PropertyInfo GetValue() User var obj = new User { Name = "John Doe", Age = 30 };
var s = XmlConverter.Serialize(obj);
Console.WriteLine(s); Output: <User>
  <Name>John Doe</Name>
  <Age>30</Age>
</User> Let’s write method for the opposite operation to convert XML into a C# object. It can be made generic to simplify the way we determine the type to deserialize. Deserialize() public static class XmlConverter
{
    // Serialize() method is somewhere here

    public static T Deserialize<T>(string s)
    {
        // instantiate the object to be deserialized
        var assembly = typeof(T).Assembly;
        var obj = assembly.CreateInstance(typeof(T).FullName);
        if (obj == null)
        {
            throw new Exception($"Can't instantiate a new object of type '{typeof(T).FullName}'");
        }
        
        // parse input string int XML document
        var doc = XDocument.Parse(s);
        if (doc.Root == null)
        {
            throw new ArgumentException("Can't parse specified xml string");
        }

        // deserialize class members states
        foreach (var node in doc.Root.Elements())
        {
            var property = 
                obj.GetType()
                   .GetProperty(node.Name.LocalName, BindingFlags.Public | BindingFlags.Instance);
            if (null != property && property.CanWrite)
            {
                if (typeof(int) == property.PropertyType)
                {
                    property.SetValue(obj, int.Parse(node.Value));
                } 
                else if (typeof(string) == property.PropertyType)
                {
                    property.SetValue(obj, node.Value);    
                }
                // TODO: add other types conversion
            }
        }
        
        return (T)obj;
    }
} First of all, we need to get the object from the type we want to deserialize. It provides method to create a new object from the specified type. Then we have to parse XML and iterate over the all elements. Since we have a very simple XML structure we just need to iterate over the internal nodes and use method to find a corresponding property of the deserialized object. After that, we can call method to set the actual value. The section with setting properties value could be quite bulky so I just wrote an example for the and types. Assembly CreateInstance() GetProperty() SetValue() int string Let’s verify the method. Deserialize() var stringToDecode = "<User><Name>John Doe</Name><Age>30</Age></User>";
var decodedUser = XmlConverter.Deserialize<User>(stringToDecode);
Console.WriteLine("User name: " + decodedUser.Name);
Console.WriteLine("User age: " + decodedUser.Age); It will bring the following output: User name: John Doe
User age: 30 Dependency Injection Dependency Injection (DI) is a design pattern that encourages loose coupling between classes. It enables the passing of dependencies into a class from external sources, rather than having the class handle its dependencies internally. This approach enhances class modularity, testability, and maintainability. To understand the Dependency Injection pattern we need to see the participants it comprises of. The client class (dependent class) is a class that depends on the service class Client Class: The service class (dependency) is a class that provides service to the client class. Service Class: The injector class injects the service class object into the client class. Injector Class: The following figure illustrates the relationship between these classes: The IoC container creates an object of the specified class and also injects all the dependency objects through a constructor, a property, or a method at run time and disposes it at the appropriate time. There is a number of IoC container libraries implemented for the C#. But let’s create our one DI container to see how it utilizes reflection for its needs. We are going to introduce Client and Service classes, and the dependency between them through the interface. It is a good practice to use interfaces as a contract to interact between two objects to follow the Dependency Inversion principle. There is an interface for the service with the method. Process() public interface IService
{
    void Process();
} The implementation of the interface is very simple just to do some action inside the method. IService public class Service : IService
{
    public void Process()
    {
        System.Console.WriteLine("Call Process() method");
    }
} The client code uses as an abstraction between the Service and the Client. IService public class Client
{
    private IService _service;
    
    public Client(IService service)
    {
        _service = service;
    }

    public void RunProcess()
    {
        _service.Process();
    }
} Let’s create a simple class and implement Dependency Injection mechanisms. Container public class Container
{
    private Dictionary<Type, Type> _containerData = new Dictionary<Type, Type>();

    public void Register<TType, TImplementation>()
    {
        _containerData.Add(typeof(TType), typeof(TImplementation));
    }
} Inside the container, we need a dictionary that contains the type we want to register as a key and the type that represents the implementation as a value. is a generic method that accepts two types, the type to be registered and the implementation for it. _containerData Register<TType, TImplementation>() public class Container
{
    // ...
        
    public TType GetInstance<TType>()
    {
        var type = typeof(TType);
        if (type.GetConstructors().Length > 1)
            throw new Exception($"The type '{type.FullName}' should implement only one constructor");
        
        ConstructorInfo ctor = type.GetConstructors()[0];
        ParameterInfo[] parameters = ctor.GetParameters();
        object[] constructorArgs = new object[parameters.Length];
        
        for (int i = 0; i < parameters.Length; i++)
        {
            var parameterType = parameters[i].ParameterType;

            if (!_containerData.ContainsKey(parameterType))
                throw new Exception($"Can't find implementation for the type '{parameterType.FullName}'");

            var obj = Activator.CreateInstance(_containerData[parameterType]);
            if (obj != null)
                constructorArgs[i] = obj;
        }
        
        return (TType)ctor.Invoke(constructorArgs);
    }
} To provide instances of the particular type we can write a new method. Inside this method, we need to find the object in the type we want to build and get an array of objects to know which parameters path into the constructor. After that, we could iterate over the array of parameters and instantiate each of them adding them to an array of objects variable. When all the parameters are instantiated we can call method of the constructor and path just created parameters. GetInstance<TType>() ConstructorInfo ParameterInfo constructorArgs Invoke() To verify the functionality of the DI container we can utilize the following code: var container = new Container();
container.Register<IService, Service>();

var client = container.GetInstance<Client>();
client.RunProcess(); You should get the following output: Call Process() method Summary We have only touched the surface of its power, but it can take you a long way in comprehending how widely used libraries operate and how reflection is utilized in everyday tasks. Many C# developers either do not utilize reflection at all or lack understanding of its potential applications. Feel free to delve into the documentation to familiarize yourself with the full range of capabilities offered by reflection.

Exploring the Practical Applications of Reflection in C#

Creating a multi-container application can be daunting, but Docker Compose and C# can make it much more straightforward. This article will walk us through the steps to create a multi-container application with Docker Compose and C#. Prerequisites Basic knowledge of OOPS concepts. Any programming language knowledge. Basic knowledge of docker So, to begin with, C#: Introduction to C# C# has been around for quite some period, and it continues to develop, obtaining more enhanced features. medium.com Learning Objectives How to create a multi-container application with Docker Compose and C#. Getting Started Step 1: Install Docker and Docker Compose Before we begin, make sure that Docker and Docker Compose are installed on your machine. Docker is a platform for developing, shipping, and running applications using containerization, while Docker Compose is a tool for defining and running multi-container Docker applications. You can download Docker and Docker Compose from their respective websites. Step 2: Create a New Project Directory Once Docker and Docker Compose are installed, please create a new directory for your project and navigate to it using your terminal. For this example, we will call our project "my-csharp-app". mkdir my-csharp-app
cd my-csharp-app Step 3: Create a Frontend Dockerfile Next, we will create a Dockerfile for our frontend container. This container will serve as a basic HTML page that calls our backend API. Create a new file called "Dockerfile.frontend" in your project directory and add the following code: FROM nginx:alpine
COPY ./nginx.conf /etc/nginx/conf.d/default.conf
COPY ./wwwroot /usr/share/nginx/html This Dockerfile uses the official nginx: alpine image as its base and copies our custom nginx configuration file and HTML files to the appropriate directories. Step 4: Create a Backend Dockerfile Next, we will create a Dockerfile for our backend container. This container will serve a simple C# API that returns a list of users in JSON format. Create a new file called "Dockerfile.backend" in your project directory and add the following code: FROM mcr.microsoft.com/dotnet/sdk:6.0 AS build
WORKDIR /app
COPY . .
RUN dotnet restore
RUN dotnet publish -c Release -o out

FROM mcr.microsoft.com/dotnet/aspnet:6.0
WORKDIR /app
COPY --from=build /app/out .
ENTRYPOINT ["dotnet", "MyCSharpApp.dll"] This Dockerfile uses the official dotnet SDK as its base and copies our application code to the appropriate directory. It then restores dependencies, builds the application, and publishes it to an output directory. Finally, it copies the output to the appropriate directory in the final container and sets the entry point to start the application. Step 5: Create a Docker Compose File Now that we have our Dockerfiles, we can create a Docker Compose file to define our multi-container application. Create a new file called "docker-compose.yml" in your project directory and add the following code: version: "3"
services:
  frontend:
    build:
      context: .
      dockerfile: Dockerfile.frontend
    ports:
      - "8080:80"
    depends_on:
      - backend
  backend:
    build:
      context: .
      dockerfile: Dockerfile.backend
    ports:
      - "5000:5000" This Docker Compose file defines two services: "frontend" and "backend". The "frontend" service uses the Dockerfile.frontend file we created earlier to build its image. It exposes port 8080 on the host machine, which is mapped to port 80 in the container. It also depends on the "backend" service, meaning it will not start until the "backend" service is running. The "backend" service uses the Dockerfile.backend file we created earlier to build its image. It exposes port 5000 on both the host and container and has no dependencies on other services. Step 6: Add Configuration Files We need to add some configuration files that our containers will use to communicate. Create a new directory called "config" in your project directory, and create two files inside it: "appsettings.json" and "nginx.conf". In the "appsettings.json" file, add the following code: {
  "BackendBaseUrl": "http://backend:5000"
} This configuration file defines a variable called "BackendBaseUrl" used by our frontend container to make API calls to our backend container. In the "nginx.conf" file, add the following code: server {
    listen       80;
    server_name  localhost;
    location / {
        proxy_pass         http://frontend:80;
        proxy_redirect     off;
        proxy_set_header   Host $host;
        proxy_set_header   X-Real-IP $remote_addr;
        proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header   X-Forwarded-Host $server_name;
    }
} This configuration file defines the NGINX reverse proxy settings, allowing our frontend container to communicate with our backend container. Step 7: Write the Application Code Now that we have our containers and configuration files, we can write the application code that will run inside them. Create a new directory called "src" in your project directory, and create two files inside it: "Program.cs" and "UserController.cs". In the "Program.cs" file, add the following code: using Microsoft.AspNetCore.Hosting;
using Microsoft.Extensions.Hosting;

namespace MyCSharpApp
{
    public class Program
    {
        public static void Main(string[] args)
        {
            CreateHostBuilder(args).Build().Run();
        }
        public static IHostBuilder CreateHostBuilder(string[] args) =>
            Host.CreateDefaultBuilder(args)
                .ConfigureWebHostDefaults(webBuilder =>
                {
                    webBuilder.UseStartup<Startup>();
                });
    }
} This code sets up the entry point for our backend container and configures it to use a "Startup" class that we will define in the next step. In the "UserController.cs" file, add the following code: using System.Collections.Generic;
using Microsoft.AspNetCore.Mvc;

namespace MyCSharpApp.Controllers
{
    [ApiController]
    [Route("[controller]")]
    public class UserController : ControllerBase
    {
        private static readonly List<string> Users = new List<string> { "Alice", "Bob", "Charlie" };
        [HttpGet]
        public ActionResult<IEnumerable<string>> Get()
        {
            return Ok(Users);
        }
    }
} This code defines a simple controller that returns a list of users when an HTTP GET request is made to the "/user" route. Step 8: Write the Startup Class Create a new file called "Startup.cs" in your project directory, and add the following code: using Microsoft.AspNetCore.Builder;
using Microsoft.AspNetCore.Hosting;
using Microsoft.AspNetCore.Http;
using Microsoft.Extensions.Configuration;
using Microsoft.Extensions.DependencyInjection;
using Microsoft.Extensions.Hosting;

namespace MyCSharpApp
{
    public class Startup
    {
        public Startup(IConfiguration configuration)
        {
            Configuration = configuration;
        }
        public IConfiguration Configuration { get; }
        public void ConfigureServices(IServiceCollection services)
        {
            services.AddControllers();
        }
        public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
        {
            app.UseRouting();
            app.UseEndpoints(endpoints =>
            {
                endpoints.MapControllers();
            });
        }
    }
} This code sets up the middleware for our backend container and adds support for controllers. Step 9: Build and Run the Application Now that we have written our application code, we can build and run our containers using Docker Compose. In your terminal, navigate to your project directory and run the following command: docker-compose up This command will build and start the containers defined in our "docker-compose.yml" file. Once the containers are running, you should be able to access the application by navigating to " " in your web browser. http://localhost You should see a page that displays a list of users, which is being served by our backend container and demonstrated by our frontend container. Step 10: Stop the Application After testing your application, you can stop all the running containers by pressing "Ctrl-C" in your terminal. This will stop and remove all the containers but will not delete any data or configuration files you created. Conclusion This article demonstrates how to create a multi-container application using Docker Compose and C#. By breaking our application into smaller, more modular containers, we can improve the scalability and maintainability of our application and make it easier to develop and deploy. Docker Compose provides a powerful toolset for managing complex container-based applications, and C# offers a robust and flexible platform for building web applications. By combining these two technologies, we can create modern, cloud-native applications that are efficient, reliable, and easy to manage. Follow Me On , , , , , C# Publication LinkedIn Instagram Twitter Dev.to BuyMeACoffee Also published here

How to Create Multi-Container Applications With Docker Compose and C#

This article will guide you through an example of how you can implement our to create an report viewer application to allow your end users to view reports directly in their web browser. JSViewer web report viewer ASP.NET 6.0 (or ASP.NET Core) Our JSViewer component can be used in a wide variety of project types, such as ASP.NET, pure , , , , and . Our example will, of course, cover ASP.NET in particular. JavaScript Angular React Vue Blazor This article explicitly covers the viewer, so please check out our pages for more information on designers if you want information on giving your users access to a full-fledged designer. report designer How To Embed JSViewer to Create Your Own ASP.NET 6.0 (or .NET Core) Report Viewer Application Before we get started, you can find pre-configured projects for ASP.NET MVC, React, Angular, Vue, and Blazor on our . Implement the JSViewer into one of your own pre-existing applications with these steps: ActiveReports Samples GitHub repository Creating a New ASP.NET Project Configuring the JSViewer Middleware Add the JSViewer Package to the Application Setting Up the JSViewer ASP.NET Core Middleware First, we’ll need to set up the middleware for our JSViewer. These middleware components will handle HTTP requests and responses. The default code added by the ASP.NET Core Web App template in Visual Studio will set up the of our request processing pipeline just fine, so let's start there. core Creating a New ASP.NET Project 1. Open Visual Studio and select “Create a new project” 2. Select ASP.NET Core Web App 3. Name the project, whatever you deem appropriate, and click “Next” 4. Select your target framework and uncheck “Configure for HTTPS”, then click “Create” In this example, we will be selecting .NET 6.0 Configuring the JSViewer Middleware Now we’ve got a good template to start with, so we can go ahead and start making some changes to get it up to speed on handling our web reporting needs. 1. Right-click the project in the Solution Explorer and select “Manage Nuget Packages” 2. Click “Browse” and then add the following package to the project: GrapeCity.ActiveReports.Aspnetcore.Viewer 3. In the License Acceptance dialog that appears, click “I Accept” 4. Add a new folder called “Reports” in the application’s root directory and place any report you want to display in the viewer in this folder FYI, this is far from the only way to make reports accessible to the report viewer component, but this is just a convenient and easy way to do it for our ASP.NET Core report viewer example 5. Make sure to set the “Build Action” property of any report files to “Embedded Resource” 6. If you are using a version of .NET , replace the contents of the “Startup.cs” file with the following: older than .NET 6.0 using Microsoft.AspNetCore.Builder;
using Microsoft.AspNetCore.Hosting;
using Microsoft.Extensions.Configuration;
using Microsoft.Extensions.DependencyInjection;
using Microsoft.Extensions.Hosting;
using GrapeCity.ActiveReports.Aspnetcore.Viewer;
namespace JsViewer_Core
{
    public class Startup
    {
        public Startup(IConfiguration configuration)
        {
            Configuration = configuration;
        }
        public IConfiguration Configuration { get; }
        // This method gets called by the runtime. Use this method to add services to the container.
        public void ConfigureServices(IServiceCollection services)
        {
            services.AddRazorPages();
        }
        // This method gets called by the runtime. Use this method to configure the HTTP request pipeline.
        public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
        {
            if (env.IsDevelopment())
            {
                app.UseDeveloperExceptionPage();
            }
            else
            {
                app.UseExceptionHandler("/Error");
            }
            app.UseReporting(settings =>
            {
                settings.UseEmbeddedTemplates("JsViewer_Sample.Reports", this.GetType().Assembly);
                settings.UseCompression = true;
            });
            app.UseStaticFiles();
            app.UseRouting();
            app.UseAuthorization();
            app.UseEndpoints(endpoints =>
            {
                endpoints.MapRazorPages();
            });
        }
    }
} Make sure that the correct namespace is provided in the first argument of “UseEmbeddedTemplates“ for the report. It should be “NameOfYourProject.Reports” 7. If you are targeting .NET 6.0 like we are, you will need to modify the “Program.cs” file instead as follows: using GrapeCity.ActiveReports.Aspnetcore.Viewer;

var builder = WebApplication.CreateBuilder(args);
// Add services to the container.
builder.Services.AddRazorPages();
;
var app = builder.Build();
// Configure the HTTP request pipeline.
if (!app.Environment.IsDevelopment())
{
    app.UseExceptionHandler("/Error");
    // The default HSTS value is 30 days. You may want to change this for production scenarios, see https://aka.ms/aspnetcore-hsts.
    app.UseHsts();
}
app.UseHttpsRedirection();
app.UseStaticFiles();
app.UseReporting(settings =>
{
    settings.UseEmbeddedTemplates("JsViewer_Sample.Reports", System.Reflection.Assembly.GetEntryAssembly());
    settings.UseCompression = true;
});
app.UseRouting();
app.UseAuthorization();
app.MapRazorPages();
app.Run(); Make sure that the correct namespace is provided in the first argument of “UseEmbeddedTemplates” for the report. It should be “NameOfYourProject.Reports” Integrating With the Front End Now that we have the middleware setup, we can move on to setting up the front end and start seeing things come into place. In our example, we will be covering setting this up with a plain ASP.NET 6.0 / JavaScript front end, but if you need help setting this up in other frameworks, you can follow these links to our for , , and . documentation Angular React Vue Add the JSViewer Package to the Application 1. Open the “Tools” menu and select “NuGet Package Manager” > “Package Manager Console” and then run the following command in the console: npm install @grapecity/ar-viewer 2. Copy the “jsViewer.min.js” and “jsViewer.min.css” files installed in the “node_modules\@grapecity\ar-viewer\dist” folder to the “wwwroot\js” and “wwwroot\css” folders in the application, respectively Note: You may need to open the project directory in the file explorer to see these files, as they may not show up in the Solution Explorer 3. Replace the code in the “Index.cshtml” file with the following: @page
@model IndexModel
@{
    ViewData["Title"] = "Home page";
}
<!DOCTYPE html>
<html lang="en">
<head>
    <title>ActiveReports JSViewer</title>
    <link rel="stylesheet" href="css/jsViewer.min.css" />
</head>
<body>
    <div id="viewer-id" style="width: 100%; height: 100%;">
    </div>
    
    <script src="js/jsViewer.min.js"></script>
    <script type="text/javascript">
        GrapeCity.ActiveReports.JSViewer.create({
            element: '#viewer-id',
            reportService: {
                url: 'api/reporting',
            },
            reportID: 'MyReport.rdlx',
            settings: {
                zoomType: 'FitPage'
            },
        });
    </script>
</body>
</html> Replace the report name “MyReport.rdlx” after “reportID:” with the name of the report you put in the “Reports” folder That’s it! You can go ahead and run the application now, and from here, you should be able to use the interface to load any reports you added to your project. Additionally, if you’d like to load a particular report via code later, you can use the following code to do so: var viewer = new GrapeCity.ActiveReports.JSViewer.create({
    element: '#viewer-host'
});
viewer.openReport("DemoReport.rdlx"); As usual, if you are using Angular, React, or Vue, you can find the respective ways to do this in our documentation.

Building an ASP.NET Core MVC 6.0 Report Viewer Application

Over the years I have faced several linux challenges that I have solved by googling or thanks to beautiful people who have shared their knowledge. This is a brief compilation of useful tricks grouped in different categories: Files management, searching, bash scripting, networking, compressed files management, packet management, server information and miscellaneous. 📝📁Files management Delete Delete first line: sed -i '1d' file.txt Delete all empty lines: sed '/^$/d' file.txt Delete first two characters from each line: cat file.txt | sed 's/^..//' Delete comments and empty lines: sed '/ *#/d; /^$/d' file.txt Delete carriage return \r: cat input.txt|tr -d "\r" > output.txt Replace Replace with string1 string2 sed -d 's/string1/string2/g' file.txt Replace space by : - sed ':a;N;$!ba;s/\n/\'\'\-\'/g'' Replace replace line break with space: sed ':a;N;$!ba;s/\n/ /g' Add Add at the beginning of the line - sed -d s/^/\-/ file.txt Add at the end of the line - sed -d s/$/\-/ file.txt Filter Filter lines starting with a number: cat file.txt |grep ^[0-9] Filter multiple words: grep -E 'string1|string2' file.txt Filter multiple words old shells: grep -e 'string1' -e 'string2' file.txt Print the third and tenth words from file: cat file.txt | awk '{print $3,$10}' Print the third word from file separated by : - cat file.txt| awk -F"-" '{print $3}' Misc Split a large file every 2000 lines: split -l 2000 input.txt output.txt View  only the lines that contain string1 : sed -n '/string1/p' files.txt Convert lowercase to uppercase: cat file.txt | tr '[:lower:]' '[:upper:] ' Copy permissions from a reference file: chmod --reference=reference_file new_file Copy ownership from a reference file: chown --reference=reference_file new_file 🧮 Let's count Files on the directory: ls | wc -l Lines in a file: wc -l file.txt Words in a file: wc -s file.txt Length of the longest line in a file: wc -L file.txt Number of files and directories in a directory: tree -a 🔍Searching Files less than two days old find -mtime -2 Files older than 5 days: find -mtime +5 Files created today: find ./ -type f -daystart -ctime -1 Directory by name: find / -type d -name directory_name Find files by content: find ./ -type f -exec grep -H ' content ' {} \; 👨‍💻👩‍💻Bash scripting basics For syntax #!/bin/bash for i in `seq 1 90` do echo $i done Execution: ./read_file_line_per_line.sh file_to_read.txt Read file line per line #!/bin/bash while IFS='' read -r line || [[ -n "$line" ]]; do echo "Text read from file: $line" done < "$1" Execution: ./read_file_line_per_line.sh file_to_read.txt Read file word per word #!/bin/bash while IFS='' read -r line || [[ -n "$line" ]]; do for word in $line do echo $word done done < "$1" Check if a file exists #!/bin/bash if [ -f $path/to/file.txt ];  then echo "exist" else echo "no exist" fi Check ip reachability #!/bin/bash ping -w1 -c3 $IP >/dev/null 2>&1 && echo "ON" || echo "OFF" 🌐Networking Ping from a defined interface: ping -I interface_name ip Rename interface: link set current_name name new_name Show IP addresses without infconfig : ip address show Traffic Traffic capture with tshark: tshark -i interface_name .151 -f "host ip and port port_number " Traffic capture with tcpdump: tcpdump -i interface_name dst port port port_number -w capture.pcap Store traffic output: tcpdump -ni eth0 -w capture.pcap Read traffic capture form the CLI: tcpdump -ttttnnr capture.pcap 👀 Port scanning Check if 5050 port is open: nc -zvn ip 5050 Check if 5050 and 5055 are open: nc -zvn ip 5050 5055 Check if range of ports: nc -zvn ip 5050-5055 Connect to on port 5050 and send content of input.in: ip nc ip 5050 < input.in 👂👂 Listening Listen for TCP connections on port 5050: netcat -l 5050 Listen for UDP connections on port 5050: netcat -ul 5050 Listen for TCP connections on port 5050 and store data received in to "received.txt": netcat -l 5050 > received.txt Listen for TCP connections on port 5050 and continue listening after client has disconnected: netcat -k -l 5050 🗃️ Compressed files management : Decompress: .tar.gz files Compress tar -czvf compressed.tar.gz /direcory/to/compress/ tar -xzvf compressed.tar.gz : Decompress: .tar files Compress tar -cvf compressed.tar /direcory/to/compress/ tar -xvf compressed.tar : Decompress: .gz files Compress gzip file.txt gzip -d file.txt.gz : Decompress: .zip files Compress zip compressed.zip /direcory/to/compress/ unzip compressed.zip 🎉 Read compressed file without decompress: Filter compressed file without decompress: Split compressed file in parts of 10m size: Bonus zcat compressed.gz zgrep -n string compressed.gz split -b 10m file.tar.gz "file.tar.gz.part" 📦Packet management (YUM and DNF) What provides a package yum whatprovides package_name dnf provides package_name Package description: yum info package_name dnf info package_name Update security  packages: yum update --security dnf update --security List dependencies from a package example httpd: yum deplist httpd dnf repoquery --deplist httpd Download all packages and dependencies needed to install something, example FTP: yumdownloader --resolve FTP dnfdownload --resolve FTP Remove orphan packages: and and package-cleanup --orphans package-cleanup --oldkernels dnf list extras dnf remove $( dnf repoquery --installonly --latest-limit -1 -q ) List pending security updates: yum list-security dnf updateinfo list --security ℹ️Server info Number of processors: grep processor /proc/cpuinfo | wc -l Number of cores: dmidecode -t processor | grep "Core Count" Number of enabled cores: dmidecode -t processor | grep "Core Enabled" RAM memory: free -m | head -2 | tail -1 | awk {'print $4'} Free space: df -h | awk {'print $3'} | head -3 | tail -1 Release version: cat /etc/*release* 🍕 Misc Execute a command as another user: sudo -u user command Clean cache: echo 3 > /proc/sys/vm/drop_caches Create symbolic link: ln -s /file_or_directory_path /direct_access_path Create FIFO files: mkfifo filename Know more information about and image from CLI: identify -verbose image.png Pretty print json files in CLI: cat file.json | jq Print only values of the key my_key from json file: jq '.[] | .my_key' file.json Hope this was useful for you. If you want more don't hesitate visit my github

A Linux Cheat-sheet So Good, You'll Want to Save It

Learning Objectives How to add GraphQL wrapper How to use the NSwag tool to generate code Prerequisites Require “HotChocolate.AspNetCore” from the NuGet package. Require .Net 5 Framework. Visual Studio IDE. Understanding of .Net Web API project. Basic knowledge of Swagger UI. Getting Started allows you to ask for what you want in a single query, save bandwidth, and reduce requests. GraphQL Step 1: Create a new project Create a new project in Core Web API template for this article demonstration, as shown below. ASP.Net The problem of generating helpful documentation and help pages for Web APIs. Now .Net project is by default enabled with swagger, as shown on the localhost URL Step 2: Add GraphQL packages Install the “ ” package from the NuGet gallery into the newly created solution in Visual Studio. HotChocolate.AspNetCore Step 3: Generate Manifest file Go to file explorer > project folder and run the following command using the Dotnet Global tool. dotnet new tool-manifest and Install the NSwag tool dotnet tool install NSwag.ConsoleCore Step 4: Create swagger.json Create a swagger JSON file in the project directory using the below command curl <SwaggerJsonFilePath> > swagger.json Click as highlighted below know the swagger JSON file path Example curl https://localhost:44323/swagger/v1/swagger.json > swagger.json Step 5: Generate service files Generate REST service file using the below command with respective namespace and class name. dotnet nswag swagger2csclient 
/input:swagger.json 
/classname:<Clasname> 
/namespace:<Namespace>
/output:<OutputFile> Example dotnet nswag swagger2csclient 
/input:swagger.json 
/classname:RestClass
/namespace:RestNamespace 
/output:ToDoService.cs Step 6: Update the base URL Update the base URL in generated “ToDoService” file. Step 7: Configure GraphQL Playground Attach playground inside the ConfigureServices method in the “Startup.cs” file public void ConfigureServices(IServiceCollection services){

services.AddHttpClient<RestClass>();
  services
   .AddRouting()
   .AddGraphQLServer()
   .AddQueryType<Query>();
} Create GraphQL Query class as follows public class Query
{
	public async Task<ICollection<TodoReader.WeatherForecast>> GetTodosAsync(
		[Service] TodoService service,
		CancellationToken cancellationToken)
	{
		return await service.WeatherForecastAsync(cancellationToken);
	}

} Map GraphQL in Configure method app.UseEndpoints(endpoints =>
{
  endpoints.MapControllers();
  endpoints.MapGraphQL();
}); Step 8: Run the playground Browse the localhost URL at route “/graphql,” and the following GraphQL playground will be displayed. That’s it, successfully integrated GraphQL playground to the .Net REST API along with swagger. GitHub Sample ssukhpinder/DotNetCoreRestApi *Add graphql and swagger to REST API. Contribute to ssukhpinder/DotNetCoreRestApi development by creating an account on…*github.com Live Demo Thank you for reading, and I hope you liked the article. Please provide your feedback in the comment section. Follow me on , , , , , , , C# Publication LinkedIn Instagram Twitter Dev.to Pinterest Substack Wix Also published . here

Fiserv News on
HackerNoon and Around the Web

fiserv.com

44000 employees

Since 1984

31775 at Alexa

📉 Stock Prices

Fiserv Story Mentions

Articles Around the Web

Read More Tech Stories Related to #Fiserv

Fiserv News on HackerNoon and Around the Web