token – Jupiter Broadcasting https://www.jupiterbroadcasting.com Open Source Entertainment, on Demand. Mon, 22 Feb 2016 02:49:00 +0000 en-US hourly 1 https://wordpress.org/?v=5.5.3 https://original.jupiterbroadcasting.net/wp-content/uploads/2019/04/cropped-favicon-32x32.png token – Jupiter Broadcasting https://www.jupiterbroadcasting.com 32 32 Corrupt Internet Police | TechSNAP 140 https://original.jupiterbroadcasting.net/47922/corrupt-internet-police-techsnap-140/ Thu, 12 Dec 2013 18:36:38 +0000 https://original.jupiterbroadcasting.net/?p=47922 Well tell you about the perfect crime, that’s Cloud enabled, the NSA gets caught with Google's cookies, and a new breed of corrupt Internet police.

The post Corrupt Internet Police | TechSNAP 140 first appeared on Jupiter Broadcasting.

]]>

post thumbnail

The perfect crime, that’s Cloud enabled. The NSA gets caught with Google\’s cookies, and a new breed of corrupt Internet police.

Plus a fantastic batch of your questions, our answers, and much much more!

Thanks to:


\"GoDaddy\"


\"Ting\"


\"iXsystems\"

Direct Download:

HD Video | Mobile Video | MP3 Audio | Ogg Audio | YouTube | HD Torrent | Mobile Torrent

RSS Feeds:

HD Video Feed | Mobile Video Feed | MP3 Audio Feed | Ogg Audio Feed | iTunes Feeds | Torrent Feed

Flaw in Microsoft Office 365 allows ‘perfect crime’

  • The researchers who discovered the attack are calling it the ‘Ice Dagger’, because it left behind almost no evidence and it took months of effort by researchers and Microsoft’s Security Response Team to discover what had happened
  • in April 2013, a customer’s nodes analyzed an HTTP request that triggered a “high risk” heuristics alert
  • The request was for an MS Word document hosted on a TOR Hidden Service node (onion.to address)
  • In this case, the request to the TOR service was not made by the user, but by MS Word it self, this elevated the incident to extremely suspicious
  • “Upon reviewing the metadata of the request, we noticed that its response had a WWW-Authenticate header with RootDomain=”sharepoint.com”, even though the request obviously wasn’t for a sharepoint.com domain. At this point we started assessing the situation and treating it as a potential data theft”
  • The end user had received an email specifically addressed to them containing a link to an MS Word document hosted on the TOR Hidden service, a very specific spear phishing attack
  • When the user opened the link, it fired off the MS Office365 URL handler, ms-word:// and MS Word opened the document
  • Due to a bug in MS Word, when the malicious web server sent the same WWW-Authenticate header that Office365 would have sent, MS Word sent the user’s private SharePoint access token back to the malicious web server, even though it should only ever send that token to sharepoint.com
  • With this token, an attacker can access every document in the Office365 environment, including SharePoint and SkyDrive, completely undetected
  • The attacker can copy all of the documents and then delete them, or make subtle modifications that could prove disastrous
  • The attack comes down to a few simple steps:
  • You get a mail asking you to review a document or visit a webpage. Some ideas: Maybe a document with coupons? Someone’s CV? A price quote? A contract? Obviously at least one employee out of hundreds will read the document.
  • You click on the link. The web page asks you to open the document in Word, just like SharePoint Online asks you (shown in step 2 above). Because this dialog is so common when using SharePoint Online, it’s really hard to believe anyone will refuse the request.
  • Word is now requesting the document from the malicious webpage. The malicious webpage asks Word for its Office 365 token and Word willingly gives it. The malicious webpage gives Word a legitimate-looking document in return.
  • The attacker now has your Office 365 token. You have a document which you will shrug off as meaningless and go on with your day.
  • The researchers provided their completed research to Microsoft on May 29th, 2013
  • The patch has finally been released as part of the December Patch Tuesday MS13-104 fixes CVE-2013-5054
  • Conclusions: This was A Perfect Crime. “There was no malware payload to reverse-engineer. No file hash we can trace through time. No IP address to locate and investigate. No servers to confiscate. The attacker simply gets away with your Office 365 token. For good. This is important in the context of understanding the limitations of your existing endpoint and perimeter defenses in the context of SaaS applications and cloud services.”
  • Microsoft also patched a WinVerifyTrust signature validation vulnerability in Windows that can be used to disguise malicious applications as trustworthy, signed executables. \”Exploits targeting this vulnerability have been seen in the wild, so deploy this patch as soon as possible\”
  • Additional Coverage: BetaNews
  • Additional Coverage: Network World
  • Additional Coverage: Information Week
  • Additional Coverage: SC Magazine
  • Additional Coverage: Softpedia

