nmap – Inconsistent Output Reason

nmap – Inconsistent Output Reason – Information Security Stack Exchange

readability – reading mathematical formula’s in pdf with matlab is inconsistent, how to generalize this?

I’m trying to extract certain pieces of text (the 4.50% and the 22.50% in picture 1) from a pdf file with matlab. To do so I use the pdfRead function. To get the text as generic as possible I remove enters, double spaces, tabs and indents and make all text uppercase. In reading the file, I run into the following problem:

  • some text in the file seems to be in math mode (see picture 1 and pay special attention to the two cases of “Notional Amount”) :

File I try to read with math mode in different places.

  • It turns out this math mode is not consistent when reading it with pdfRead (see picture 2 and pay special attention to the two cases of “Notional Amount” (For readability I chose to show the file before removing enters, double spaces etc. however the problem is the same)).
  • The spaces within the word “notional amount” here are in a different spot for every pdf file, this results in the fact that I cannot use 1 matlab code for multiple pdf files (I do need that).

Problem when reading in Matlab

  • Besides this when copy pasting the part into my command window it appears different than it appears in the text (see picture 3)

Difficulty with copy paste

My question consists of multiple questions:

  1. Why doesn’t the text appear as text and how can I make it appear as text?
  2. How can I make this part generic such that I can read multiple pdf files with the same code?

Solutions I tried:

  • Removing all spaces
  • Saving it as a txt file and try to change font (the formula part didn’t change)
  • Use Python to try to adjust the file

requirejs – Getting the dreaded inconsistent $fotoramaElement.fotorama is not a function

I see quite a few people have this issue, but I can’t find a solution that works. I have app/design/frontend/Smartwave/porto_child/requirejs-config.js and I have it shimed, but I’m getting the same error.

var config = {
    paths: {
        'parallax': 'js/jquery.parallax.min',
        'sfowlcarousel': 'owl.carousel/owl.carousel.min',
        'owl.carousel_thumbs': 'owl.carousel/owl.carousel2.thumbs',
        'floatelement': 'js/jquery.floatelement',
        'sfs/stellar': 'js/jquery.stellar.min',
        'jquery/lazyload': 'js/jquery.lazyload',
        'fotorama/fotorama': 'fotorama/fotorama'
    },
    shim: {
        'fotorama/fotorama': {
            deps: ['jquery']
        },
        'parallax': {
            deps: ['jquery']
        },
        'sfowlcarousel': {
            deps: ['jquery']
        },
        'owlcarousel_thumbs': {
            deps: ['jquery', 'sfowlcarousel']
        },
        'floatelement': {
            deps: ['jquery']
        },
        'sfs/stellar': {
            deps: ['jquery']
        },
        'jquery/lazyload': {
            deps: ['jquery']
        }
    },
    config: {
        mixins: {
            'mage/collapsible': {
                'js/collapsible-mixin': true
            }
        }
    }
};

Understanding inconsistent behaviour of template layout in Pages for Mac

I came across the problem when I was trying to adjust a layout of CV document, based on one of those available in Pages for Mac. On the shared screenshot there are two freshly created documents in Pages for Mac (well, I’ve just removed contact text area on the left to indicate that it has no impact on the problem).

contemporary-vs-business-body-shift

The one on the left is created from “Contemporary CV”, the one on the right – “Business CV”. In both documents the body box is shifted about 6,5cm from left edge of the page. However, in “Contemporary” this is clearly indicated in document properties (also header & footer seem to follow the left margin setting). On the other hand, the “Business” one seems to have the document body shifted to the right by some kind of “magic setting”. Left margin is set to 2,12cm – which is respected by header and footer, yet document body is still intended by ~6,5cm. Moreover, it is not possible to change left margin to negative number, so document body is always shifted, even at value of 0. This remains whether I choose portrait or landscape. With ‘facing pages’ on document body is shifted from right edge on even pages, unsurprisingly.

My intention was to take the “Business” template but make document body occupy full page width. This would be easy with “Contemporary”. But I couldn’t find ANY difference between the two documents, that would cause the document body box to shift. Is there any hidden or not so obvious setting that is causing this irregular behaviour?

why is “arp -a” showing inconsistent outputs that are vastly different?

I have newly set up a computer with Ubuntu 18.04 and connected to my home wifi. When I try arp -a command to scan other devices connected to the same network, I see some very weird outputs.

First, the connect is fine by checking ifconfig:

john@home:~$ ifconfig 
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 246054  bytes 21958490 (21.9 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 246054  bytes 21958490 (21.9 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlo1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.14  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::e3f:e0a5:2438:a96a  prefixlen 64  scopeid 0x20<link>
        inet6 240d:1a:6a5:c900:1420:b3cc:994b:1b7b  prefixlen 64  scopeid 0x0<global>
        inet6 240d:1a:6a5:c900:74f4:f504:3a41:bc12  prefixlen 64  scopeid 0x0<global>
        ether 04:33:c2:c4:02:a2  txqueuelen 1000  (Ethernet)
        RX packets 2452125  bytes 3302288691 (3.3 GB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 964749  bytes 117659686 (117.6 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

It has the ip address of 192.168.1.14
Then I tried arp -a:

john@home:~$ arp -a 
? (192.168.1.19) at 92:c4:78:3c:46:16 (ether) on wlo1
_gateway (192.168.1.1) at e4:7e:66:1f:bf:4c (ether) on wlo1
? (192.168.1.5) at 26:36:46:f9:69:83 (ether) on wlo1

which makes sense because I can confirm that my ipad has ip address of 192.168.1.19 and my phone has ip address of 192.168.1.5

However, after a while I executed arp -a again, and the output blows my mind:

john@home:~$ arp -a 
? (192.168.1.206) at <incomplete> on wlo1
? (192.168.1.183) at <incomplete> on wlo1
? (192.168.1.107) at <incomplete> on wlo1
? (192.168.1.8) at <incomplete> on wlo1
? (192.168.1.18) at <incomplete> on wlo1
? (192.168.1.165) at <incomplete> on wlo1
? (192.168.1.186) at <incomplete> on wlo1
? (192.168.1.110) at <incomplete> on wlo1
? (192.168.1.77) at <incomplete> on wlo1
? (192.168.1.33) at <incomplete> on wlo1
? (192.168.1.178) at <incomplete> on wlo1
? (192.168.1.123) at <incomplete> on wlo1
? (192.168.1.112) at <incomplete> on wlo1
? (192.168.1.96) at <incomplete> on wlo1
? (192.168.1.117) at <incomplete> on wlo1
? (192.168.1.74) at <incomplete> on wlo1
? (192.168.1.95) at <incomplete> on wlo1
? (192.168.1.84) at <incomplete> on wlo1
? (192.168.1.41) at <incomplete> on wlo1
? (192.168.1.62) at <incomplete> on wlo1
? (192.168.1.51) at <incomplete> on wlo1
? (192.168.1.8) at <incomplete> on wlo1
? (192.168.1.29) at <incomplete> on wlo1
? (192.168.1.18) at <incomplete> on wlo1
? (192.168.1.231) at <incomplete> on wlo1
? (192.168.1.252) at <incomplete> on wlo1
? (192.168.1.241) at <incomplete> on wlo1
? (192.168.1.198) at <incomplete> on wlo1
? (192.168.1.219) at <incomplete> on wlo1
? (192.168.1.208) at <incomplete> on wlo1
? (192.168.1.165) at <incomplete> on wlo1
? (192.168.1.186) at <incomplete> on wlo1
? (192.168.1.143) at <incomplete> on wlo1
? (192.168.1.132) at <incomplete> on wlo1
? (192.168.1.153) at <incomplete> on wlo1
? (192.168.1.110) at <incomplete> on wlo1
? (192.168.1.99) at <incomplete> on wlo1
? (192.168.1.120) at <incomplete> on wlo1
? (192.168.1.77) at <incomplete> on wlo1
? (192.168.1.66) at <incomplete> on wlo1
? (192.168.1.87) at <incomplete> on wlo1
? (192.168.1.44) at <incomplete> on wlo1
? (192.168.1.33) at <incomplete> on wlo1
? (192.168.1.54) at <incomplete> on wlo1
? (192.168.1.11) at <incomplete> on wlo1
? (192.168.1.21) at <incomplete> on wlo1
? (192.168.1.234) at <incomplete> on wlo1
? (192.168.1.244) at <incomplete> on wlo1
? (192.168.1.201) at <incomplete> on wlo1
? (192.168.1.222) at <incomplete> on wlo1
? (192.168.1.211) at <incomplete> on wlo1
? (192.168.1.168) at <incomplete> on wlo1
? (192.168.1.189) at <incomplete> on wlo1
? (192.168.1.178) at <incomplete> on wlo1
? (192.168.1.135) at <incomplete> on wlo1
? (192.168.1.156) at <incomplete> on wlo1
? (192.168.1.145) at <incomplete> on wlo1
? (192.168.1.102) at <incomplete> on wlo1
? (192.168.1.123) at <incomplete> on wlo1
? (192.168.1.112) at <incomplete> on wlo1
? (192.168.1.69) at <incomplete> on wlo1
? (192.168.1.90) at <incomplete> on wlo1
? (192.168.1.47) at <incomplete> on wlo1
? (192.168.1.36) at <incomplete> on wlo1
? (192.168.1.57) at <incomplete> on wlo1
? (192.168.1.3) at <incomplete> on wlo1
? (192.168.1.24) at <incomplete> on wlo1
? (192.168.1.237) at <incomplete> on wlo1
? (192.168.1.226) at <incomplete> on wlo1
? (192.168.1.247) at <incomplete> on wlo1
? (192.168.1.204) at <incomplete> on wlo1
? (192.168.1.193) at <incomplete> on wlo1
? (192.168.1.214) at <incomplete> on wlo1
? (192.168.1.171) at <incomplete> on wlo1
? (192.168.1.160) at <incomplete> on wlo1
? (192.168.1.181) at <incomplete> on wlo1
? (192.168.1.138) at <incomplete> on wlo1
? (192.168.1.159) at <incomplete> on wlo1
? (192.168.1.148) at <incomplete> on wlo1
? (192.168.1.105) at <incomplete> on wlo1
? (192.168.1.126) at <incomplete> on wlo1
? (192.168.1.115) at <incomplete> on wlo1
? (192.168.1.72) at <incomplete> on wlo1
? (192.168.1.93) at <incomplete> on wlo1
? (192.168.1.82) at <incomplete> on wlo1
? (192.168.1.39) at <incomplete> on wlo1
? (192.168.1.60) at <incomplete> on wlo1
? (192.168.1.49) at <incomplete> on wlo1
? (192.168.1.6) at <incomplete> on wlo1
? (192.168.1.27) at <incomplete> on wlo1
? (192.168.1.16) at <incomplete> on wlo1
? (192.168.1.229) at <incomplete> on wlo1
? (192.168.1.250) at <incomplete> on wlo1
? (192.168.1.207) at <incomplete> on wlo1
? (192.168.1.196) at <incomplete> on wlo1
? (192.168.1.217) at <incomplete> on wlo1
? (192.168.1.174) at <incomplete> on wlo1
? (192.168.1.163) at <incomplete> on wlo1
? (192.168.1.184) at <incomplete> on wlo1
? (192.168.1.141) at <incomplete> on wlo1
? (192.168.1.130) at <incomplete> on wlo1
? (192.168.1.151) at <incomplete> on wlo1
? (192.168.1.108) at <incomplete> on wlo1
? (192.168.1.97) at <incomplete> on wlo1
? (192.168.1.118) at <incomplete> on wlo1
? (192.168.1.75) at <incomplete> on wlo1
? (192.168.1.64) at <incomplete> on wlo1
? (192.168.1.85) at <incomplete> on wlo1
? (192.168.1.42) at <incomplete> on wlo1
? (192.168.1.63) at <incomplete> on wlo1
? (192.168.1.52) at <incomplete> on wlo1
? (192.168.1.9) at <incomplete> on wlo1
? (192.168.1.30) at <incomplete> on wlo1
? (192.168.1.19) at <incomplete> on wlo1
? (192.168.1.232) at <incomplete> on wlo1
? (192.168.1.253) at <incomplete> on wlo1
? (192.168.1.242) at <incomplete> on wlo1
? (192.168.1.199) at <incomplete> on wlo1
? (192.168.1.220) at <incomplete> on wlo1
? (192.168.1.209) at <incomplete> on wlo1
? (192.168.1.166) at <incomplete> on wlo1
? (192.168.1.187) at <incomplete> on wlo1
? (192.168.1.176) at <incomplete> on wlo1
? (192.168.1.133) at <incomplete> on wlo1
? (192.168.1.154) at <incomplete> on wlo1
? (192.168.1.111) at <incomplete> on wlo1
? (192.168.1.100) at <incomplete> on wlo1
? (192.168.1.121) at <incomplete> on wlo1
? (192.168.1.78) at <incomplete> on wlo1
? (192.168.1.67) at <incomplete> on wlo1
? (192.168.1.88) at <incomplete> on wlo1
? (192.168.1.45) at <incomplete> on wlo1
? (192.168.1.34) at <incomplete> on wlo1
? (192.168.1.55) at <incomplete> on wlo1
? (192.168.1.12) at <incomplete> on wlo1
_gateway (192.168.1.1) at e4:7e:66:1f:bf:4c (ether) on wlo1
? (192.168.1.22) at <incomplete> on wlo1
? (192.168.1.235) at <incomplete> on wlo1
? (192.168.1.224) at <incomplete> on wlo1
? (192.168.1.245) at <incomplete> on wlo1
? (192.168.1.202) at <incomplete> on wlo1
? (192.168.1.223) at <incomplete> on wlo1
? (192.168.1.212) at <incomplete> on wlo1
? (192.168.1.169) at <incomplete> on wlo1
? (192.168.1.190) at <incomplete> on wlo1
? (192.168.1.179) at <incomplete> on wlo1
? (192.168.1.136) at <incomplete> on wlo1
? (192.168.1.157) at <incomplete> on wlo1
? (192.168.1.146) at <incomplete> on wlo1
? (192.168.1.103) at <incomplete> on wlo1
? (192.168.1.124) at <incomplete> on wlo1
? (192.168.1.113) at <incomplete> on wlo1
? (192.168.1.70) at <incomplete> on wlo1
? (192.168.1.91) at <incomplete> on wlo1
? (192.168.1.80) at <incomplete> on wlo1
? (192.168.1.37) at <incomplete> on wlo1
? (192.168.1.58) at <incomplete> on wlo1
? (192.168.1.15) at <incomplete> on wlo1
? (192.168.1.4) at <incomplete> on wlo1
? (192.168.1.25) at <incomplete> on wlo1
? (192.168.1.238) at <incomplete> on wlo1
? (192.168.1.227) at <incomplete> on wlo1
? (192.168.1.248) at <incomplete> on wlo1
? (192.168.1.205) at <incomplete> on wlo1
? (192.168.1.194) at <incomplete> on wlo1
? (192.168.1.215) at <incomplete> on wlo1
? (192.168.1.172) at <incomplete> on wlo1
? (192.168.1.161) at <incomplete> on wlo1
? (192.168.1.182) at <incomplete> on wlo1
? (192.168.1.139) at <incomplete> on wlo1
? (192.168.1.128) at <incomplete> on wlo1
? (192.168.1.149) at <incomplete> on wlo1
? (192.168.1.106) at <incomplete> on wlo1
? (192.168.1.127) at <incomplete> on wlo1
? (192.168.1.116) at <incomplete> on wlo1
? (192.168.1.73) at <incomplete> on wlo1
? (192.168.1.94) at <incomplete> on wlo1
? (192.168.1.83) at <incomplete> on wlo1
? (192.168.1.40) at <incomplete> on wlo1
? (192.168.1.61) at <incomplete> on wlo1
? (192.168.1.50) at <incomplete> on wlo1
? (192.168.1.7) at <incomplete> on wlo1
? (192.168.1.28) at <incomplete> on wlo1
? (192.168.1.17) at <incomplete> on wlo1
? (192.168.1.230) at <incomplete> on wlo1
? (192.168.1.251) at <incomplete> on wlo1
? (192.168.1.240) at <incomplete> on wlo1
? (192.168.1.197) at <incomplete> on wlo1
? (192.168.1.218) at <incomplete> on wlo1
? (192.168.1.175) at <incomplete> on wlo1
? (192.168.1.164) at <incomplete> on wlo1
? (192.168.1.185) at <incomplete> on wlo1
? (192.168.1.142) at <incomplete> on wlo1
? (192.168.1.131) at <incomplete> on wlo1
? (192.168.1.152) at <incomplete> on wlo1
? (192.168.1.109) at <incomplete> on wlo1
? (192.168.1.98) at <incomplete> on wlo1
? (192.168.1.119) at <incomplete> on wlo1
? (192.168.1.76) at <incomplete> on wlo1
? (192.168.1.65) at <incomplete> on wlo1
? (192.168.1.86) at <incomplete> on wlo1
? (192.168.1.43) at <incomplete> on wlo1
? (192.168.1.32) at <incomplete> on wlo1
? (192.168.1.53) at <incomplete> on wlo1
? (192.168.1.10) at <incomplete> on wlo1
? (192.168.1.31) at <incomplete> on wlo1
? (192.168.1.20) at <incomplete> on wlo1
? (192.168.1.233) at <incomplete> on wlo1
? (192.168.1.254) at <incomplete> on wlo1
? (192.168.1.243) at <incomplete> on wlo1
? (192.168.1.200) at <incomplete> on wlo1
? (192.168.1.221) at <incomplete> on wlo1
john@home:~$ 

What is this? What just happened?
I thought arp -a is supposed to scan and list other devices on the same network. What are these results?

database design – multiple inconsistent states and multiple deadlocks

Do these plural ‘states’ and ‘deadlocks’ mean that multiple inconsistent states and multiple deadlocks may occur? If they were singular (an inconsistent state, a deadlock) then would there be only one of them at a time, please?

If we do not use locking, or if we unlock data items too soon after
reading or writing them, we may get inconsistent states. On the
other hand, if we do not unlock a data item before requesting a lock
on another data item, deadlocks may occur.

Database System Concepts

openstack – Keystone scopes behavior is inconsistent between nova and cinder

I’ve been trying to update our OpenStack installation to use new options enforce_new_defaults and enforce_scope since in Wallaby for nova old policies will be deprecated. Those option seem to be present in many components (nova, cinder, keystone, glance, …) so I thought it is good idea to enable them everywhere. I’ve started with nova and cinder and hit interesting problem.

I’ve created user test without default project and assigned it admin permissions in system scope and in one project. Both options mentioned before are set to true in nova and cinder. Policy files are absent (because I want to test defaults).

Doing basic test (https://docs.openstack.org/keystone/latest//admin/tokens-overview.html#authorization-scopes):

  • openstack token issue gives me unscoped token
  • openstack --os-system-scope=all token issue gives me system-scoped token
  • openstack --project-name=NAX.Prod token issue gives me project-scoped token

So far so good. Now fun starts:

  • openstack volume service list – FAIL: The service catalog is empty.
  • openstack --os-system-scope=all volume service list – FAIL: public endpoint for volumev3 service not found
  • openstack --os-project-name=NAX.Prod volume service list – OK

System-scoped request does not pass, because volumev3 service uses /v3/%(project_id)s in the endpoint URL (double checked docs) so it seems without authenticating to some project it won’t work.

Looking in the generated policy, it seems to not support scopes for this request:

# List all services.
# GET  /os-services
#"volume_extension:services:index": "rule:admin_api"

Fine, now the nova:

  • openstack compute service list – FAIL: The service catalog is empty.
  • openstack --os-system-scope=all compute service list – OK
  • openstack --os-project-name=NAX.Prod compute service list – FAIL: Policy doesn't allow os_compute_api:os-services:list to be performed.

The relevant policy:

# List all running Compute services in a region.
# GET  /os-services
# Intended scope(s): system
#"os_compute_api:os-services:list": "rule:system_reader_api"

So it does seem to work as expected.


That said, if you want to manage OpenStack to perform same operation for different components (list services) you have to use different scopes (different OS_CLOUD or CLI arguments, depending how you have set it up). Is this really expected? Do I miss anything?

Relevant versions:

  • Keystone: 18.0.0
  • Nova: 22.0.1
  • Cinder: 17.0.0
  • OpenStack Client: 5.4.0
  • OpenStack SDK: 0.50.0

Unable to update due to inconsistent file permissions

Where can I find the permissions and how do I know which are inconsistent? I have no idea why I can’t update my WC version, any extensions, or plugins… help!

lightroom – Inconsistent colors across different apps in windows

I have finally pulled the trigger and got the monthly subscription for the PS + Lightroom CC. Yesterday when exporting the photo from lightroom I noticed a huge color difference when viewed with the Photos app. The photo is shifted more to red and there is a huge visible difference with what I see in lightroom before export.

Opening with Windows Photo Viewer however renders the colors fine. However, if I set the photo as desktop background it goes back to the reddish color. It is somewhat annoying to have such a discrepancy across the apps.

I have Dell U3014 monitor that was calibrated off the factory and never had this issue before. I could invest into color calibration tool, but they are rather expensive and I’d like to understand better what would that help me with. Also not sure I understand how color calibrating monitor will solve the issue of the same image being rendered differently on the same monitor. My understanding is that color calibration calibrates the color on the monitor with the color that you would see on the print. (?)

I have also tried exporting the photo with the older version of lightroom and it has the same issue, so it’s not the lightroom version per se, but I wonder if something in the Lighroom CC installation screwed something up.

Could you please help me understand what is the cause of this and how can one solve this problem?

Thank you.

Is inconsistent URL structure bad for SEO?

I work for a site and I don’t know why the content team did this, but here is an example:

example.com/food/italian is a page that contains links to Italian recipes, such as:

example.com/italian-food/lasagna

And all other Italian recipes are under that /italian-food/ folder. But the main page about Italian food (which links to all the recipes) is /food/italian/

I am thinking I should make a case that all the recipe URLs should be changed to /food/italian/{recipe-name}

However, I wanted to check here first in case this isn’t needed, as long as everything is interlinked. Generally speaking, the URL structure on the site makes sense, but not in this one case.

Thanks in advance for any help.

DreamProxies - Cheapest USA Elite Private Proxies 100 Private Proxies 200 Private Proxies 400 Private Proxies 1000 Private Proxies 2000 Private Proxies ExtraProxies.com - Buy Cheap Private Proxies Buy 50 Private Proxies Buy 100 Private Proxies Buy 200 Private Proxies Buy 500 Private Proxies Buy 1000 Private Proxies Buy 2000 Private Proxies ProxiesLive Proxies-free.com New Proxy Lists Every Day Proxies123