Skip to content

Translate security #9

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.

Sign up for GitHub

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

Jump to bottom
Merged
marocchino merged 1 commit into from
Feb 25, 2015
Merged

Translate security #9

marocchino merged 1 commit into from
Feb 25, 2015

Conversation

@marocchino
Copy link

@marocchino marocchino commented Feb 18, 2015

No description provided.

@marocchino marocchino changed the title Translate security Translate security (wip) Feb 18, 2015
@marocchino marocchino force-pushed the ko-security branch 2 times, most recently from da4f8cb to 258e221 Compare February 19, 2015 04:07
@marocchino marocchino changed the title Translate security (wip) Translate security Feb 19, 2015
@marocchino marocchino force-pushed the ko-security branch 2 times, most recently from f6725c3 to fc37635 Compare February 19, 2015 04:16
@marocchino
Copy link
Author

marocchino commented Feb 19, 2015

@ruby-korea/attendees 리뷰 부탁드립니다.

yous
yous reviewed Feb 24, 2015
View reviewed changes
security.md
Copy link

@yous yous Feb 24, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

다른 글에선 주로 '보안 수칙'이라고 번였되었는데, 하나로 맞추는 게 좋겠습니다.

Copy link
Author

@marocchino marocchino Feb 24, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

아마 Security Practices를 보안 수칙으로 하고 Security을 보안으로 하고 싶었던 것 같습니다.
이것도 다시 한번 확인해 볼께요.

Copy link
Author

@marocchino marocchino Feb 24, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

6b53199 에서 publishing의 110번째 줄을 보안으로 변경했습니다.
확인한 범위에서 다른 곳에 보안을 보안 수칙으로 표현한 부분은 없었습니다.

Copy link

@yous yous Feb 24, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

grep 해보니 _layouts/default.html의 83번째 줄만 추가로 고치면 될 것 같습니다.

Copy link
Author

@marocchino marocchino Feb 24, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

거기는 원래 Security Practices 였어서 그냥 두고 싶습니다 -0-

Copy link

@yous yous Feb 24, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

앗 이 부분은 Security Practices라고 되어 있군요. URL은 security길래 혼동했습니다. 😓

yous
yous reviewed Feb 24, 2015
View reviewed changes
security.md Outdated
Copy link

@yous yous Feb 24, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

망할 위험이 있습니다.

여기에서 'pwn'은 해킹, 크래킹 등을 의미합니다. http://en.wikipedia.org/wiki/Pwn

In script kiddie jargon, pwn means to compromise or control, specifically another computer (server or PC), web site, gateway device, or application. It is synonymous with one of the definitions of hacking or cracking, including iOS jailbreaking. The Pwnie Awards are awarded by a group of security researchers.[4]

'해킹 당할 위험이 있습니다.' 정도로 번역하면 될 것 같습니다.

yous
yous reviewed Feb 24, 2015
View reviewed changes
security.md Outdated
Copy link

@yous yous Feb 24, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

'떄문이며' → '때문이며'

yous
yous reviewed Feb 24, 2015
View reviewed changes
security.md Outdated
Copy link

@yous yous Feb 24, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

'trust'는 '신뢰'라고 해도 괜찮을 것 같습니다.

yous
yous reviewed Feb 24, 2015
View reviewed changes
security.md Outdated
Copy link

@yous yous Feb 24, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

'Yorick Peterse 님과의 대화를 확인하세요.'는 어떨까요?

Copy link

@yous yous Feb 24, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

이 부분의 논의가 빠진 것 같습니다.

Copy link
Author

@marocchino marocchino Feb 24, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

엇 그렇네요.

yous
yous reviewed Feb 24, 2015
View reviewed changes
security.md Outdated
Copy link

@yous yous Feb 24, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

pull request를 그냥 'pr'이라고 적어도 될지 모르겠습니다. '풀 리퀘스트'라고 해도 괜찮지 않을까요?

@marocchino marocchino force-pushed the ko-security branch 2 times, most recently from ec22c70 to 5d33f56 Compare February 24, 2015 07:15
yous
yous reviewed Feb 24, 2015
View reviewed changes
security.md Outdated
Copy link

@yous yous Feb 24, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

연락해 문제와 어떻게 악용될 수 있고 이상적인 해결책은 어떤 것인지 설명합니다.

원문에서 'ideally'는 'offering an indication of how it might be fixed' 전체를 꾸미는 말 같은데 어떠신가요? 해결책까지 제시한다면 완벽하다는 뜻으로 쓰인 것 같아요.

Copy link
Author

@marocchino marocchino Feb 24, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

이렇게 해보았습니다.

새로운 취약점처럼 보인다면 저자에게 비공개(즉, 풀 리퀘스트나 공개 프로젝트의 이슈는 사용하면 안 됩니다.)로 연락해 어떻게 악용될 수 있는지 문제를 설명합니다. 물론, 해결책까지 제시할 수 있다면 더 좋습니다.

@marocchino marocchino force-pushed the ko-security branch 2 times, most recently from ec5ba46 to 42f1db5 Compare February 24, 2015 07:26
yous
yous reviewed Feb 24, 2015
View reviewed changes
security.md Outdated
Copy link

@yous yous Feb 24, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

그 인증서로 서명된 모든 gem은 신뢰되게 됩니다.

'모든 gem을 신뢰하게 됩니다.'로 고쳐도 무방할 것 같습니다.

yous
yous reviewed Feb 24, 2015
View reviewed changes
security.md Outdated
Copy link

@yous yous Feb 24, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

패치된 버전을 포함해 사용자들이 업그레이드를 권장할 수도 있습니다.

'This may involve releasing a patched version'은 취약점 해결을 위해 패치된 버전의 gem의 릴리스가 필요할 수 있다는 얘기 같습니다.

Copy link
Author

@marocchino marocchino Feb 24, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

음.. 어렵네요.

패치된 버전을 릴리스해 사용자들에게 업그레이드를 권할 수도 있습니다.

yous
yous reviewed Feb 24, 2015
View reviewed changes
security.md Outdated
Copy link

@yous yous Feb 24, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

'해야하는 지를' → '해야하는지를'

marocchino added a commit that referenced this pull request Feb 25, 2015
@marocchino
Merge pull request #9 from marocchino/ko-security
66e426f 
Translate security
@marocchino marocchino merged commit 66e426f into rubykr:gh-pages Feb 25, 2015
@marocchino marocchino deleted the ko-security branch February 25, 2015 09:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@marocchino @yous