NSA using Google cookies to pinpoint targets for attack

  • The agency\’s internal presentation slides, provided by former NSA contractor Edward Snowden, show that when companies follow consumers on the Internet to better serve them advertising, the technique opens the door for similar tracking by the government
  • The slides also suggest that the agency is using these tracking techniques to help identify targets for offensive hacking operations.
  • According to the documents, the NSA and its British counterpart, GCHQ, are using the small tracking files or \”cookies\” that advertising networks place on computers to identify people browsing the Internet.
  • The intelligence agencies have found particular use for a part of a Google-specific tracking mechanism known as the “PREF” cookie.
  • These cookies typically don\’t contain personal information, such as someone\’s name or e-mail address, but they do contain numeric codes that enable Web sites to uniquely identify a person\’s browser.
  • This cookie allows NSA to single out an individual\’s communications among the sea of Internet data in order to send out software that can hack that person\’s computer. The slides say the cookies are used to \”enable remote exploitation,\”
  • Separately, the NSA is also using commercially gathered information to help it locate mobile devices around the world, the documents show.
  • These specific slides do not indicate how the NSA obtains Google PREF cookies or whether the company cooperates in these programs, but other documents reviewed by the Post indicate that cookie information is among the data NSA can obtain with a Foreign Intelligence Surveillance Act order. If the NSA gets the data that way, the companies know and are legally compelled to assist.
  • Google assigns a unique PREF cookie anytime someone\’s browser makes a connection to any of the company\’s Web properties or services. This can occur when consumers directly use Google services such as Search or Maps, or when they visit Web sites that contain embedded \”widgets\” for the company\’s social media platform Google Plus. That cookie contains a code that allows Google to uniquely track users to \”personalize ads\” and measure how they use other Google products.
  • Another slide indicates that the NSA is collecting location data transmitted by mobile apps to support ad-targeting efforts in bulk. The NSA program, code-named HAPPYFOOT, helps the NSA to map Internet addresses to physical locations more precisely than is possible with traditional Internet geolocation services.

British “Police Intellectual Property Crime Unit” attempts to censor the global Internet

  • We have covered a bit of this story in the past, but it seems to be getting worse, and we have a lot more detail now
  • “Today, a special police unit can decide that a certain website needs to disappear from the Internet, and threaten its domain name registrar into revoking the address “until further notice”, without any legal basis whatsoever.”
  • The PIPCU is claiming success in it’s Operation Creative, a three month campaign where they improperly seized the 40 domains they accused of copyright infringement. Some of the sites were shut down, while some simply moved to a different domain
  • The owners of the 40 domains, nor their registrars or web hosts were ever served with a court order
  • How the PIPCU works:
  • Investigators who work at notorious copyright trolls such as BPI (British Phonographic Industry) and FACT (Federation Against Copyright Theft) scour the Internet, looking for websites that share copyrighted content
  • They then forward this ‘intelligence’ to the PIPCU, which then decides whether or not it will attempt to take down the site.
  • The PIPCU will ask a network of over 60 advertisers to stop placing banners and bankrolling a pirate resource
  • Finally, after a certain period of time, the PIPCU will send a letter to the site’s registrar, asking it to suspend the domain name. Instead of a court order, this peculiar document refers to an outdated section of ICANN’s Registrar Accreditation Agreement, which states that such accreditation can be terminated if the organisation is found to have ‘permitted illegal activity in the registration or use of domain names’.
  • This scare tactic causes many registrars to suspend the domains, rather than risking their entire business by losing their ability to register new domains
  • One registrar has decided to stick up for its users, and the rest of the internet
  • EasyDNS posted the notice on their blog
  • Specifically “We have an obligation to our customers and we are bound by our Registrar Accreditation Agreements not to make arbitrary changes to our customers settings without a valid FOA (Form of Authorization). To supersede that we need a legal basis. To get a legal basis something has to happen in court”
  • Registrars are not ALLOWED to seize a domain without a legal basis. Registrars that complied with the shakedown may actually be in violation of ICANN policies
  • One customer who had their domain seized at another registrar then attempted to move to EasyDNS, however the ‘losing’ registrar, in violation of ICANN policy’, refused to release the domain
  • So EasyDNS requested that Verisign, the operators of the .com and .net registries, make a ruling and release the domain. However Verisign rendered a decision of ‘no decision’
  • Verisign’s reason for no decision? The losing registrar did not provide the requested documentation
  • EasyDNS has appealed the decision with ICANN and we are watching for further developments

