Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Although there is an error, it runs successfully, and the cracking speed is very slow (Subsequent installation errors occur in Windows PowerShell) #10

Open
yangxin325 opened this issue Feb 22, 2022 · 2 comments

Comments

@yangxin325
Copy link

yangxin325 commented Feb 22, 2022

There is an error, and the cracking speed is very slow,like a snail.

npm start

unredacter@1.0.0 start
npm run build && electron ./dist/main.js

unredacter@1.0.0 build
tsc

(node:8300) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(node:20660) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.

Steps to Reproduce

First npm install, second npm start

Additional context

Win10 , Desktop, Browser:Google Chrome vision 98.0.4758.102 , 2022.2.22

Relevant screenshots

image
image
image

@yangxin325 yangxin325 changed the title Although there is an error, it runs successfully, and the cracking speed is very slow Although there is an error, it runs successfully, and the cracking speed is very slow (Subsequent installation errors occur in Windows PowerShell) Feb 26, 2022
@yangxin325
Copy link
Author

npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm WARN deprecated debug@4.2.0: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)
npm ERR! code 1
npm ERR! path C:\Users\HUAWEI\Downloads\unredacter-main\node_modules\electron
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c node install.js
npm ERR! RequestError: read ECONNRESET
npm ERR! at ClientRequest. (C:\Users\HUAWEI\Downloads\unredacter-main\node_modules\got\source\request-as-event-emitter.js:178:14)
npm ERR! at Object.onceWrapper (node:events:640:26)
npm ERR! at ClientRequest.emit (node:events:532:35)
npm ERR! at ClientRequest.origin.emit (C:\Users\HUAWEI\Downloads\unredacter-main\node_modules@szmarczak\http-timer\source\index.js:37:11)
npm ERR! at TLSSocket.socketErrorListener (node:_http_client:442:9)
npm ERR! at TLSSocket.emit (node:events:520:28)
npm ERR! at emitErrorNT (node:internal/streams/destroy:157:8)
npm ERR! at emitErrorCloseNT (node:internal/streams/destroy:122:3)
npm ERR! at processTicksAndRejections (node:internal/process/task_queues:83:21)

npm ERR! A complete log of this run can be found in:
npm ERR! D:\Program Files\nodejs\node_cache_logs\2022-02-26T09_17_13_337Z-debug-0.log

Subsequent installation errors occur in Windows PowerShell

@dan-bishopfox
Copy link
Member

No idea what's up with those warnings.

But in terms of speed, just how slow is "like a snail"? That's rather subjective. Can you try to guesstimate how many iterations per second you're getting?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants