nodeJS and Web APIs
74.4K views | +4 today
nodeJS and Web APIs
about node.js and Web APIs
Your new post is loading...
Your new post is loading...

Popular Tags

Scooped by Srdjan Strbanovic
February 24, 2014 1:21 PM
Scoop.it!

Coding Magic: Express.JS quick-start guide on Windows

Coding Magic: Express.JS quick-start guide on Windows | nodeJS and Web APIs | Scoop.it
No comment yet.
Scooped by Srdjan Strbanovic
February 20, 2014 9:46 AM
Scoop.it!

MTProto Mobile Protocol

MTProto Mobile Protocol | nodeJS and Web APIs | Scoop.it
Please feel free to check out our FAQ for the Technically Inclined. Client developers are required to comply with the Security Guidelines. Related articles Mobile Protocol: Detailed Description Creating an Authorization Key Creating an Authorization Key: Example Mobile Protocol: Service Messages Mobile Protocol: Service Messages about Messages Binary Data Serialization TL Language MTProto TL-schema Security Guidelines for Client Software Developers General Description The protocol is designed for access to a server API from applications running on mobile devices. It must be emphasized that a web browser is not such an application. The protocol is subdivided into three virtually independent components: High-level component (API query language): defines the method whereby API queries and responses are converted to binary messages. Cryptographic (authorization) layer: defines the method by which messages are encrypted prior to being transmitted through the transport protocol. Transport component: defines the..
No comment yet.
Scooped by Srdjan Strbanovic
February 17, 2014 4:53 PM
Scoop.it!

OAuth 2.0 Tutorial

OAuth 2.0 Tutorial | nodeJS and Web APIs | Scoop.it
OAuth 2.0 is an open authentication protocol designed to allow applications to access the data of each others users.
No comment yet.
Scooped by Srdjan Strbanovic
February 13, 2014 6:42 PM
Scoop.it!

kimono: Create APIs where they don't exist - kimono : Turn websites into structured APIs from your browser in seconds

kimono: create APIs where they don't exist
No comment yet.
Scooped by Srdjan Strbanovic
February 13, 2014 2:15 PM
Scoop.it!

How To Build A CLI Tool With Node.js And PhantomJS | Smashing Coding

How To Build A CLI Tool With Node.js And PhantomJS | Smashing Coding | nodeJS and Web APIs | Scoop.it
In this article, we’ll go over the concepts and techniques required to build a command line tool using Node.js and Phantomjs.
No comment yet.
Scooped by Srdjan Strbanovic
February 13, 2014 12:54 PM
Scoop.it!

Beacon performance / Stoyan's phpied.com

Beacon performance / Stoyan's phpied.com | nodeJS and Web APIs | Scoop.it
No comment yet.
Scooped by Srdjan Strbanovic
February 12, 2014 4:47 PM
Scoop.it!

How RareWire uses Postman to save development time and build APIs easily

How RareWire uses Postman to save development time and build APIs easily | nodeJS and Web APIs | Scoop.it
Writing apps that use REST APIs without using Postman is kind of like driving a car with mud or ice on the windshield: if you know your environment and take it slow, you might be safe.
No comment yet.
Scooped by Srdjan Strbanovic
February 12, 2014 1:15 PM
Scoop.it!

Live.pics.io — How We Developed a Service Using WebRTC

Live.pics.io — How We Developed a Service Using WebRTC | nodeJS and Web APIs | Scoop.it
Live.pics.io is a free web-service to share photos and images the new way.This post tells about technical challenges we overcome during its development.
No comment yet.
Scooped by Srdjan Strbanovic
February 12, 2014 11:58 AM
Scoop.it!

Checking out the Helios IIS Owin Web Server Host - Rick Strahl's Web Log

Checking out the Helios IIS Owin Web Server Host - Rick Strahl's Web Log | nodeJS and Web APIs | Scoop.it
No comment yet.
Scooped by Srdjan Strbanovic
February 11, 2014 12:12 PM
Scoop.it!

User Management for Web Apps with UserApp

User Management for Web Apps with UserApp | nodeJS and Web APIs | Scoop.it
Cloud-based user management for web apps.
No comment yet.
Scooped by Srdjan Strbanovic
February 23, 2014 4:42 PM
Scoop.it!

monet.js - For when you have no choice but to use JavaScript

monet.js - For when you have no choice but to use JavaScript | nodeJS and Web APIs | Scoop.it
Monadic library for functional programming in JavaScript.
No comment yet.
Scooped by Srdjan Strbanovic
February 21, 2014 9:15 AM
Scoop.it!

Using Claims in your Web App is Easier with the new OWIN Security Components

Using Claims in your Web App is Easier with the new OWIN Security Components | nodeJS and Web APIs | Scoop.it
.NET Web Development and Tools Blog
No comment yet.
Scooped by Srdjan Strbanovic
February 20, 2014 6:00 PM
Scoop.it!

How To Build A CLI Tool With Node.js And PhantomJS | Smashing Coding

How To Build A CLI Tool With Node.js And PhantomJS | Smashing Coding | nodeJS and Web APIs | Scoop.it
In this article, we’ll go over the concepts and techniques required to build a command line tool using Node.js and Phantomjs.
No comment yet.
Scooped by Srdjan Strbanovic
February 18, 2014 6:06 PM
Scoop.it!

What the "REST"? REST in Pieces - James Tong

What the "REST"? REST in Pieces - James Tong | nodeJS and Web APIs | Scoop.it
What the
No comment yet.
Scooped by Srdjan Strbanovic
February 14, 2014 3:32 PM
Scoop.it!

ExpressJS Named Routes and Regular Expressions – James Jeffery

No comment yet.
Scooped by Srdjan Strbanovic
February 14, 2014 10:01 AM
Scoop.it!

cloudup/browser-repl

cloudup/browser-repl | nodeJS and Web APIs | Scoop.it
Contribute to browser-repl development by creating an account on GitHub.
No comment yet.
Scooped by Srdjan Strbanovic
February 13, 2014 2:21 PM
Scoop.it!

More security and granular control with the new API keys

More security and granular control with the new API keys | nodeJS and Web APIs | Scoop.it
API keys can now be customized in a number of ways.
Users can now have multiple API keys, the keys have a secret to sign requests and you can set granular permissions and whitelist IPs for each and...
No comment yet.
Scooped by Srdjan Strbanovic
February 13, 2014 12:55 PM
Scoop.it!

OWIN Components Registry by owin-middleware

No comment yet.
Scooped by Srdjan Strbanovic
February 13, 2014 10:31 AM
Scoop.it!

OWIN series conclusion - LINQ to Fail

No comment yet.
Scooped by Srdjan Strbanovic
February 12, 2014 4:45 PM
Scoop.it!

The Secure Web Series, Part 1: Securing Your Password Reset Mechanism