Feedback:

3 days 4 hours left to buy


Round Up:


The post Corrupt Internet Police | TechSNAP 140 first appeared on Jupiter Broadcasting.

]]>
Phishin’ Hole | TechSNAP 113 https://original.jupiterbroadcasting.net/38381/phishin-hole-techsnap-113/ Thu, 06 Jun 2013 16:23:54 +0000 https://original.jupiterbroadcasting.net/?p=38381 We’ll go inside some clever bank malware, a dedicated server provider our very own Allan uses discovers a backdoor... Plus picking the right VM storage.

The post Phishin' Hole | TechSNAP 113 first appeared on Jupiter Broadcasting.

]]>

post thumbnail

We’ll go inside some clever bank malware, a dedicated server provider our very own Allan uses discovers a backdoor…

Plus: Picking the right virtual machine storage, a big batch of your questions, and much much more!

Thanks to:

Use our code tech249 to score .COM for $2.49!

32% off your ENTIRE first order just use our code go32off3 until the end of the month!

 

Direct Download:

HD Video | Mobile Video | MP3 Audio | Ogg Audio | YouTube | HD Torrent | Mobile Torrent

RSS Feeds:

HD Video Feed | Mobile Video Feed | MP3 Audio Feed | Ogg Audio Feed | iTunes Feeds | Torrent Feed

 

Support the Show:

   

Show Notes:

Get TechSNAP on your Android:

Browser Affiliate Extension:

 

Direct Download:

HD Video | Mobile Video | MP3 Audio | Ogg Audio | YouTube | HD Torrent | Mobile Torrent

RSS Feeds:

HD Video Feed | Mobile Video Feed | MP3 Audio Feed | Ogg Audio Feed | iTunes Feeds | Torrent Feed

 

Support the Show:

   

Show Notes:

Get TechSNAP on your Android:

Browser Affiliate Extension:

  • Jupiter Broadcasting Affiliate Extensions for Chrome and Firefox
  • Why a password isn’t good enough anymore

    • An article by Mat Honan, the Wired writer who had his entire online existence destroyed earlier this year
    • An attacker wanted to steal the twitter handle @mat, and so started by trying to do a password reset on twitter.
    • This directed the attacker to Mat’s gmail account
    • When trying to initiate a password reset set on the gmail account, he was directed to Mat’s Apple account
    • The attacker called Apple and using information about Mat from Twitter, Facebook, Google etc, he managed to reset the password for Mat’s Apple account
    • Using the Apple account, the attacker was able to disable and remotely wipe Mat’s Apple devices (iPhone, iPad and Macbook)
    • Once the attacker was in control of the Apple account, he was able to reset the password for the Gmail account
    • Then to reset the password for the Twitter account
    • Watch TechSNAP 70 for the full story
    • In this followup article we get an even closer look at what happened, and an in-depth analysis of other recent happenings
    • A lot of the problems discussed in the article are not weaknesses in passwords specifically, but in the people and systems that use them
    • Authentication Bypass – When an attacker finds a way to access an account or service without needing the password at all. We have seen this with Dropbox, Oracle and others in past episodes of TechSNAP, or the recent case with Skype, where it failed to properly authenticate you before allowing you to reset account, we’ll cover that later in this episode.
    • Brute Force – Accounts for services like POP3, FTP, SSH, and SIP are under constant attack, all day, every day. Attackers attempt to compromise the accounts in order to gain access for various reasons, from using the initial password as a stepping stone to gain access to more sensitive accounts, to using your machine to scan for yet more weak passwords, or as a source of spam. Attackers are constantly attempting common username and password combinations against every public facing server on the internet, using apps such as DenyHosts, Fail2Ban or SSHGuard to protect these servers is a must.
    • Database Compromise – Services such as Sony PSN, Gawker, LinkedIn, Yahoo, eHarmony, LastFM and others had their databases compromised, and their lists of passwords dumped online. Often these passwords were hashed (MD5, SHA1, SHA256), but not always. Even a hashed password is little protection, it doesn’t immediately disclose your password, but with tools like Rainbow Tables and GPU accelerated cracking, these hashes were quickly cracked and the plain text passwords posted online. Hopefully more services will start using properly secure Cryptographic Hashes (sha512crypt, bcrypt) that take tens of thousands of times more computational power for each attempt to crack a password. Some algorithms like bcrypt are also, thus far, immune to GPU acceleration, actually taking longer on a GPU than a CPU.
    • Disclosure – People often share their passwords, I don’t know how many facebook accounts have been ‘hacked’ by friends or ex’s because you willingly gave them your password, or you gave them the password to something else, and they used one of the other techniques described here to gain access to something you didn’t mean for them to have access to.
    • Eavesdropping – Someone could be listening on the wire (or in the air in the case of wireless or mobile data connections) and see your password as it goes between your computer and the remote service. Most services now login over SSL to prevent this, but older services such as FTP (still very popular for web hosting, where your password may be shared with the web hosting control panel that has access to reset your email password) are not encrypted.
    • Exposure – This is when you accidently give away your password, it happens on IRC at least once a week, someone attempts to enter the command to identify, but prefixes it with a space or something and ends up displaying their password to the entire chat room. Users will also sometimes accidentally enter their password in the username field, or their credit card number in the field that is for the ‘name as it appears on the card’, which causes it not to be treated with the same level of security.
    • Guessing and Inference – When people base their password on birthdays or pet’s names, they become easy to guess. If you compile a largish list of keywords about a person, including bands and songs they like, their family and friends names, important dates, sports teams etc, and run it through an app like John The Ripper, which will make variations of those passwords, including l33t speak transformations, adding numbers and symbols, are are likely to get a fairly high success rate. In addition to guessing, there is inference, if you know that Bob’s password for gmail is: bobisgreat@gmail then you can probably guess that his password for facebook is: bobisgreat@facebook. If there is a pattern or ‘system’ to your passwords, once someone compromises ONE of those passwords, they have a much greater chance of compromising them all.
    • Key Logging – When an attacker, using hardware or software, is able to record the keys you type in your keyboard, thus capturing your password as you input it. Apps like LastPass may seem to help with this, but they usually use an OS API to simulate typing the keys to remain compatible with all applications. Clipboard scanners can also often catch passwords.
    • Man-in-the-Middle – An attack that intercepts your traffic and pretends to be the service you are trying to connect to, allowing it to capture your password, even if it was encrypted. SSL/TLS was designed to prevent Man-in-the-Middle attacks by verifying the identity of the remote server, however with Certificate Authority being compromised and issuing false certificates and tools such as SSLStrip to trick you into not using SSL, it is still possible for your communications to be intercepted.
    • Phishing – Emails meant to look like they are from an official source, whether is be eBay, PayPal or your bank, prompt you to login on a page that looks like the legitimate one, but is not. Once you enter your details, the attackers have all they need to know to compromise your real account. Combine this with the weak DKIM keys from a few weeks ago, a compromised Certificate Authority and a man-in-the-middle DNS attack, and you have no way of knowing that when you entered https://www.paypal.com in to your browser, you actually ended up on an attackers site instead.
    • Reply Attack – When an attacker is able to capture you authenticating in some secure manner, but is able to resend that same information and authenticate as you later, without ever knowing your password
    • Reuse – Using the same password on multiple sites means that when one of them is compromised, they all are. I keep telling you, use lastpass.
      • Secret Questions – So, when you setup that new account and it prompts you for some secret questions/answers, consider carefully what you put down. You’re going to need to be able to remember it later to regain access to the account (or some accounts ask them when they suspect you are logging in from a different computer), but if they are simple ones that someone could look up via google or facebook (remember, the attacker could be someone you know, so your privacy settings on facebook might not be enough), then it isn’t good enough.
      • Social Engineering – In the case of the Mat Honan compromise, the weakest link turned out to be AppleCare Support, they very much wanted to be helpful and allow him to recover his accounts, the only problem was, the caller was not Mat Honan, but the attacker, to managed to guess and trick his way through the security questions and gain control of the Apple and Amazon accounts.
      • See some old Blog post by Allan for more reading at [GeekRoundTable] ](https://www.geekrt.com/read/88/Myths-of-Password-Security/) and AppFail
    • These issues are endemic across the entire internet, and it is important that you be aware of them and take steps to protect yourself as best you can
    • A comparison of two major password dumps has shown that half of all passwords were used on both sites, the problem of password reuse is growing rather than shrinking
    • Having a long and strong password is important, but you have to consider the other ways someone could compromise your account, the weakest link is the most likely avenue of attack
    • If you have the option, you should enable two-factor authentication, adding one more step makes the attackers job that much harder, but remember, this doesn’t mean you are immune, RSA and Blizzard authenticators have been compromised in the past when their seed values were stolen from the central databases.

    Skype IDs hijackable by anyone who knows your email address

    • An attacker found a way to bypass the authentication in skype’s password reset system, and take over any target account for which the email address was known
    • The Instructions
    • Register for a new account, using the email address of the victim
    • Login to Skype using that new account
    • Initiate a password reset for the victim’s account
    • Skype will email the victim a password reset token, but the token will also pop up in the skype client for all accounts that use that email address, allowing the attacker to get the token
    • Use the token to reset the password of the victim account
    • Login to the victim’s account and remove their email address and add your own (one that no one knows) and you now own that account
    • Skype disabled the password reset system a few hours later, then fixed the issue and re-enabled the password reset system. Tokens are no longer displayed in logged-in skype clients. This makes sense, and I question why it was ever the other way around, because if you are logged in, you are unlikely to have forgotten your password (unless it was saved I guess).
    • Skype’s Reaction
    • NextWeb Coverage
    • NextWeb Followup

    Feedback:

    Round Up:

    The post Patch Your Password | TechSNAP 84 first appeared on Jupiter Broadcasting.

    ]]> We Lied About the Title | CR 23 https://original.jupiterbroadcasting.net/27346/we-lied-about-the-title-cr-23/ Mon, 12 Nov 2012 12:44:21 +0000 https://original.jupiterbroadcasting.net/?p=27346 Mike and Chris discuss if sticking to the same job makes you utterly irrelevant, or uniquely positioned for future challenges, the twitter has dropped, and we tackle the topic that was too hot for The Linux Action Show!

    The post We Lied About the Title | CR 23 first appeared on Jupiter Broadcasting.

    ]]>

    post thumbnail

    Mike and Chris discuss if sticking to the same job makes you utterly irrelevant, or uniquely positioned for future challenges, the twitter hammer has dropped, and we tackle the topic that was too hot for The Linux Action Show!

    Plus some great feedback, the great Orca meltdown, more thoughts on the Ubuntu SDK, and the flexibility of Python!

    Direct Download:

    MP3 Audio | OGG Audio | Video | Torrent | YouTube

    RSS Feeds:

    MP3 Feed | OGG Feed | Video Feed | Torrent Feed | iTunes Audio | iTunes Video

    Show Notes:

    Feedback

    This Week’s Dev World Hoopla

    Book of the Week

    [asa]0321623215[/asa]

    Follow the show

    The post We Lied About the Title | CR 23 first appeared on Jupiter Broadcasting.

    ]]>
    SQL Injections | TechSNAP 40 https://original.jupiterbroadcasting.net/15661/sql-injections-techsnap-40/ Thu, 12 Jan 2012 18:53:27 +0000 https://original.jupiterbroadcasting.net/?p=15661 We’ll explain how SQL Injections work, plus cover tools you can use to passively discover details about everyone connected to your network.

    The post SQL Injections | TechSNAP 40 first appeared on Jupiter Broadcasting.

    ]]>

    post thumbnail

    We’ll explain how SQL Injections work, plus cover tools you can use to passively discover details about everyone connected to your network.

    And Adobe blames some researches for THEIR security mistakes, we’ll explain.

    All that and more, on this week’s episode of TechSNAP!

       

    Direct Download Links:

       

    HD Video | Large Video | Mobile Video | MP3 Audio | OGG Audio | YouTube

     

       
    Subscribe via RSS and iTunes:

    Show Notes:

    Thanks to:

    GoDaddy.com Use our codes TechSNAP10 to save 10% at checkout, or TechSNAP20 to save 20% on hosting!

    Pick your code and save:
    techsnap7: $7.99 .com
    techsnap10: 10% off
    techsnap20: 20% off 1, 2, 3 year hosting plans
    techsnap40: $10 off $40
    techsnap25: 25% off new Virtual DataCenter plans

    Zero day Adobe Reader vulnerability uses to target defense contractors

    • An extremely targeted attack was carried out against major players in the defense industry using a previously unknown zero-day vulnerability in Adobe Reader
    • Only 20 or so machines were targeted, spread across a number of different companies
    • Specially crafted .PDF files that exploited the vulnerability to execute code on the victim’s machine were sent to a very specific list of email addresses, rather than the typical spam of phishing style attack. This was likely meant to prevent the zero day vulnerability from being discovered so it could continue to be used
    • The payload of the exploit was the Sykipot Trojan
    • From analysis of the exploit , it appears to be based on previous research and a proof of concept released by Felipe Andreas Manzano in 2009
    • Adobe made a point of reminding security researchers that their publicly disclosed proof of concepts are often used as free R&D by cyber criminals. TechSNAP would like to remind Adobe that the point of publicly disclosing the research is free R&D to help/force Adobe to patch the vulnerabilities
    • The vulnerability was apparently reported to Adobe by Lockheed Martin after they discovered they had been compromised
    • Adobe announced the vulnerability on December 6th, and released the patch on January 10th
    • Previous TechSNAP Coverage
    • CVE Announcement

    New version of the P0f network finger printing tool

    • The tool passively analyzes incoming network transmissions and determines the operating system and other information about the remote machine with a fairly high degree of accuracy
    • The feature of note with the newly rewritten version is that it can detect many types of forgery, alerting you when the remote machine is who what it claims to be
    • The tool also features the ability to analyze some application layer protocols such as HTTP
    • One of the features I the ability to detect user agent forging (spam bots pretending to be running firefox or MSIE)
    • It is also able to detect some other aspects of the connection, such as NAT, load balancing, PPPoE (common for DSL), VPNs, Transparent and other irregular Proxies, and even tor
    • This tool could be very useful for fraud screening purposes, ecommerce sites can detect when the user is attempting to mask their identity and flag the orders for additional investigation
    • This tool could also be used as part of a firewall or man-in-the-middle attack, to detect technologies such as VPNs and block them, in an effort to have users connect without the additional security so they can be spied upon

    Verizon Business Consulting analyzes second wave attacks against RSA customers

    • Typical attacks using email spear-phishing to attempt to place trojans and keyloggers on machines of SecurID users
    • The objective is to log the username, password and the temporary PIN generated by the SecurID Token
    • Once a small number of these PINs are obtained, the attackers may be able to successfully clone the SecureID Token to generate valid PINs at will, allowing them to compromise the targets easily
    • The unconfirmed list of companies who have been targeted includes: Lockheed Martin, Northrop Grumman, The International Monetary Fund, and L–3 Communications
    • RSA continues to claim that the security of the SecurID tokens has not been compromised, but after being subjected to much pressure by customers, has agreed to replace the tokens of any customers who request it

    Feedback:

    Q: (EBeyer) You talk about it a lot on the show, and it is one of the most common security vulnerabilities on the web, but what is SQL Injection?

    A: An SQL Injection attack is caused by careless coding during the construction of an application that uses an SQL database. Through some fault or other, the attacker is able to “inject” code in to the SQL statement.

    The most classic example of this comes from this very poor example of a login script:

    SELECT * FROM users WHERE username = ‘$username’ AND password = ‘$password’

    During normal operations, which would work as expected. However, if someone were to attempt to login with a username of say, “allan’ –” the executed SQL query would be:

    SELECT * FROM users WHERE username = ‘allan’ –‘ AND password = ‘$password’

    Where – is the SQL comment indicator, causing the rest of the query to be ignored. This would allow someone to login as any user without knowing the users password

    A further example, they could use the username “‘; DROP TABLE users; –”

    Causing the resultant SQL query to be:

    SELECT * FROM users WHERE username = ‘’; DROP TABLE users; –’ AND password = ‘$password’

    Which would find 0 users, then delete the entire users database table.

    That is why it is important to ‘sanitize inputs’. What this means is that you must remove or escape characters with special meanings, so that they are not interpreted. Each programming language provides ways to do this, but amateurs and sloppy coders often forget or miss cases where input from the user is executed without being sanitized.
    PHP for example, provides a number of methods of sanitizing the input , including the mysql_escape_string() function which attempts to escape any meta characters, but does not consider the character set. It has been deprecated and should be replaced by mysql_real_escape_string() which requires an active connection to the MySQL database (required anyway if you are going to run a query), and takes the character set, database settings and server configuration in to consideration. You can also use Prepared Statements , where the SQL query is defined with the variables, and then those variables are replaced at execution time, where they are escaped properly.


    Round-Up:

    The post SQL Injections | TechSNAP 40 first appeared on Jupiter Broadcasting.

    ]]> Full Speed Ahead | STOked 102 https://original.jupiterbroadcasting.net/13562/full-speed-ahead-stoked-102/ Mon, 07 Nov 2011 20:31:37 +0000 https://original.jupiterbroadcasting.net/?p=13562 More updates and changes were rolled out to the STO free to play testers this week. Some of them have us puzzled, but some are a big win for players!

    The post Full Speed Ahead | STOked 102 first appeared on Jupiter Broadcasting.

    ]]>

    post thumbnail

    More updates and changes were rolled out to the STO free to play testers this week. Some of them have us puzzled, but some are a big win for players!

    Plus thoughts on the new Dilithium Exchange, Skill Tree changes, and an what happened to that C-Store tribble?

    Audible.com

    Ready Player One – Support STOked by buying a book or subscribing to Audible!

    Direct Download Links

    HD Video | Large Video | Mobile Video | MP3 Audio | OGG Audio | YouTube

    Subscribe via RSS and iTunes:

    Our STOked App:

    STOked App Grab the STOked iPhone/iPod App and download STOked on the go!

     

    [ad#shownotes]

    Show Notes:

    Support the show:

    Ready Player One – Support STOked by buying a book or subscribing to Audible!

    SHIPS
    • Implemented a maximum limit ship slots purchased via the C-store to 28.
    • https://forums.startrekonline.com/showthread.php?t=239380
    • Bellerophon and Gladius now on Holodeck.
    • https://forums.startrekonline.com/showthread.php?t=239458
    • StormShade says ships will remain account wide unlocks.
    • https://forums.startrekonline.com/showthread.php?p=3839727
    • Geko says ships will remain account wide unlocks & the point behind character unlocks is so they can be tradable.
    • https://forums.startrekonline.com/showthread.php?p=3840094

    • DILITHIUM EXCHANGE

    Stuff We Forgot To Talk About Last Week:

    Yay!

    • CaptainGeko posts Some important news you might want to know
    • 1) VA token added to 500 Day Vet Reward.
    • 2) Gold Members will auto-refine Dilithium for up to 1 week.
    • 3) They’re still working on the New Skill System and on Crafting.
    • https://forums.startrekonline.com/showthread.php?p=3844420

    Math:

    New Space Skills are on tribble, Nikki has been looking at them closely, toss in some little math tidbits to wet viewers apatite, and make joke at Admiral Murphy’s expense.

    Quad Cannon Controversy, Was Geko misquoted as to the Quad cannons being the highest damage cannons in the game or was he simply referring to the 3 damage modifiers on the item. Item is level-less.

    Torpedo spread, most notably Torpedo Spread 3, has being causing controversy as well.  They were targeting up to 10 enemies and now with the patch 3, 4, and 5 targets respectively.  PvPers were raging about this as it was supposedly causing 1 shot kills.

    Community Feedback:

    • Introduce revamped community feedback segment – Promo/pop community to make submissions to community feedback @ STOked@Jupiterbroadcasting.com.  We will take all questions, comments, concerns regarding STO & F2P, Cryptic, STOked and its segments (Foundry Files). Also I will promo Jupiter Force.org and my contact info Asmick@Jupiterforce.net & my twitter @Asmick_JF.

     

    The post Full Speed Ahead | STOked 102 first appeared on Jupiter Broadcasting.

    ]]>