sudo apt-get update fail related to cuda 9.2

I try to implement Gazebo on ubuntu 16.04, and it asks to do the command

sudo apt-get update 

However, I got the error like this:

Err:5 file:/var/cuda-repo-9-2-local  Packages                                   File not found - /var/cuda-repo-9-2-local/Packages (2: No such file or directory) Get:6 file:/var/cuda-repo-9-2-local  Translation-en_US                          Ign:6 file:/var/cuda-repo-9-2-local  Translation-en_US                          Hit:8 http://packages.ros.org/ros/ubuntu xenial InRelease                       Hit:9 http://apt.llvm.org/xenial llvm-toolchain-xenial-7 InRelease              Hit:10 http://linux.teamviewer.com/deb stable InRelease                         Ign:11 http://dl.google.com/linux/chrome/deb stable InRelease                   Hit:13 http://us.archive.ubuntu.com/ubuntu xenial InRelease                     Get:14 http://packages.osrfoundation.org/gazebo/ubuntu-stable xenial InRelease [4,264 B] Hit:15 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease             Hit:16 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease           Hit:17 http://ppa.launchpad.net/jonathonf/ffmpeg-4/ubuntu xenial InRelease      Hit:18 http://dl.google.com/linux/chrome/deb stable Release                     Get:19 http://security.ubuntu.com/ubuntu xenial-security InRelease [109 kB]     Hit:20 https://download.docker.com/linux/ubuntu xenial InRelease                Hit:21 https://packages.microsoft.com/repos/vscode stable InRelease             Hit:22 https://dl.winehq.org/wine-builds/ubuntu xenial InRelease                Hit:23 https://dl.winehq.org/wine-builds/ubuntu trusty InRelease                Hit:24 http://ppa.launchpad.net/openshot.developers/ppa/ubuntu xenial InRelease Fetched 364 kB in 12min 2s (504 B/s)                                            Reading package lists... Done W: The repository 'file:/var/cuda-repo-9-2-local  Release' does not have a Release file. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. E: Failed to fetch file:/var/cuda-repo-9-2-local/Packages  File not found - /var/cuda-repo-9-2-local/Packages (2: No such file or directory) E: Some index files failed to download. They have been ignored, or old ones used instead.` 

Anyone can help? Thanks!

Fail to connect to CloudMQTT

Got a CloudMQTT Server and I want to connect to it from C# with a client Using uPLibrary.Networking.M2Mqtt

I managed to create a client but it doesn’t connect to the server.

_client = new MqttClient(“m24.cloudmqtt.com”,10307,true,null,null,MqttSslProtocols.TLSv1_0);

_client.Connect(“id”, “someUsername”, “somePassword”);

This is the Exception i get Exception thrown: ‘uPLibrary.Networking.M2Mqtt.Exceptions.MqttConnectionException’ in M2Mqtt.Net.dll

Will ret2plt technique, where libc address is leaked by e.g. puts, not fail if the .got entry contains 0-bytes?


Will ret2plt technique, where libc address is leaked by e.g. puts, not fail if the .got entry contains 0-bytes?

In the ret2plt technique, puts is used to e.g. output its own .got entry after it has been resolved.

But won’t this technique fail if e.g. the .got entry stores the address 0xffff00ff?

In this case, puts would only output 0xff? Have I misunderstood something?

Can a caster Deliberately Fail Wrest Resources to produce adamantium?


This is a request for a viability check on a spell combo to mass produce adamantium.

My questions are:

  • Is this viable?
  • Am I missing any negative consequences not accounted for?
  • Is there a way to make the Adamantium Stable? I.E. No longer susceptible to Dispel Magic or Flesh to Stone, etc.

Sequence of Events:

  1. Cast Clone or Kidnap a Beggar to use as “Body Fodder” for Magic Jar.
  2. Use Magic Jar on Clone Body or Beggar.
  3. Cast the ritual Wrest Resources. Make sure you don’t have the required skills to successfully complete the spell.
  4. Let your current body be turned into Adamantium via the Flesh To Stone aspect of Wrest Resources.
  5. Let magic Jar Expire, return to your original body.
  6. Cast Restoration on yourself to remove the negative level.

Relevant Quotes:

Magic Jar

the host body is slain, you return to the magic jar, if within range, and the life force of the host departs (it is dead). If the host body is slain beyond the range of the spell, both you and the host die. Any life force with nowhere to go is treated as slain.

If the spell ends while you are in the magic jar, you return to your body. If the Spell ends while you are in a host, you return to your body.

Flesh To Stone

The subject, along with all its carried gear, turns into a mindless, inert statue. If the statue resulting from this spell is broken or damaged, the subject (if ever returned to its original state) has similar damage or deformities. The creature is not dead,

Wrest Resources

Failure: All casters take 6d6 points of damage and are exhausted. The primary caster is the target of a flesh to stone spell (DC = 16 + the primary caster’s Charisma bonus) but instead of stone the spell turns the caster into the resource used in the material component.

Backlash The primary caster takes 1 permanent negative level.

