Collaborate Disseminate
Shielding is crucial for all manner of electronic devices. Whether you want to keep power supply noise out of an audio amplifier, or protect ICBMs against an electromagnetic pulse from …read more Continue reading MXenes Make Faraday Cages You Can Turn On And Off
Science today seems to be dominated by big budgets and exotics supplies and materials, the likes of which the home gamer has trouble procuring. But back in the day, science …read more Continue reading Reviving Old Recipe for Faraday Wax Keeps Vacuum Experiments Going
On this special edition of the podcast we speak with Aaron Zar, co-founder and CEO of Silent Pocket. Silent Pocket has been a long time sponsor of the show and it was great to catch up with Aaron to get his thoughts on the current state of digital priv… Continue reading Aaron Zar, Co-Founder and CEO of Silent Pocket
When you think of who invented the induction motor, Nikola Tesla and Galileo Ferraris should come to mind. Though that could be a case of the squeaky wheel being the one that gets the grease. Those two were the ones who fought it out just when the infrastructure for these motors was being developed. Then again, Tesla played a huge part in inventing much of the technology behind that infrastructure.
Although they claimed to have invented it independently, nothing’s ever invented in a vacuum, and there was an interesting progression of both little guys and giants that came before them; …read more
Electric current comes in many forms: current in a wire, flow of ions between the plates of a battery and between plates during electrolysis, as arcs, sparks, and so on. However, here on Hackaday we mostly deal with the current in a wire. But which way does that current flow in that wire? There are two possibilities depending on whether you’re thinking in terms of electron current or conventional current.
In a circuit connected to a battery, the electrons are the charge carrier and flow from the battery’s negative terminal, around the circuit and back to the positive terminal.
Conventional …read more
As a hacker, chances are that you have built a homopolar motor, as you only need three things: a battery, a magnet and some copper wire. There are zillions of videos on YouTube. This time we want to show you [Electric Experiments Roobert33]´s version. Definitely a fresh twist on the ubiquitous design that you see everywhere. His design is a bit more complicated, but the result makes the effort worthwhile.
The homopolar motor was the first electric motor ever built. Created Michael Faraday in 1821, it works because of the Lorentz force. This force acts on any current-carrying conductor that …read more
Toolsmith first covered Faraday in March 2015 with Faraday IPE – When Tinfoil Won’t Work for Pentesting. As it’s just hit its 2.0 release milestone, I’m reprinting Francisco Amato’s announcement regarding Faraday 2.0 as sent via securityfocus.com to the webappsec mailing list.
“Faraday is the Integrated Multiuser Risk Environment you were looking
for! It maps and leverages all the knowledge you generate in real
time, letting you track and understand your audits. Our dashboard for
CISOs and managers uncovers the impact and risk being assessed by the
audit in real-time without the need for a single email. Developed with
a specialized set of functionalities that help users improve their own
work, the main purpose is to re-use the available tools in the
community taking advantage of them in a collaborative way! Check out
the Faraday project in Github.
Two years ago we published our first community version consisting
mainly of what we now know as the Faraday Client and a very basic Web
UI. Over the years we introduced some pretty radical changes, but
nothing like what you are about to see – we believe this is a turning
point for the platform, and we are more than happy to share it with
all of you. Without further ado we would like to introduce you to
Faraday 2.0!
https://github.com/infobyte/faraday/releases/tag/v2.0
This release, presented at Black Hat Arsenal 2016, spins around our
four main goals for this year:
* Faraday Server – a fundamental pillar for Faraday’s future. Some of
the latest features in Faraday required a server that could step
between the client and CouchDB, so we implemented one! It still
supports a small amount of operations but it was built thinking about
performance. Which brings us to objective #2…
* Better performance – Faraday will now scale as you see fit. The new
server allows to have huge workspaces without a performance slowdown.
200k hosts? No problem!
* Deprecate QT3 – the QT3 interface has been completely erased, while
the GTK one presented some versions ago will be the default interface
from now on. This means no more problems with QT3 non-standard
packages, smooth OSX support and a lighter Faraday Client for
everyone.
* Licenses – managing a lot of products is time consuming. As you may
already know we’ve launched Faraday’s own App Store
https://appstore.faradaysec.com/ where you can get all of your
favourite tools (Burp suite, IDA Debugger, etc) whether they’re open
source or commercial ones. But also, in order to keep your licenses up
to date and never miss an expiry date we’ve built a Licenses Manager
inside Faraday. Our platform now stores the licenses of third party
products so you can easily keep track of your licenses while
monitoring your pentest.
With this new release we can proudly say we already met all of this
year’s objectives, so now we have more than four months to polish the
details. Some of the features released in this version are quite
basic, and we plan to extend them in the next few iterations.
Changes:
* Improved executive report generation performance.
* Totally removed QT3, GTK is now the only GUI.
* Added Faraday Server.
* Added some basic APIs to Faraday Server.
* Deprecated FileSystem databases: now Faraday works exclusively with
Faraday Server and CouchDB.
* Improved performance in web UI.
* Added licenses management section in web UI.
* Fixed bug when deleting objects from Faraday Web.
* Fixed bug when editing services in the web UI.
* Fixed bug where icons were not copied to the correct directory on
initialization.
* Added a button to go to the Faraday Web directly from GTK.
* Fixed bug where current workspace wouldn’t correspond to selected
workspace on the sidebar on GTK.
* Fixed bug in ‘Refresh Workspace’ button on GTK.
* Fixed bug when searching for a non-existent workspace in GTK.
* Fixed bug where Host Sidebar and Status Bar information wasn’t
correctly updated on GTK.
* Fixed sqlmap plugin.
* Fixed metasploit plugin.
We hope you enjoy it, and let us know if you have any questions or comments.”
https://www.faradaysec.com
https://github.com/infobyte/faraday
https://twitter.com/faradaysec
Toolsmith first covered Faraday in March 2015 with Faraday IPE – When Tinfoil Won’t Work for Pentesting. As it’s just hit its 2.0 release milestone, I’m reprinting Francisco Amato’s announcement regarding Faraday 2.0 as sent via securityfocus.com to the webappsec mailing list.
“Faraday is the Integrated Multiuser Risk Environment you were looking
for! It maps and leverages all the knowledge you generate in real
time, letting you track and understand your audits. Our dashboard for
CISOs and managers uncovers the impact and risk being assessed by the
audit in real-time without the need for a single email. Developed with
a specialized set of functionalities that help users improve their own
work, the main purpose is to re-use the available tools in the
community taking advantage of them in a collaborative way! Check out
the Faraday project in Github.
Two years ago we published our first community version consisting
mainly of what we now know as the Faraday Client and a very basic Web
UI. Over the years we introduced some pretty radical changes, but
nothing like what you are about to see – we believe this is a turning
point for the platform, and we are more than happy to share it with
all of you. Without further ado we would like to introduce you to
Faraday 2.0!
https://github.com/infobyte/faraday/releases/tag/v2.0
This release, presented at Black Hat Arsenal 2016, spins around our
four main goals for this year:
* Faraday Server – a fundamental pillar for Faraday’s future. Some of
the latest features in Faraday required a server that could step
between the client and CouchDB, so we implemented one! It still
supports a small amount of operations but it was built thinking about
performance. Which brings us to objective #2…
* Better performance – Faraday will now scale as you see fit. The new
server allows to have huge workspaces without a performance slowdown.
200k hosts? No problem!
* Deprecate QT3 – the QT3 interface has been completely erased, while
the GTK one presented some versions ago will be the default interface
from now on. This means no more problems with QT3 non-standard
packages, smooth OSX support and a lighter Faraday Client for
everyone.
* Licenses – managing a lot of products is time consuming. As you may
already know we’ve launched Faraday’s own App Store
https://appstore.faradaysec.com/ where you can get all of your
favourite tools (Burp suite, IDA Debugger, etc) whether they’re open
source or commercial ones. But also, in order to keep your licenses up
to date and never miss an expiry date we’ve built a Licenses Manager
inside Faraday. Our platform now stores the licenses of third party
products so you can easily keep track of your licenses while
monitoring your pentest.
With this new release we can proudly say we already met all of this
year’s objectives, so now we have more than four months to polish the
details. Some of the features released in this version are quite
basic, and we plan to extend them in the next few iterations.
Changes:
* Improved executive report generation performance.
* Totally removed QT3, GTK is now the only GUI.
* Added Faraday Server.
* Added some basic APIs to Faraday Server.
* Deprecated FileSystem databases: now Faraday works exclusively with
Faraday Server and CouchDB.
* Improved performance in web UI.
* Added licenses management section in web UI.
* Fixed bug when deleting objects from Faraday Web.
* Fixed bug when editing services in the web UI.
* Fixed bug where icons were not copied to the correct directory on
initialization.
* Added a button to go to the Faraday Web directly from GTK.
* Fixed bug where current workspace wouldn’t correspond to selected
workspace on the sidebar on GTK.
* Fixed bug in ‘Refresh Workspace’ button on GTK.
* Fixed bug when searching for a non-existent workspace in GTK.
* Fixed bug where Host Sidebar and Status Bar information wasn’t
correctly updated on GTK.
* Fixed sqlmap plugin.
* Fixed metasploit plugin.
We hope you enjoy it, and let us know if you have any questions or comments.”
https://www.faradaysec.com
https://github.com/infobyte/faraday
https://twitter.com/faradaysec
The history of capacitors starts in the pioneering days of electricity. I liken it to the pioneering days of aviation when you made your own planes out of wood and canvas and struggled to leap into the air, not understanding enough about aerodynamics to know how to stay there. Electricity had a similar period. At the time of the discovery of the capacitor our understanding was so primitive that electricity was thought to be a fluid and that it came in two forms, vitreous electricity and resinous electricity. As you’ll see below, it was during the capacitor’s early years that …read more
Continue reading History of the Capacitor – The Pioneering Years
Beginning in 1827, [Michael Faraday] began giving a series of public lectures at Christmas on various subjects. The “Christmas Lectures” continued for 19 years and became wildly popular with upper-class Londoners. [Bill Hammack], aka [The Engineer Guy], has taken on the task of presenting [Faraday]’s famous 1848 “The Chemical History of a Candle” lecture in a five-part video series that is a real treat.
We’ve only gotten through the first episode so far, but we really enjoyed it. The well-produced lectures are crisply delivered and filled with simple demonstrations that drive the main points home. [Bill] delivers more or less …read more