The Secure Web Series, Part 1: Securing Your Password Reset Mechanism | nodeJS and Web APIs | Scoop.it
Welcome to a new series on how to avoid common web application
vulnerabilities, called The Secure Web Series. In this series of posts,
I’ll be exploring some of the most common vulnerabilities we see in our
testing practice here at Fortify on Demand. The focus of the series will
be on vulnerabilities that aren’t easily identified via automation, as
these are harder to find using readily available tools and many testing
offerings tend to miss them during assessments. The target audience is
web developers and web application security testers. In each installment
of the series we’ll cover the following areas: The most common flaws we
see in the real world for this particular component of web
applicationsHow to avoid making each of those mistakesA list of best
practices for that componentIn this first installment, we'll be tallking
about vulnerabilities in the Password Reset Mechanism… The Insecure
Password Reset Mechanism Unfortunately, there are a myriad of ways to do
password resets insecurely: User account leakageSending the real
password in emailPredictable reset tokensFailure to expire reset
tokensAuto-logon after reset User Account Leakage Injection attacks are
noisy, take a long time, and have a decently high chance of getting
noticed. So one of the first things an attacker (or a good security
tester) will do on a site is look for a way to log in with a legitimate
account. Many websites have a form field like the one above on their
password reset page. Looks harmless enough, but most have an error in
it: When you enter a valid email address it gives you one message
(you’ll get an email shortly), and if you give it an email address
that’s not in the system it gives you another message (email address not
found). This means that an attacker can use automation to guess email
accounts, and come up with a list of valid users. From there you can
throw some quality password lists at it and probably walk right through
the front door with a valid account. Remediation The way to fix this is
to make the response to both situations identical (and that includes the
time it takes to come back with an answer). So instead of saying, yes or
no depending on the input, instead you ALWAYS say, "If your account was
found, you’ll receive an email shortly." That way we're not saying
whether or not it was found, only that if it was they'll get an email
soon. Sending Your Actual Password in Email One of the worst
vulnerabilities we see in applications’ password reset systems is when
the system just sends us our password in email. There are a couple of
problems with this: They just sent my password over the internet with no
encryptionHOW DID THEY HAVE MY CLEARTEXT PASSWORD?Bad on top of bad.
Remediation Avoid sending users their passwords, and instead have them
come to the website and create a new one. And if you absolutely MUST
send someone a password, it should be a temporary one that requires a
reset when they log in. You should never even know what a user’s real
password is, let alone send it to them over the Internet without
encryption. Predictable Reset Tokens Another serious problem we often
see with passwod reset systems is the use of predictable reset tokens.
This happens when developers either come up with their own, or use
someone else's homegrown solution for making the tokens. Predictable
tokens allow an attacker to make a large number of requests to the
password reset function, gather a large number of tokens, and then
analyze them for patterns. Once a pattern is found, the attacker can
then infer the next tokens to come from the system and reset victims'
passwords using those token links. Remediation Use a modern framework's
implementation of token generation. Never build your own. Failure to
Expire Reset Tokens Once a password reset token has been used it needs
to be rendered inactive within the system. We often find web
applications here at FoD that allow the user (or anyone with the link)
to continue resetting the password after it's already been reset once.
This is especially true because reset tokens are usually sent via email,
which often traverses the Internet unencrypted. For high security
websites you should consider an additional security measure: Notifying
the user if someone attempts to reuse the token. This can alert the user
to a potential compromise of their email account or some other type of
compromise of their security. Finally, if the password reset token is
not used within a certain amount of time it should expire. This period
of time should depend on the security level of the website, but between
10 and 90 minutes is fairly common. Remediation Ensure that reset tokens
are rendered invalid as soon as they are used, and for high security
sites consider alerting the user and possibly the security administation
team if there is an attempt to reuse one. Expire tokens that are not
used. Auto-logon After Reset Finally, after the user has successfully
reset her password, ensure that she's forced to return to the standard
login screen and authenticate with the new credentials. We see many
implementations that, upon the user completing their reset, simply drop
the user right into an authenticated session. This provides additional
surface area for attack of your authentication system (via logic attacks
errors and other methods) and should be avoided. Another reason to avoid
this is that all logins (attempted and successful) to your application
should be logged, and a backdoor into the app (without going through the
primary auth page) could leave a blind spot in your audit logs.
Remediation Ensure that all users are required to use the primary
authentication page after resetting their credentials. Don't allow any
backdoor entry through the password reset mechanism. Best Practices
Review Ok, so let's hit the main points again all in one place: Use
cryptographically strong password reset tokensExpire those tokens after
a successful useExpire tokens after 10-90 minutes--depending on the
security of the siteAlways reset the password on the website itself
rather than emailing the user a new oneEnsure you use HTTPS on the page
where you have users reset their passwordsDetect (and potentially
respond to) attempts to reuse reset tokenForce the user to explicitly
log in via the standard mechanism using their new credentials after the
password reset process has completed Conclusion Keep in mind this isn’t
a complete guide to security issues related to password reset
mechanisms, but it should get you thinking about some of the main errors
to avoid. Also be sure to come back for the next installment where we'll
cover Authentication Vulnerabilities. As always, feel free to reach out
with any questions via Twitter (@danielmiessler) or via email
(daniel.miessler@hp.com). hp.com/go/fortifyondemand : : Daniel Miessler
is a Practice Principal with Fortify on Demand based out of San
Francisco, California. His areas of expertise are web and mobile
application security testing and building application security programs
for the Global and Fortune 100. He can be reached at
daniel.miessler@hp.com and on Twitter at @danielmiessler.
No comment yet.
Scooped by Srdjan Strbanovic
February 12, 2014 1:12 PM
Scoop.it!

WebRTC data channels: WebRTC data channels for high performance data exchange - HTML5 Rocks

WebRTC data channels: WebRTC data channels for high performance data exchange - HTML5 Rocks | nodeJS and Web APIs | Scoop.it
WebRTC data channels for high performance data exchange
No comment yet.
Scooped by Srdjan Strbanovic
February 11, 2014 12:13 PM
Scoop.it!

Replacing callbacks with ES6 Generators

Replacing callbacks with ES6 Generators | nodeJS and Web APIs | Scoop.it
No comment yet.