Reference Links:

  • Clone – Used for the “Extra” Body necessary to pull this off with moral ambiguity. Spell target for Magic Jar.
  • Beggar – Alternative spell target for Magic Jar – Evil Alignment Requirement.
  • Magic Jar – Used to get out of our Adamantium body.
  • Flesh to Stone – This is what we want to happen to us.
  • Wrest Resources – The spell we want to fail.
  • Restoration – Needed to undue the negative caster level post ritual.
  • Stone to Flesh – A possible problem spell.
  • What is a reliable source of Adamantium? – The whole reason were doing this.

Does Tarjan algorithm fail for this test case ? references :gfg and Tushar roy’s tutorial

The test case is : There are 3 vertices 1,2,3 such

edge: source-destination

1-2 1-3 2-3 

As dfs proceeds from 1 to 2 and then to 3 . Following are the discovery and low times :

1 discT:0,lowT:0;  2 discT:1,lowT:1;  3 discT:2,lowT:2; 

Since 2’s disc time is less than 3’s low time . 2 becomes the articulation point due to the theorem which should NOT BE.

Am i doing something wrong . Kindly explain. Below is my dfs function->

public void dfs(){              ArrayDeque<vertex> st=new ArrayDeque<>();              st.push(vertexList.get(0));              int pt=1;             vertexList.get(0).discTime=0;             vertexList.get(0).lowTime=0;             vertexList.get(0).visited=true;             int numberOfverticesCovered=0;              while(!st.isEmpty()){                  vertex v=st.peek();                  System.out.println("considering "+v.label);                  vertex p=getAdjacent(v);                  if(p==null)                  {                      System.out.println("left with no unvisited adjacent vertices "+v.label);                      if(v!=vertexList.get(0)){                          LinkedList<edge> le=adjList.get(v.label-1);                          for (edge e : le)                          {                                  if(v.discTime<=e.destination.lowTime)                                  {                                     artPoints.add(v);                                      System.out.println("new articulation point found "+v.label+" for edge "+e.source.label+" and "+e.destination.label);                                      System.out.println("disc time of "+v.label+"  is "+v.discTime+" and low time is "+v.lowTime);                                      System.out.println("disc time of adj "+e.destination.label+"  is "+e.destination.discTime+" and low time is "+e.destination.lowTime);                                     break;                                  }                                     v.lowTime=Math.min(v.lowTime, e.destination.lowTime);                                     System.out.println("new low time of "+v.label+"  is "+v.lowTime);                          }                      }                      numberOfverticesCovered+=1;                      st.pop();                  }                  else                  {                      v.children+=1;     //                 System.out.println("adding child "+p.label+" to parent "+v.label);                      p.discTime=pt;                      p.lowTime=pt;                      p.parent=v;                      st.push(p);                      pt+=1;                  }                  if(st.isEmpty()&& numberOfverticesCovered!=vertexList.size()){                      for (vertex object : vertexList) {                          if(!object.visited)                          {                              object.discTime=pt;                              object.lowTime=pt;                              object.visited=true;                              st.push(object);                              break;                          }                      }                  }              }               if(vertexList.get(0).children>1 ) //  put in check for back edge for the other children so that they are not connected to each other.              {                               artPoints.add(vertexList.get(0));                  System.out.println("added root as an articulation point and it has "+vertexList.get(0).children);              }           }       } 

OpenVPN handshake fail after Debian upgrade

I upgraded my Debian server from 7 to 9 few days ago and, since then, I can’t connect to my openvpn anymore.

I tried to remove & purge openvpn and reinstall it with https://github.com/Nyr/openvpn-install

But the handhshake still fail…

I also remove all the rules in iptables wihtout success.

I’m conecting with tunnleblick on MacOsxm here is the logs:

My config:

client dev tun proto udp sndbuf 0 rcvbuf 0 remote 92.*.21.* 1194 resolv-retry infinite nobind persist-key persist-tun remote-cert-tls server auth SHA512 cipher AES-256-CBC setenv opt block-outside-dns key-direction 1 verb 3 

the error:

2019-06-15 09:20:49.517373 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity) 2019-06-15 09:20:49.518603 TLS Error: TLS handshake failed 2019-06-15 09:20:49.519079 SIGUSR1[soft,tls-error] received, process restarting 

Fail to ping from single machine to another specific machine

I’m using Google Cloud, there are 2 machines on the cloud which can’t ping each other, A can’t ping B, and B can’t ping A too; all other machines can ping to A&B as usual. But it happens only on Internet IPs, not LAN IPs.*

The difference is this way:

#fails, timeout ping 35.197.x.x #internet ips  #ok as normal ping 10.240.x.x #LAN ips on google cloud 

I have disabled Google Cloud firewall, firewalld service, iptables, ufw; still no luck. Why is it so?

When running ‘netstat -nc’ on the listener server, it keeps showing SYN_RECV and never ESTABLISHED.

#test ssh connection from A to B, #run netstat on B: netstat -nc | grep IP_OF_A