chrome   64848

« earlier    

A node.js command line app for packing Google Chrome extensions. https://npmjs.com/crx
crx is a utility to package Google Chrome extensions via a Node API and the command line. It is written purely in JavaScript and does not require OpenSSL!
chrome  browser 
yesterday by shearichard
SafeBrowse Chrome extension found to be secretly mining for cryptocurrency
The SafeBrowse extension purports to block popup ads and skip ad pages that appear before downloads, but in fact it was secretly running a Coin Hive mining tool in the background. With over 140,000 users, SafeBrowse -- which has now been removed from the Chrome Web Store -- was quietly making an income for its developers through clandestine use of CPU time.
bitcoin  estensioni  problemi  chrome  javascript  spunti  fordjbatman 
yesterday by nicoladagostino
Attach to a manually opened Chrome browser using debuggerAddress | Testing by Justin Ko
Cool, can attach to an open Chrome browser. Though I don't necessarily see how this is much better than opening a browser with Watir first and messing with the browser then?
dev  webdriver  chrome  tidbits  blog_posts  helpful 
2 days ago by skinnymuch
Self signed certificate no longer valid as of Chrome 58 #854
It turns out that the Subject Alt Name property is missing in the certificate, resulting in Chrome that marks the certificate as insecure. The error in chrome is misleading (net::ERR_CERT_COMMON_NAME_INVALID), though according to this post it is about the Subject Alternative Name (SAN) that is missing.


refrr:https://github.com/webpack/webpack-dev-server/issues/854
It turns out that the Subject Alt Name property is missing in the certificate, resulting in Chrome that marks the certificate as insecure. The error in chrome is misleading (net::ERR_CERT_COMMON_NAME_INVALID), though according to this post it is about the Subject Alternative Name (SAN) that is missing.


refrr:https://github.com/webpack/webpack-dev-server/issues/854
It turns out that the Subject Alt Name property is missing in the certificate, resulting in Chrome that marks the certificate as insecure. The error in chrome is misleading (net::ERR_CERT_COMMON_NAME_INVALID), though according to this post it is about the Subject Alternative Name (SAN) that is missing.


refrr:https://github.com/webpack/webpack-dev-server/issues/854
chrome  dev  ssl  tls  https  environment  vagrant  openssl  devops 
2 days ago by michaelfox

« earlier    

related tags

%quora  %stack_overflow  2017  2018  a11y  accessibility  accessibilitytree  adblock  addon  advanced  algorithms  antiminer  app  article  arxiv  audio  audits  autoplay  bitcoin  block  blog_posts  bookmark  bookmarked_on_site  browser  browsers  cdn  chromebook  chromeextension  chromeextensions  code  coding  coinhive  collaboration  color  compilers  cryptocurrencies  cryptocurrency  cryptominer  cs131  cs132  css  cvim  debug  debugging  design  dev  developemtn  developer  devops  devtools  dns  docker  domain  download  edge  environment  es2015  estensioni  etsy  extension  extensions  fb  firefox  for  fordjbatman  fridayfrontend  github  golang  google  head  headless-chrome  headless  helpful  history  howto  html  https  ie  ifttt  instartlogic  interface  irritating  issues  january  javascript  key  keyboard  keys  learning  less  linux  listener  malaware  mappings  markdown  media  medium  melanto  miner  monero  mvc  node.js  on  opensource  openssl  pdf  performance  plugin  privacy  problemi  producthunt  productivity  programming  prototyping  proxy  puppeteer  readthis  remove  research  resource  resources  robotframework  rules  safari  screenshots  security  selenium  seo  shortcut  socks  spunti  ssl  starting  superusers  surfing  surfingkeys  tab  tabs  takes  tech  terminal  testing  the  tidbits  tls  todo  tool  tools  trend  tutorial  twitter  unused  used  utilities  v8  vagrant  vi  video  vim  visual  vuejs  web  web2.0  webdesign  webdev  webdevelopment  webdriver  wikipedia  will  workflows 

Copy this bookmark:



description:


tags: